The EU is one of the primary tools all these authoritarians use to push their agenda. In which functional democracy do parliaments have to vote AGAINST a bill? Which sane democracy establishes a literal ministry of truth? Which non-dystopian government introduces highly destructive laws (forcing every small online store to hire a legal representative in every single memberstate they want to ship to) and then telling desparate small business owners not to worry, because surely their countries wont enforce those laws?

And all of those happened AFTER the British people saw the writing on the wall and forced their rulers to downgrade their rank in the new aristocracy.

The decline is entirely by design.

I really wonder why this was never fundamentally fixed. How performant a certain instruction on a specific platform is, how well it is supported and potential equivalents or sets of other instructions to emulate an equivalent are usually all very well understood.

So there should be some graph of operations which can transform any software from and to the specifics of each platform. Especially because firmware + compliers + platform abstracting libraries are basically already just that graph, although (usually?) to lossy to be applied in reverse. Add the recent developments in very large scale statistics to it and it'd probably be quite possible to transform from and to generic intent in the implementation to the uniqueness of each platform. E.g. the theming differences between a MacOS UI and a terminal application served over serial or the processing capabilities of a VLIW CPU compared to a FPGA or a GPU server.

Considering the enormous amount of work that went into compilers, better debugging and intermediate representations it seems like a huge missed opportunity nobody seriously asked the question whether information could be emitted that would allow for decompiling all the way back to the generic intent.

All these projects only took off because people were forced to contribute back. Want an example? Look at the state of opensource boot firmware on x86. The "open source" version heavily relies on proprietary firmware blobs and the only actual open source alternative had been heavily ridiculed for pursuing that goal and trading basically any significant compatibility for it.

Copyleft licenses make software basically self-regulating utilities. You can draw power from the grid and in return help finance it for everyone else, or you could build your own power plants.

You can draw excellent pre-made software and tooling from copylefted repositories and contribute back, helping to make the software even better for everyone else, or you could build all of it yourself. Or, you could put in the work to replace all major copyleft software with non-copyleft versions, eventually gaining the ability to pull up the ladder behind you.

You wouldn't want to decide what's worth training on and what isn't manually, so there is almost certainly an automated pipeline to do so (certainly at least for the free accounts and those that dont opt out of training).

Then there's the question if this pipeline only sorts through the data or also transforms it and to what degree. E.g. for removing personal details, locations, medical information and so on. The data that comes out of this pipeline might have VERY little information left in it a human could connect to the original input. Even worse, since we're talking about companies specializing in sota statistics, the input data could have been transformed into a representation that is very well suited to represent all the novel and interesting parts, but is awful at modelling all the things that could end up identifying where the data comes from (or causes legal liabilities otherwise).

In the end the only thing a potential whistleblower might even have a chance at observing in the first place, is whether a company's data enters such a pipeline or not. And I have my suspicions that the major AI companies operate at a scale and level of automation, that absolutely nobody has a chance at figuring out where anyone's data is at any point in time and what any specific piece of equipment is currently busy with.

So the only place to figure out whether data is trained on that shouldn't be trained on is by looking at whatever configurates every single system that could take a peek at some customer's data or the systems themselves while processing the data.

The latter would be such a huge violation of a customer's rights, no whistleblower is going to attempt that or admit to doing it.

And the configuration for the former could live just about anywhere, from regular config files to the CI/CD pipeline, pre-compiled libraries, kernel modules, modified vendor firmware, the compiler itself ... and probably plenty other scenarios you'd have to train an LLM on the ramblings of a crackhead to come up with.

So I'd say a whistleblower is pretty out of luck even becoming one.

As if an online community of mostly software developers had never heard of such obscure writings like the GPL, AGPL, LGPL, and so on.

I get it, the person running GrapheneOS happens to be ... special, but there could hardly be any community that has benefited more off copyright than the free software one.

