No argument here, but that wasn’t my point.

I’m not sure what you’re making here.

Well, the power efficiency being much better is one problem to solve. Also various laws need to make pronouncements on copyright, etc. There is also figuring out what will happen to open weight models, what will become of challenges like deepseek.

Ultimately, ai will remain in some form, or catalyze another kind of technology, but it will certainly change tech landscape the way the printing press did.

I suppose some folks were saying that about hydrogen-filled zeppelins too, but it turns out that you can’t just jam new tech down society’s throat that way.

We now have helium and hot air airships and the tech is used way more appropriately.

I do take your point that what whipped up AI frenzy isn’t just the tech, but the tech itself does needs to change before society will accept its ubiquity.

There are two kinds of self-hosters: those who backup, and those who will start testing em after their first failed restore.

Congrats on becoming one of the 5% of ppl who backup, but actually also test them.

Well, these things come in cycles. In the 90s everything had it’s own tool, then tools like Drupal and WordPress, office and image editing suites came along… And we went back to using simpler tools with app stores. And then we got orchestration with K8s. And so on.

We’re going through another a big change in software, and we’ll see more. The big, complex swiss army knife software suites again.

The UNIX philosophy does look like “do one thing and do it well”, but it’s really a means of working in such a way that one doesn’t introduce scope creep to a point of Drupal.

• I personally wouldn’t be touching /etc/crontab, but adding or editing a tab in /var/cron/tabs.
• I would use _test or just a bash eval instead of mkdir to check for the existence of a directory. Mkdir has backfired on me spectacularly in bash and sh scripts.
• always grep, then sort, then awk. Just as a habit, any other order can make run time long and cause globbing problems.
• good job

Your said you were going to use the cloud services, so even if you self-host, using a cloud service api carries the same risk as using their apps. This is an app to unify all the remote storage things.

However, after looking at the code, I retract my comment and caution you not to use Drivebase:

[crypto]
# Generate: openssl rand -base64 32
masterKeyBase64 = "<base64-encoded-32-byte-key>"

If this is a salt or a seed, the documentation is wrong. But it looks like they’re using this base64 value as the actual key for whatever encryption Claude has vibe-coded into it.

base64 values can be reversed very trivially.

Don’t use this.

Regarding the access to cloud, it’s been done with fuse many times and it is very useful for those who need it.

You should know that many of these cloud services claim they “don’t know what’s in your files”, but have been shown to absolutely be able to access them on request from court order or law enforcement. Just saying.