pretty impressed by fediverse, the technology is cool and there's a nice social atmosphere. seems like most instances are either libtards, heavily /pol/-influenced, or pedos though. would be nice to see less uniformity
Timeline
Post
Remote status
Context
4
@exis7enz The fediblock list essentially re-created the Twitter bubbles, just decentralized.
@PunishedD it almost makes me want to make my own instance. I would be a benevolent mastodon jannie.
@exis7enz @PunishedD >mastodon
Why would you do that to yourself?
Anyway yeah I recommend muting anyone that posts twitter screenshots, it's a strict improvement.
Why would you do that to yourself?
Anyway yeah I recommend muting anyone that posts twitter screenshots, it's a strict improvement.
@Zergling_man @PunishedD oh is pleroma better, interesting
Replies
2
@exis7enz @PunishedD Mastodon is modelled after twitter, and it shows. Twitter was never good, it was a dumb idea from the outset and it's still a dumb idea now.
Pleroma was basically "hey fedi is pretty cool but why the fuck would you copy twitter in anything?"
*That said*, these days I actually find it hard to recommend pleroma, either, primarly because it depends on postgres, which is such a piece of shit that arch just keeps two copies of it in repos at all times to deal with it.
Without actually having used them, I'm more inclined to recommend snac2 (php though) or epicyon (python though), but there is also always misskey and its 50 million forks (none of which I recommend, because forks die, that's what they do). Misskey is good if it is important to you to have a setting on user accounts to add cat ears to their avatar.
Notably pleroma mimics mastodon's client-server API so it just picks up mastodon clients for free, but a lot of those tend to just assume things rather than actually check what the server reports, so you tend to get limited experience even on pleroma instances. However, many clients also support misskey API, and that tends to check server settings. Occasionally they copy that behaviour to masto side.
Pleroma was basically "hey fedi is pretty cool but why the fuck would you copy twitter in anything?"
*That said*, these days I actually find it hard to recommend pleroma, either, primarly because it depends on postgres, which is such a piece of shit that arch just keeps two copies of it in repos at all times to deal with it.
Without actually having used them, I'm more inclined to recommend snac2 (php though) or epicyon (python though), but there is also always misskey and its 50 million forks (none of which I recommend, because forks die, that's what they do). Misskey is good if it is important to you to have a setting on user accounts to add cat ears to their avatar.
Notably pleroma mimics mastodon's client-server API so it just picks up mastodon clients for free, but a lot of those tend to just assume things rather than actually check what the server reports, so you tend to get limited experience even on pleroma instances. However, many clients also support misskey API, and that tends to check server settings. Occasionally they copy that behaviour to masto side.
@Zergling_man @PunishedD @exis7enz
>primarly because it depends on postgres, which is such a piece of shit that arch just keeps two copies of it in repos at all times to deal with it.
Filtered by the DB :D
If you run Arch on your servers, I think you are genuinely insane and need help. The reason why there's always two versions is literally only for upgrades between major versions which you barely have to think about.
Anyways, snac2 is nice, but the codebase is hacky and handling completely arbitrary free-form data in C is a recipe for disaster waiting to happen. Especially with the custom built JSON parser. If you want a small single-user instance I would also recommend Mitra besides Pleroma, but that also uses Postgres. GoToSocial does sqlite, but is such an annoyance to federate with that I don't recommend it just based on that.
>primarly because it depends on postgres, which is such a piece of shit that arch just keeps two copies of it in repos at all times to deal with it.
Filtered by the DB :D
If you run Arch on your servers, I think you are genuinely insane and need help. The reason why there's always two versions is literally only for upgrades between major versions which you barely have to think about.
Anyways, snac2 is nice, but the codebase is hacky and handling completely arbitrary free-form data in C is a recipe for disaster waiting to happen. Especially with the custom built JSON parser. If you want a small single-user instance I would also recommend Mitra besides Pleroma, but that also uses Postgres. GoToSocial does sqlite, but is such an annoyance to federate with that I don't recommend it just based on that.