There was nothing automatic about Google's trustworthiness. It simply counted up links that lead back to a particular page. If it had more links it was (supposedly) a better page. Almost immediately webmasters around the world started gaming the system. Google still restricts some of the things my account can do for hidden links that were added to some ads on websites that I ran in like 2001. GoDaddy and all of the other big web hosting companies of that era all rose to prominence on the strength of gaming the PageRank system.

I am sure that other industries tell the same story.

PageRank might seem trustworthy to you, but that's only because you weren't trying to game the system back in the day. I can assure you that, right from the start, people were abusing PageRank in precisely the same way that upsets you now. The only difference was that registering a domain back then cost $70 for two years, and you probably created the links you used to game the system by writing Perl. That raised the barrier to entry significantly. However, there was still real money to be made in that arena, and whether the winners paid Google directly, or paid for back links to their content (or both), I can guarantee you that the road to your trust was paved in money.

In the end Google has decided that the most reliable way to have publishers show that their information is trustworthy is to force them to pay for the privilege. Coincidentally that also happens to be the method that makes Google the most money. For years an entire SEO industry has thrived around the idea that if you pay someone enough money they can trick Google to steal your information instead of your competitors. Now we are finally at the endgame and Google doesn't even send traffic. They simply summarize the information for their customers. Chances are excellent that you don't even leave the google.com domain.

Google's competitors are simply doing the same thing at a different domain. All of them make their money by charging publishers to show up prominently in search ranks. Whether you are rooting for Oceania, Eurasia, or Eastasia it's Big Brother all of the way down.

Jellyfish that could concentrate heavy metals from the water they live in.
You would let them breed and clean up water in an area, then release a pheromone to get them to jump into your harvester ship, render them and get the contaminants.

They were released in an area with an old nuclear waste dump, so some of the stuff they were concentrating was potentially fissile.
Especially so when the pheromone told them to go up the water intakes at a power plant...

Whether we like it or not, whether we use Windows or not, Microsoft is going to insist on adding the tax whether the PC comes shipped with Windows or not. This is illegal bundling, Microsoft has essentially ignored prior rulings, and it's pretty much a certainty the courts will be fine with this.

"How did you get hired?"
"I was top at Fortnite. You?"
"Combat flight sims."

"Damn, two Boeings just crashed over an oil refinery on city limits and took out half the city."
"Did you remember to save your position beforehand?"
"Yeah."
"The reload and continue from there. No-one will notice."

I love computer games. I have XPlane 12 and many scenery packs. I rank well on Elite:Dangerous. From the sounds of it, the FAA would see me as over-qualified. In reality? There's no way in hell I'd be taking those kinds of risks with real lives. There's a huge difference between having good reflexes and a good eye, versus having the complex 4D spacetime relationship mental models needed for robust air traffic control.

Freenet is also based on middle-out compression.

No. Trying to push 30TB into Freenet will be interpreted as an attack on the network by other peers and they'll disconnect from your peer.

Freenet is better viewed as a communication medium than a storage medium. Data is prioritized according to demand, somewhat like an LRU cache. You can't upload 30TB and expect the network to preserve it for you.

On liability, running a Freenet peer is more like running network infrastructure that automatically routes and caches other people's traffic than intentionally publishing it. US law explicitly recognizes this distinction in the DMCA's provisions for transitory network communications and system caching. We discuss this in more detail in the FAQ.

You obviously haven't tried Freenet. You can join our room on River and you'll see no spam, no fraud, no hate speech, none of that.

Decentralized doesn't mean unmoderated. Systems built on Freenet can be moderated however their creators and communities want. River is moderated.

The difference is that nobody running one service gets to decide what everyone else is allowed to run.

You see, Linus has embraced transhumanism and is testing out the new kernel as a supplementary brain function, using MOSIX to offload all of the irritable comment generation at yet more nonsense on the mailing list to an Elizabot that he has written specifically to do this. This saves his actual brain for real work.

AI is not currently capable of performing any meaningful conceptual abstraction, it is only capable of very basic mechanical abstraction. Abstraction is itself multi-dimensional. Nor is there any indication that AI could ever perform multi-dimensional abstraction or multi-dimensional decomposition. Precious few humans are capable of it either, but some can.

