Needs more attention. Anything that replicates ChatGPT using OpenAI APIs is valuable because of this fact for enterprise use cases.
https://mitta.ai uses these API calls, has an Open Source code base for inspection, a strong user privacy policy, and doesn't store data in transit, other than documents that are uploaded. I'm working on TTLs for the files stored, so there is no data left behind (other than what might be stored by the user in the DB).
What Bird is really fighting over in this case is the indemnification clause in their user agreement. If this clause is not found to be legal in California, the potential liability down the road could be millions in other cases.
What Bird is really fighting for here is their entire business. If Bird has to take on liability for any accident on their scooter, regardless of fault, then there is no scooter business. Heck, potentially no sharing type business at all could exist then.
This is the current indemnification clause. It could've been different at the time plaintiff in this case used Bird.
"In exchange for Rider being allowed to use Services, Vehicles, and other equipment or related information provided by Operator, Rider agrees to fully release, indemnify, and hold harmless Operator, Technology Services Provider and all of its and their owners, managers, affiliates, employees, contractors, fleet management service providers, officers, directors, shareholders, agents, representatives, successors, assigns, and to the fullest extent permitted by law any Municipality (including its elected and appointed officials, officers, employees, agents, contractors, and volunteers) in which Rider utilizes Services, and every property owner or operator with whom Operator has contracted to operate Services and all of such parties’ owners, managers, affiliates, employees, contractors, officers, directors, shareholders, agents, representatives, successors, and assigns (collectively, the “Released Persons”) from liability for all “Claims” arising out of or in any way related to Rider’s use of the Services, Vehicles, App, or related equipment, including, but not limited to, those Claims based on Released Persons’ alleged negligence, breach of contract, and/or breach of express or implied warranty, except for Claims based on Released Persons’ gross negligence or willful misconduct. Such releases are intended to be general and complete releases of all Claims."
Bird indemnifies the City of Los Angeles as part of their agreement to roll out the scooters. Bird then makes their users indemnify Bird in the user agreement.
The key to this whole thing is for a judge or jury to toss out the latter indemnification as unconscionable. If this indemnification clause is found to be unconscionable here, it could potentially open up Bird to significant liability in future cases. Bird is going to fight tooth-and-nail to make sure this is not the outcome, or offer to settle once it has enough information to figure out that the legal winds are not blowing in its favor.
Why should Bird be responsible for anything here though? There's no evidence or claim that there was anything wrong with the scooter that caused the accident...
No one made them do that. They did that because they wanted the right to rent the scooters in the city and the city knew that would come with real problems because shit happens. So Byrd says "Don't worry, we will accept responsibility for any problems."
Well they got the green light and are happy enough to collect the rent, but they tell the user "We accept no responsibility"
Bird isn't technically a party to this case, but it's on the hook for costs and damages via an agreement it has with the City of Los Angeles to indemnify the City. So, ultimately Bird would have to spend money if the indemnification clause it has with the end user is found to be illegal.
From the look of it this product is just an API to distribute the contract you already have and collect esignatures--kinda like Docusign, but with text.
I'm wondering about the use case of developers actually wanting to send out contracts (on behalf of their employer, I assume). Is this something that your clients who are software developers are asking for?
That's right! They often want to integrate with existing processes or products (often Salesforce) to automatically send contracts out for signatures on behalf of the company.
Right, but that is absolutely a misuse, since if anything it's the opposite that's meant, it's a 'claimer' - I claim relevant experience or context through being a lawyer and SE.
Again not just boring and nit-picking on something so common where I know what's meant; I was just surprised that a lawyer (i.e. someone so familiar with it) would make that error. (Or use it with that (proscribed) meaning, if you prefer.)
On non-disc road bikes, the tire size is limited by not only the width of the rims, but also by what the brake calipers can accommodate. For example, newer Shimano rim-brake calipers can accommodate tires up to 28mm in width, whereas older versions only up to 25mm in width. With disc bikes, the tire size is limited by what the wheel and frame can accommodate.
Gravel bike tires are all over the place, with companies making frames that can accommodate 700c, 29", and/or 27.5" wheels. And thus tire variations can be quite overwhelming.
Frame clearance can get you too. Cantilever brakes will allow you to fit a lot of tire, but you'll likely rub the frame long before you rub the brakes.
another "interesting" thing to consider is that some 700C gravel or cyclocross frames, designed for disc only, can take either 700C wheelsets or 650B. Because you no longer need to consider the vertical distance between the rim and the top of your fork, other than the general width between forks and rear stays for tire clearance.
650B is becoming increasingly popular for gravel.
There are a number of 650B tires that have intentionally higher than normal sidewall heights, so the total wheel+tire diameter is actually not that different from something like a 622x23 (aka 700C) skinny road bike tire on a traditional pavement only road bike.
If you have a disc only frame with wide tire clearance there exists the possibility of swapping between wheelsets that are either 650B or 700C depending on what type of riding you have planned in the near future.
My all road bike was built with 650b wheels since I didn't want skinny tires. The issue is that with this wheel size the bottom bracket is about 15…30 mm lower compared to 700c so you'll have to be careful with crank length due to the increased risk of pedal strike. Most of these bikes have a bottom bracket drop of 70 mm or more, while a frame designed for 650b specifically will have 54…60 mm. I don't know why the industry doesn't build frames with 65 mm BB drop since it would be in between, but I'm inclined to believe they prioritize 700c with 40…50 mm tires. But then one wouldn't be able to use anorher wheelset with skinny 25 mm tires for road, so you'll probably need a road bike. While designing for single wheel size only, the industry also ignores the needs of shorter people and most women.
Learning the material well and getting good grades are not necessarily correlated. If an assignment has grading rubrics, satisfy them literally and you'll get a good grade. As for really learning the material, it's often challenging to do within the timeline allowed for a course, especially with other courses competing for your attention. Just try to do well and get through the semester/quarter, then afterward when you have more free time, pick the subjects that speak to you and go through the material again, this time with the objective of internalizing the knowledge. Feel free to supplement your school material with material from other sources. Remember that what you're learning in school will only scratch the surface of CS; the real learning, if you choose to pursue it, will happen afterward.
Source: https://openai.com/enterprise-privacy