It's frustrating to read articles like this written by people who obviously don't travel much and therefore have no clue what they are talking about.
- Yes there are way fewer overhead bins than there are possible space for. This is a very well known thing to anyone who has ever boarded a plane.
- Not having carry on bags is an unworkable solution to anyone who ever has to connect anywhere, or values their time in any way.
- Checking bags adds a minimum of 20 minutes on either side of the flight in the best of cases, and when you have a delay and rebooking, not having checked bags will very often be the difference between you making the flight on the same day at all or not at all.
- The real problem, as any frequent flyer knows, is that airlines don't enforce their sizing guidelines. If they actually did, then a solid 30% of carry on bags would be refused at the gate because they are too large to fit properly in the bin and take up more space than should be allowed.
You are misreading and misunderstanding this whole paragraph.
The purpose of 10.4 is to allow zoom to send your call to other services, like say YouTube for live streaming, or any of the dozens of other services that integrate with their APIs. Without 10.4, three quarters or more of Zooms use cases would no longer work.
It is depressing how few people seem to be able to read or understand basic legal text nowadays.
Service Generated Data is *very clearly defined* to not include user generated data. Service Genrated Data would include data like APM, error logs, aggregate stats around how many customers use features. None of this data us PII.
It is depressing how many CISOs and others reposted this drivel.
Because Apple makes a shitton of money selling ads on iOS using its Ad ID.
Wait, did you seriously buy into their marketing BS about how they care about your privacy? Apple cares about making money, and that's it. They hamstrung Google and Meta on iOS simply so they would have a monopoly on advertising trackers on the platform.
They committed three person-years, not three years. This project would need dozens of person-years over a three year period.
Also a comment on Github is not a binding support contract. Meta executives could deprioritize this project at any time... hell the person making the commitment could already be laid off, we have no clue. As someone who worked in big tech for a long time, trust me - it needs to be in writing with an exec signature.
Name a single other major social network around today that has an API and allows third-party clients. The only one I can think of is Reddit - and even in that case, there are numerous features already being locked out of third-party clients. They are on the same path as Twitter, and at some point they will realize that maintaining a gigantic cost center that provides no revenue (since they don't control ads) and does not allow them to rapidly innovate or build a brand (since they don't control the app) does not make a lot of business sense.
The death of the Twitter API is long, long overdue. Bad for us consumers? Sure. But these companies are not charities, they exist to make money.