for me it was the fact that the desktop case i used for the server had the power button on top and it was big enough to be pushed in, when my cat walked over it…

i might be a more typical nerd. i have a phd in physics and took a bunch of computer science course out of interest/boredom.

but i never learned anything that is really related to hosting. containers were not really a thing at the time and most courses i took were much more fundamental, like basics of networking or cpu scheduling. programming a learned on the fly to solve a problem, never as actual task in itself (what is very typical in my field and leads to horrible program code/collaboration scheme)

if not for the forced installation of the official client, it would really be neat. with a telegram bridge i also have good experience, only a single hiccup, years ago.

i have Whatsapp in a frozen shelter to starts it every two weeks.

recently i was thinking to have a second home server just for bridges, you should be able to use it federated. but didn’t try it yet.

main point for me was the sheer amount of ghost users.

one Location for dozen of rss feeds instead of looking up each individual. alternative is of course setting up the feeds on the client computer, but that works only nice if you use it only from one device (e.g. read history sync).

furthermore i prefer to have such set ups on a server with backups, so if e.g. my phone gets lost i don’t need to find back all those urls.

I’m using matrix for years with my wife and my mom, never really had issues, but maybe my requirements are not that high.

i tried all three for my personal use. so i can’t say much about collaboration aspects. anyway:

• gitlab is old, stable and solid. and it eats half of your servers resources.
• gitea and forgeji are for me equal in experience, which is makes sense, as one being a fork of the other. i haven’t had any issues with anything, from setting up, using openid as auth method, to ssh passthrough.
• eventually i settled now on forgejo, simply for ideology reasons. it’s heavily developed, so things might change. but they have this nice attitude to not release a latest tag for docker. so you can’t accidentally update to a breaking change. had this issue with some other programs, which i spun up to quickly.
• looking forward to federation feature on forgejo!

custom OS shouldn’t be effected by it. I’ll probably change soon as well.

anyway, that is rather independent on the petition. a petition is usually not for your own short term benefit, rather for the common good, or outreach of the general problem. so doing either is for different reasons, both reasonable

here it makes at least some sense to verify that each person voted once. the mail list stuff is of course to much and should be optional from the beginning.

wait… there was a v2.* ? feels like yesterday that i read about the release and wanted to check it out since

never saw the s argument and was curious what’s the difference to d. man pages are way ahead of me ^^

--max-depth=0 is the same as --summarize