Pleroma seems to just keep getting more bloated and every time I see something new I become more and more tempted to just write my own minimal AP server à la Honk.

“ephemeral posts… so we can build Stories”

“video and voice calling are on the horizon”

like, seriously?

@shadowfacts i think people want ephemeral posts for just being ephemeral actually

@314 I can at least see the reasoning for ephemeral posts, but then there’s stuff like LDAP, and stickers, and other stuff that I’m forgetting

and I just miss when software was simple and it was enough for it to do one thing well

@shadowfacts i don't suppose i ever thought of pleroma as the simple or the unixy, but rather as the speedy and the bending spoon
@shadowfacts as for software being simple and doing one thing well, i also fail to remember those times

@314 maybe

but it still feels like pleroma’s doing way more than it needs to

like, are there people who really want video chat over AP but won’t build a separate thing?

which is more important, video chat in pleroma or letting people view posts when JS is disabled?

it feels like the priorities are way out of whack

@shadowfacts this reminds me of my today's visit to #revolutionirc on freenode where someone was subtly annoyed that @MrARM was focusing on other projects instead of adding more features to Revo
like, Revo has a working viable product, from my point of view the things that are left to do are nice-to-haves
@shadowfacts maybe ideally a socnet server would be speaking only s2s apub and c2s apub, and would have pluggable frontends that would speak c2s apub and whatever they want
maybe
but maybe that's not a viable way to develop

@314 that would work, but honestly, if I were just building something for myself, it would be hyper-specific to my needs

like with my blog, the trade-off of specificity saves me a lot of architectural complexity

@shadowfacts yeah I did a lot of working around Hugo static site generator's inner design recently