Is that even a question? Of course everything not kept on premise at gunpoint is going to be trained on. The chances of getting caught are 0 and the consequences of getting caught are 0 (as we've seen with copyright laws going from sending people to jail for years to unenforced within months). Yet the benefits are through the roof. Your customers aren't going to pay for having the very same data vibe enriched twice, it's exclusive, extremely high value data your competitors will never have access to.

All of these side effects just disappear if we were to engineer this dust to emit a lot of radiation outside of the absorption spectra of water vapour and CO2, absorb a lot of light in the the absorption spectra of water and CO2, mix it as pigment into paint, rooftiles, road surfaces, and so on.

That way absorbed direct radiation gets its climate change contribution cut about in half and probably much more for diffuse radiation.

We could also biologically engineer e.g. grasses to have similar effects.

I'm a huge fan of engineering various plants to emit light in specific wavelengths anyway, and making sure that e.g. insects pollinate and birds spread them much more preferentially. That way you can outcompete or naturally cross invasive species with them and then you'll just look from satellites were the stuff you dislike is spreading and send in automated drones to highly selectively spray anything that has weirdly glowing pollen stuck to it. And after repeating that a few times, you get rid of your trojan-glowies.

The real problem is not really drivers being tracked, but how the tracking data is or might be used. Timestamped delivery notifications might be just as bad in this regard.

As often, the solution is probably more about accessible and pro-human law. No idea how that should work, maybe certain sensitive data services having to be provided by a third party or even the government itself? There are probably much smarter ideas or variations of this...

1. Is the law aligned with moral and ethical expectations? Probably not.

2. Is the process reliable? At least since the Derek Chauvin trials, I'm having doubts, but it doesn't seem it had failed in this case.

Sure, cases of the former need urgent fixing (and we're not getting that), but the latter scenario falls into the "The end is nigh" category.

Despite its huge size and it installing several services that constantly run in the background, it's still one of my favorite "languages" of all time. It's the only one I've ever seen people going from never having programmed before to making simple but meaningful contributions in within a single day.

After that that scam would result in the scammer paying the (e.g.) $10 upfront, the (up to; e.g.) 10% for every hop between networks and likely and transaction, processing and legal fees for the civil case (if he's not cooperating).

And he'll likely end up with criminal charges on top of that.

Also it's not like the scammer gets sued by some powerless private citizen authorities are likely to ignore. His opponent will be a telecom provider in his own jurisdiction.

Result: All routes to non-cooperating networks get dropped within days to weeks and scam-calling stops being a lucrative business basically instantly.

Also, have you considered AI being necessary to fill in for missing surveillance footage if the cameras are failing (the ruling class)? E.g. the whole Epstein (PR) disaster could have been avoided if the cameras could have been kept running and the footage post-processed in time.

Isn't this solving a slightly, but very significantly different problem?

You could serve the very same data in two different ways: One to present to the users and one to hand over to scrapers. Of course, some sites would be too difficult or costly to transform into a common underlying cache format, but people who WANT their sides accessible to scrapers could easily help the process along a bit or serve their site in the necessary format in the first place.

But the key is:

A tool using a "pre-scraped" version of a site has very likely very different requirements of how a CDN caches this site. And this could be easily customizable by those using this endpoint.

Want a free version? Ok, give us the list of all the sites you want, then come back in 10min and grab everything in one go, the data will be kept ready for 60s. Got an API token? 10 free near-real-time request for you and they'll recharge at a rate of 2 per hour. Want to play nice? Ask the CDN to have the requested content ready in 3 hours. Got deep pockets? Pay for just as many real-real-time requests as you need.

What makes this so different is that unless customers are willing to hand over a lot of money, you dont need to cache anything to serve requests at all. Potentially not even later if you got enough capacity to serve the data for scheduled requests from the storage network directly.

You just generate an immediate promise response to the request telling them to come back later. And depending on what you put into that promise, you've got quite a lot of control over the schedule yourself.

- Got a "within 10min" request but your storage network has plenty if capacity in 30s? Just tell them to come back in 30s.

- A customer is pushing new data into your network around 10am and many bots are interested in getting their hands on it as soon as possible, making requests for 10am to 10:05? Just bundle their requests.

- Expected data still not around at 10:05? Unless the bots set an "immediate" flag (or whatever) indicating that they want whatever state the site is in right now, just reply with a second promise when they come back. And a third if necessary... and so on.

Cash just about never sits just around as long as whoever holds onto it has no current need for extremely liquid assets. Like insurances.

I doubt that the ratio of cash that ends up bound up that way to the one that doesn't changes a lot overall.

The real problem to UBI is governments creating income via debt, IMO.