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.

snoopy@jlai.lu personally, since I create AP enabled software I am on the side of votes being public data. We already have enough issues with votes being out of sync with each other. Mixing in private voting is just asking for trouble. Emoji reactions are neat, although niche to those softwares that utilise it. They allow for greater expression which is nice. They're useless for deriving value (for ranking purposes) unless you assign value to them.

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!

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?

Hey deadsuperhero@lemmy.world have you tried updating to the latest NodeBB? You can post to Lemmy communities from there 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.

I think the FEP process is overly complicated for what it is, but it's definitely helpful if you have multiple implementors on board. The easiest (but least accessible) solution is to document something on your own site, but that lacks the social proof that a finalized FEP has. Just some food for thought I'm looking to create an FEP for cross posting and would love to get the entire threadiverse dev community involved.