No, AI would need humans because the best system is not a pure system but a hybrid system, and that means transhumanism with AI operating as an additional brain function rather than as a replacement for a brain.

Tool calling is, yes, but the current approach to it is (a) overt not transparent to the user, (b) not designed for the purpose I've outlined, and (c) not remotely good enough for the AI to be able to manage data through such tools.

Yes, you can connect an AI to a PostgreSQL database. Whoopee. Not even close to an AI detecting via classifiers that some of the data is relational in nature, transparently setting up its own PostgreSQL database in response, and using that proactively as an additional way to examine the data. You would need to explicitly set up the constructs, explicitly set up the databases, explicitly tell it when, where, and how to use the database, and if that particular usage conflicted with a way the AI actually worked, the AI would not be able to use it effectively. That's not remotely close to what I'm talking about.

What I'm talking about is much, much deeper than that. AIs lose focus when there is too much information currently in the system. Absolutely nothing stops an AI from using a document database as a virtual memory in which it can page in and out conceptual spaces so that the focus on any given step of a problem concerns just the problem. Other than such a concept not existing yet, which is kind of a limiting factor. But you need to know what connects to what. The AI could use an ontology reasoner for that, or a relational database, or an external graph. But you cannot provide those tools and you cannot configure them, for the simple reason that the AI is the only entity with any detailed map of how the underlying neural net is connecting those ideas up.

The AI itself has to select the tools, has to configure the tools, has to do all the work. Which means YOU cannot use any sort of API. YOU should have no involvement in the underlying mechanisms needed for the internal NN housekeeping.

And that's your other error. You're assuming this is about user data. No. It's about housekeeping operations within the NN itself to maximise functionality, it has nothing to do with the user side of things at all. If the user was capable of setting up dynamically structured databases that mutated with each step of a decomposed analysis, you'd have done everything the AI would be doing and you wouldn't need the AI to begin with.

You cannot do this work, you cannot even assist in this work, it has to be dynamic and it has to be utterly invisible to the operator.

Right now, it is legal for third parties like Flock to collect surveillance data and offer it for sale to anyone.
The third party doctrine makes it presumed OK for third parties to give or sell their data to the Government.
This is rapidly eroding Fourth Amendment guarantees in the US.

One possible way out would be to specify in federal law that data that can enable mass surveillance must be protected - leaking it gets you fined, government doesn't get it without a warrant.

The HIPAA laws are a potential model here - they basically say data related to health care can only be shared between certain businesses, and only with the permission of the person the data is about.

We don't need bigger models, at this point. What we need is multi-dimensional decomposition, problem space transforms, and the ability for AI to use external tools (such as SQLite, memcached, etc) so that it can externalise static data that it needs to not corrupt accidentally but still keep in easy access.

If we had that, most of the things "bigger models" will do will actually end up being done better, quicker, with fewer compute resources.

To be useful in deep space, you're going to have to deal with very harsh radiation, far harder than the Vikings dealt with. You really want to have some large number of computers, where the number has to be odd and exceed 5. The reason it has to exceed 5 is that you need 5 in order to be able to use the Byzantine General's Problem to discern which computers are working correctly and which are radiation damaged. Since some will be damaged over time and you want 5 computers still operating around the time the power runs out, you have to start with more than that.

Massively radiation-hardened highly-robust low-power chips could be done. If you were clever enough, you could do this as a wafer-scale system where you marked parts as bad and networked around them. Free space optical communication across the wafer might be doable.

They might well still end up being low-density CMOS discrete logic.

Lead-lining the electronics isn't as much of a problem if you've launchers capable of handling heavy objects and don't mind burning through a lot of ion drive propellant for course corrections. This would improve the hardening beyond what can be done through the usual operations.

But, yeah, you'd need defect-free microelectronics. You really can't handle F00F bugs or defective instructions once you pass Earth orbit. And I can't think of anyone who knows how to do that.

Well, not just the solar system but the heliopause as well, and the near-Sol galactic winds. We can estimate the effects of space from just about any ancient near-Earth space junk, but I'm not sure how we'd go about calculating the impact of the galactic winds on something. The Voyager sensors won't be sending back nearly enough high-quality data to establish that.