This is your sign to find a smaller instance and support that one instead. Or, maybe even go the selfhosting route and setup a GotoSocial instance for yourself.

“Do you have natural freckles or did you use that shoulder-mounted guided missile prototype again?”

The main problem here is persistance. Most users are on machines that get turned off.

This! It only works if you have a server that’s online 24/7. Can be a VPS in a data centre, can be some Raspberry Pi running at your home with a DNS name pointing to it.

If you are not a Gitea customer, you are not being informed of security updates in a timely manner

I don’t need a notification of issues, I need a notification of when there’s a new version to roll out. And that can be solved by using things like WatchTower or setting up release notifications on GitHub.

And, of course, a comparison hosted on ForgeJo’s webpage will make it out that they’re “the better choice”.

Also, ForgeJo was promising federation which is still a WIP several years later.

Oh no, it doesn’t do the big feature™. I guess it’s unusable now.

Well, that was the one big distinguishing thing between the two, back when ForgeJo was the new kid on the block. ForgeJo wanted to make it a priority to implement federation.

And I never said it’s unusable - it’s just that I, personally, don’t see any reason to switch from Gitea to ForgeJo.

I’m staying with Gitea. They’ve created the Ltd. so they can sell professional support as most businesses will want a proper invoice. I don’t see anything wrong with that. Also, ForgeJo was promising federation which is still a WIP several years later. And, the one time I’ve tried ForgeJo it shit itself when I’ve added an emoji to my username. For some reason Gitea didn’t have any problem with that.

It works in both directions. I’ve been shadowbanned from mastodon.social because one user misinterpreted my comment about something political (related to Germany), reported me and apparently their (German) mod was either lazy or followed the same misinterpretation and shadowbanned me - for life.

And there’s no way to object this as their support only answers to members. Which I am not.

Meshtastic has issues with all those repeated status messages eating up airtime. Meshcore seems more reliable. And there’s also Reticulum.

Yep, and an especially fun fact is that people with high-end equipment prefer MP3 over lossless.

But did they use oxygen-free copper (OFC) wire? Because otherwise the results are skewed as regular copper sounds just as bad as a banana stuck in wet mud.

Interesting! Thank you for that insight. I might adopt some methods for when I finally replace the Synology with a new NAS (which will definitely not be another Synology device!).

How often do you change your storage setup? I’ve configured everything once like 5 years ago and haven’t touched it since. I can add larger disks in pairs and the Synology does some LVM-/mdraid-magic to add the newly available free space as RAID1 until I add a third larger disk and it remodels it to RAID5.

How do you handle parity with MergerFS? Or are all your storage partitions mirrored?

Hard drive storage is pretty cheap.

Not really - especially, if you’re looking for CMR drives. And any storage increase needs at least 2 disks with basically no (ethical) way to get any money back for the old ones.

Agreed. However, mirroring the remaining disk onto a new one makes it more likely for it to fail, too, I guess?

I think the more important rule would be to not buy two disks from the same batch. And then go with whatever tickles your fancy.

Posts can also get synced if someone from gram.social searched for a direct link to a post. E.g. if you go to gram.social and search for https://pixelfed.social/p/pixuser/1234, it’ll get synced in the background and show up if you follow @pixuser later on. (Depending on how long the instance caches it.)

Likes and Reshares of external posts are local to their instance. Those won’t get sent to other instances. E.g. on my private GotoSocial I don’t see the correct amount of likes or reshares of posts from other instances. I’ll have to visit the posts on their original instance for that. (But then, I rarely care.)

Rebuilding parity requires processing power.

That shouldn’t be an issue with any NAS bought in the past decade.

the rebuild stresses the drives

You can tweak the parameters so the rebuild is being done slower. Also, mirroring a disk stresses the (remaining) disk as well. (But to be fair, if that one fails, you’ll still be able to access the data from the other mirror-pair(s).)

It all results in management overhead

I’m not seeing that. Tweaking parameters is not necessary unless you want to change the default behaviour. Default behaviour is fine in most cases.

In comparison […] RAID is a headache.

Speak for yourself. I rather enjoy the added storage capacity.

Fediverse works like newsletters via email. If you search for an account on a different server, only the last few items are (sometimes) pulled and shown on your local instance. Only after subscribing/following that other account, you’ll get new(!) updates sent to your local server. For older messages, you’ll have to visit the other account’s server.

Maybe those 2 photos you see were shared with gram.social earlier.

Now mostly you either use striped mirrors

How is rebuilding an xx TB mirrored disk faster than rebuilding an xx TB disk that’s part of a RAID? Since most modern NASes use software RAID, it’s only a matter of tweaking a few parameters to speed up the rebuild process.

For #1 a quick search spat out this.

For #2 have a look into XPenology.

Not to be confused with the original Web Intents.

They’re doing test rides already.

micro?