Any particular reason why you can’t do something like host a Send instance instead? Better to treat “filesystem behind the network” and “files to share” as two different things: one is imanent, the other is punctual and sporadic.

Only mostly when I want to. Which tends to be on Mondays and Saturdays.

I’m running Sid on servers, so automatic updates are actually a risk. Used to be Debian Stable, but maaan the docker and podman improvements… make me drool.

Google flags F-Droid updates…

Why would people have Google security going on if they have set up F-Droid as their appstore? Doesn’t that defeat the entire purpose?

There’s a wide gap of stuff one can do between IRC and “chat with voice channels”. For example, having a better protocol with better formatting options, a moderation API, better account management, other forms of multimedia (page embeds, images).

This week I was setting up an IRC server for a group of friends, but might switch it to XMPP. I also have a v good friend who is hosting a XMPP server that sees very little use and has some good lots of legacy stuff going on, I’ll try to ping them to see if it’s worth to spin something completely new.

This is so nice to hear.

What for?

XMPP is quite robust and open, and while it’s not in the level of simplicity of, say, IRC, it still beats pretty much everything else on connectivity and efficiency, and can be run on a potato. Storage is only slighly a concern.

OTOH nu-protocols like Mastodon stuff or Matrix stuff, while they are nice to have, are notoriously badly designed because kiddies these days can’t bother to learn C. This results in highly energy-, memory- and storage-consuming systems. In the amount of RAM I need to kick up a Matrix server (assuming it even runs) I can run ~18 XMPP services and about ~240 ircd services.

Terrified Blanco

Well yeah, it means the system can’t keep torrentin’ stuff!

i am un-admining

Pretty much this. I just manually handle stuff when needed. I already work at IT so this feels quite liberating, the last thing I want is to annoy myself more, and the stuff I manage is not Critical™.

…Huh, it seems I’m quite out of date with the advantages of opus then!

on the scale of YouTube

That’s precisely the trick. Don’t try to copy Youtube. You’re gonna lose. And it’s not the Peertube intended use case anyway.

Instead, Peertube and other such platforms should work as cross-indexing domain-specific, configuration-specific video galleries. A retro videogame video archive does not need 4K 120fps Dobly 14.3 audio; they can just encode most of everything in 480i 30fps and their storage costs will go down significantly. A news report / news reel archive can save some costs by encoding as SDR (or even lower) with ~80kbps mono MP3 audio or somesuch, since most of everything past the intro jingle is human voice.

Play to your advantages. Trying to break into a monopoly game where the rules are broken, the only other player is broken, and the entry fees are broken is self-defeating.

May this be the hoped-for token of enshittification that will spring Peertube and other platforms upwards!

That’s quite senseful yes. In the cases where I want to host somewhere that already has a Postgres service going, I just up and use that.

…How come so few people are using SQLite?

You intendeth to mean Beowulf? I would mayhaps have seen one ere the break of my college time. Wouldst you tell me more about it?

The only part that is wrong TMK is the “indivisible” one; and perhaps the last item because I recall that PulseAudio and Wayland were pushed this way worse than systemd was.

Because it was not always the case that sysvinit was supported - things were sorta “accidentally hazy” for a while. There was a time (I think during Debian 9 and 10) that systemd not only was the default, but was also enforcedly linked against a large part of the stack (you couldn’t have a desktop environment, PulseAudio or NetworkManager without systemd, for example).

This led to the rise of projects like Devuan, that provide a working system that installs without systemd by default; Antix’s nosystemd repo, which allows to install components of the Debian stack without the enforced systemd dependency; and later libam-elogind-compat which aided shimming some of systemd’s requirements under elogind.

Nowadays at least, the only hard part of not using systemd in Debian is 1.- switching (from or to) seems to require rescue mode and 2.- you lose some of the container management goodies (for eg.: Podman services).

None. On Alpine you can only use OpenRC and on Debian you can only use systemd. Most distros don’t let you change out the init system. If you want systemdless Debian look into Devuan.

Fake news. On Debian you can use both sysvinit and openrc (I have six servers on sysvinit, tho I do actually intend to shift them to systemd later mostly because of the container management goodies).

Judging from this post, I would say you should not be looking to change out your init system

Mostly agreeing here. For selfhosting the init system matters barely any, since past the default distro setup one would be doing most of everything with Docker, Podman, etc. At that point, none of the usual Linux religious wars matter much (you can perfectl edit a compose file with nano).

Wouldn’t a zero-knowledge hosting solution (you provide hosting, but you can’t see what’s into it past a stream of binary) help with that?