tchambers@indieweb.social this, in a nutshell. The fediverse vid AP can support both A and B, and we can wax poetic about how one is superior to the other but both are legitimate UX decisions by their respective software stacks. I prefer B myself, of course. cc tommi@pan.rent j12t@j12t.social

Tell me about it! There are some very cool people (i.e. thisismissem@hachyderm.io) working on content classification and tagging so that the burden of filtering out this kind of content isn't borne by server admins directly.

Very interesting article! I have immense respect for jerry@infosec.exchange, he was one of the first people I found on the fediverse, and it's no wonder why, he's revered quite highly by others as being a generous and kind admin. I do want to point out one thing, and that is that Mastodon has some design decisions that make it rather resource and storage intensive. There are oodles of lighter software out there, some with even more features than Mastodon, and some with less. For example, snac.bsd.cafe (https://snac.bsd.cafe/) runs on Snac, which is fast as hell. I am going to guess that a not insignificant portion of Jerry's bill is caching assets. Mastodon likes to save everything it encounters, videos, images, avatars, everything... forever (though I imagine this is customisable). Most likely the assets are viewed a handful of times in one day and never seen again... but you'll pay to store it forever!

There's NodeBB if you want a forum/BBS style UX for the threadiverse!

For what it's worth your blog does show up fine in NodeBB as well. Perhaps you are missing the @context property and so Mastodon is refusing to parse it?

rwg@aoir.social I'm not actually sure! You'll have to ask reiver@mastodon.social about that one. Let me know too!

blazeknave@lemmy.world beep beep boop boop boop boop beep... EEEEEEEEEEeeeeeeee awwwwwww ka-dong ka-dong da kshhhhhhhhhhhhhhHHHHHHHHHHHHHHHHHHHHHHHHHH eerie silence

melroy@kbin.melroy.org oh sorry to hear that hopefully Dan hasn't moved on from FediDB already.