things i would like to see in mastodon that pleroma has been able to do for years:

[ariadne@social.treehouse.systems]

@ionizedgirl @UntaggedTransmitter akkoma is basically a hard fork at this point and exists because of this specific problem

[delta@mk.absturztau.be]

@[email protected] @[email protected] i can confirm, pleroma's database design is not great, i have a 1.5 year old single user akkoma instance with a 10gb database, and have known many akkoma/pleroma admins who've had to deal with the rot as it is colloquially known

pleroma/akkoma in general, has good features and ideas but its all built on top of a foundation made of sand and spaghetti, it works most of the time but you best hope there is a god to save you if you ever have to debug or fix a technical issue in the thing

admin-FE is also just kinda terrible, it works and thats the most that can be said about it, it is a pile of barely sorted settings, excluding the ones that aren't in there

[ariadne@social.treehouse.systems]

@delta @ionizedgirl i've considered forking Pleroma before and fixing the database to use normal SQL relations to represent the data and just accepting that a universal AS2/AP server probably isn't feasible at scale

[ionizedgirl@toot.cat]

@ariadne @UntaggedTransmitter does that mean it's missing the tools you listed

[ariadne@social.treehouse.systems]

@ionizedgirl @UntaggedTransmitter no, akkoma has the full MRF framework with all of the things i listed

[ariadne@social.treehouse.systems]

@ionizedgirl @UntaggedTransmitter (though akkoma seems to be kinda dead anymore)

[untaggedtransmitter@aberrantwinds.bond]

@ariadne @ionizedgirl
Akkoma existing is pretty much the whole reason I see Pleroma derived software as worth looking at. It would almost certainly be my software of choice if I was standing up a new fediverse instance at this point.

[ariadne@social.treehouse.systems]

@UntaggedTransmitter @ionizedgirl i wouldn't bother. when i ran pleroma.site, the database broke several times, and it took *days* to rebuild it each time.

[untaggedtransmitter@aberrantwinds.bond]

@ariadne @ionizedgirl
Sad to hear that akkoma is looking dead.

Also, I didn't know you ran pleroma.site, I had an account there for a bit!

[ariadne@social.treehouse.systems]

@UntaggedTransmitter @ionizedgirl mastodon is pissing me off to the point that i'm likely to make my own soon. part of my reason for using mastodon was to motivate me to build something from scratch.

[tusooa@kazv.moe]

@ariadne @delta @ionizedgirl pleroma forces all posts to pass a validation function before storing it in the db. you still only get what is supported by it though. unsupported params are dropped.

[ariadne@social.treehouse.systems]

@tusooa @delta @ionizedgirl yes, which just makes me wonder why it still has this terrible object store design

[spacelifeform@infosec.exchange]

@ariadne

Interesting thread.

How does Glitch-soc stack up?

cc: @jerry @paco

[ariadne@social.treehouse.systems]

@SpaceLifeForm @jerry @paco equally deficient

[thisismissem@hachyderm.io]

@ariadne rejecting content based on hashtag has been on my list to do for Mastodon, but needs this activitypub issue resolved: https://github.com/w3c/activitypub/issues/424

This was an early attempt at this in Mastodon: https://github.com/mastodon/mastodon/pull/29264

Just silently dropping the message may not be the best option, hence needing community consensus on best practices

[paco@infosec.exchange]

@ariadne @SpaceLifeForm Glitch is just a small patch to core mastodon. Mostly about UI improvements.

[ariadne@social.treehouse.systems]

@paco @SpaceLifeForm thank you for explaining glitch to me, as somebody who uses glitch already

[paco@infosec.exchange]

@ariadne You were CCed, effectively. I was answering @SpaceLifeForm who asked the question and tagged me into the conversation. I didn’t take much care to move userids around to make it clear who I was addressing. Sorry.

[ariadne@social.treehouse.systems]

@paco @SpaceLifeForm no worries, sorry for being snippy

[finchhaven@infosec.exchange]

@thisismissem

This is interesting, but raises several questions for me (not that I'm anyone) that I've not seen addressed

Maybe early days in the larger issue, or something

Is this seen as content rejected because it contains $Word only, or content rejected because $Word is used in conjunction with a hashtag?

Who curates the list of $Words?

Then, a further question because of "Create a global default text filter to help prevent the use of racist and abusive language (Issue #31182)"

What language will the "global default text filter" list be kept in?

What becomes of other languages, which can be equally problematic on their own or in translation?

cc @ariadne