210 karma · joined September 2, 2016
It writes itself.
So it becomes a purely business decision: Do we risk a 10% global revenue penalty to release this globally, do we release this everywhere the DMA does not apply, or do we simply not build it? And make no mistake, even if Apple moved heaven and earth to try to comply with DMA they are STILL RISKING the full 10% penalty if the EU decides against them.
"In September 2014, the CEO of Clarifai, Inc. e-mailed one of OkCupid’s founders requesting that Humor Rainbow give Clarifai, Inc. (i.e., the Data Recipient) access to large datasets of OkCupid photos."
[0] https://www.ftc.gov/system/files/ftc_gov/pdf/OkCupid-MatchCo...
Each and every Radar (Apple's internal issue tracker is called Radar, and each issue is called a Radar) follows a state machine, going from the untriaged state to the done state. One hard-coded state in this is Verify. Each and every bug, once Fixed, cannot move to Closed without passing through the Verify state. It seems like a cool idea on the surface. It means that Apple assumes and demands that everything must be verified as fixed (or feature complete) by someone. Quite the corporate value to hold the line on, and it goes back decades.
I seriously hated the Verify state. It caused many pathologies. Imagine trying to run a burndown of your sprint when zero of the Radars are closed, because they have to be verified in production before being closed, meaning you cannot verify until after the release. Another pathology is that lots (thousands and thousands) of Radars end up stranded in Verify. Many, many engineers finish their fix, check it in, it gets released and then they move on. This led to a pathology that the writer of this post got caught up in: There is lots of "org health" reporting that goes out showing how many Radars are unverified and how long your Radars stay in the unverified state on average. A lot of teams simply close Radars that remain unverified for some amount of time because they are being "graded" on this.
You are indeed missing a TON. A lot of Open Claw users don't give it everything. We give it specific access to a group of things it needs to do the things we want. If I want an agent to sit there 24/7 maximizing uptime of my service, I give it access to certain data, the GitHub repo with PR privileges, and maybe even permissions to restart the service. All of this has to be very thoughtful and intentional. The idea that the only "useful" way to use Open Claw is to give it everything is a straw man.
More like you cannot build a self-driving car without starting with a good phone. See Huawei.
1. https://www.levels.fyi/companies/google/salaries/software-en...
And there it is. This narrative that immigration hasn't been a constant and deciding factor in the development of the West (and pretty much everywhere else) is so wild. Stability of an insular population is the absolute exception of history.
By that logic around 35% of 24-year-old Americans have bachelor degrees. More than a third, but not by much.
[1] https://nces.ed.gov/programs/coe/indicator/coi/high-school-g... [2] https://educationdata.org/college-enrollment-statistics [3] https://nces.ed.gov/fastfacts/display.asp?id=40
My car knows when its key fob is inside it with great precision, to the point that I cannot even lock the doors while it is inside. My iPhone knows when it is itself in the car, so when I want to use it while driving, I have to dismiss a warning message, which I adeptly do with muscle memory.
Seems to me if cars supported driver and passenger authentication, most illegal device usage could be stopped rather trivially.