The server, though, is made in pretty inefficient python, eating a lot of resources to run. There are rust, c++ and go implementations promising to be less intensive

Seafile, if you want such advanced features as “full text search”.

I kept hating against DoH for this reason and now they’re deploying it without a way out. Or it requires significant extra configuration.

My Samsung device still uses my own local DNS, but I wonder when that will also follow.

This won’t help against the device using DoH

More importantly, when do these hosted html desktops develop a common standard on how to implement the apps? There’s so many now, and none have a common standard on stuff like data access for example. They also all bringt their own small set of mini applications that aren’t very useful.

At least Code has a file system backend implemented for it - but it seems like it’s a file system provider specifically implemented for it?

Because it’s a complicated topic, you’re just feeling the actual responsibilities of doing it right that many are ignoring now.

Why do you call it a media server (on the homepage) when it’s actually just an install script for a media server? You call it an install script truthfully here

It’s just a script that throws a handful of preconfigured config files together, but that should really be (honestly, too) written on the page