mbirth

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.

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.

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.)

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.

For #1 a quick search spat out this.

For #2 have a look into XPenology.

Not to be confused with the original Web Intents.