It’s easier to consider responses or solutions to specific problems, rather than to solve for a broad, general principle. You can see this in many areas of life. Solving for general principles requires group effort (usually); you can get buy-in from individuals if you csn focus them on specific cases or subsets. So the Floxk fetish is reasonable at this point, IMO.
There’s also nothing inherently wrong with carrying sensors in your pocket. The “wrong” is in the providers/manufacturers exploiting the position they put themselves in. Managing data is hard, and most people don’t want to do the necessary work most of the time, so the providers/manufacturers offer to do that for their users/customers. However, they also exploit their csretaker position by tresting the data like they own it too, and extracting profit.
If the solutions to the Flock problems could be framed such that other providers/manufacturers had to build systems that were “local first” or “private by default” (as in pre-internet home computing plus explicit, finegrained shsring consents), then it would also be fine to carry sensors. I want my fitness tracker and GPS. I just don’t want the data it generates used to build advertising profiles on me such that ads (and government mass surveillance dragnets) can follow my every other move.
Using a battery powered electronic device as a “pass” detected by another handheld electronic device, both of which are contacting cell towers, exchanging data with data centres 100s of kms away, filling out detailed profiles of user behavior … rather than a paper ticket?
All AI prices will rise soon - probably shortly after the IPOs. The new prices will be eyewatering compared with today’s. This bulling change is lengthening the time until Anthropic have to raise the subscription prices, so those of us who’re not doing 24hr claw stuff can continue to use the tools the way we’ve gotten used to.
I'm a beginner with agentic coding. I vibe code something most days, from a few lines up to refactors over a few files. I don't knowingly use skills, rarely _choose_ to call out to tools, haven't written any skills and only one or two ad hoc scripts, and have barely touched MCPs (because the few I've used seem flaky and erratic). I answered as such and got... intermediate.
I read the implication too, as well as the fatigue.
They offered nothing to counteract the idea that we should just shut up and accept it. Then they closed with "And I actually like the concept of reward cards (although I don't use them) because it is pretty much the only way how you can make money off your data." - which sounds like they have given up opposition, and are now considering ways to profit from the situation rather than fight it.
As the attack actor now has the data, they're liable for ongoing GDPR failures, on top of the theft. Then anyone they sell the data to becomes liable (on top of handling stolen goods). Could be a money-earner for the EU if they pursue it properly.
SoC is how all maintainable software is built. A function for A, a class for B, DDD-spec'd modules and features, databases on separate machines, API definitions, queuing systems, event systems, load balancing, web servers.
You don't even need to think of the web to see how content and presentation are different. Try editing a text file with hard line breaks in and you'll quickly understand how presentation and content are orthogonal.
Please don’t be so condescending. We all know what separation of concerns is.
The comment said “web development”, and it’s inarguably that in the history of web development there have been at least a couple of major misapplications of separation of concerns, which have had practically everlasting negative consequences.
Read what you’re replying to before you reply to it.
There’s also nothing inherently wrong with carrying sensors in your pocket. The “wrong” is in the providers/manufacturers exploiting the position they put themselves in. Managing data is hard, and most people don’t want to do the necessary work most of the time, so the providers/manufacturers offer to do that for their users/customers. However, they also exploit their csretaker position by tresting the data like they own it too, and extracting profit.
If the solutions to the Flock problems could be framed such that other providers/manufacturers had to build systems that were “local first” or “private by default” (as in pre-internet home computing plus explicit, finegrained shsring consents), then it would also be fine to carry sensors. I want my fitness tracker and GPS. I just don’t want the data it generates used to build advertising profiles on me such that ads (and government mass surveillance dragnets) can follow my every other move.
reply