No problem at all reiver@mastodon.social thanks for doing this hard post-conference work!

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.

Hey deadsuperhero@lemmy.world have you tried updating to the latest NodeBB? You can post to Lemmy communities from there too!

m_f@discuss.online not directly, but there was a session at FediForum on Thursday that discussed the website and next steps for updating it. It's been stagnant for quite awhile but evan@cosocial.ca and j12t@j12t.social finally have write access to the repo and control of the domain.

PewDiePie built his fame and fortune on a centralized platform. I am not certain whether he will see the benefit of a decentralized future beyond dollar signs. Happy to be proven wrong.

I would say that Pixelfed is closer to the microblog space than it is the threaded discussion space. It's essentially microblogging except with an image media focus (or video, in the case of Loops.) To each their own, some people communicate better using pictures, some better over short text, some better over long-form text. There's a space for them all

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

@thisismissem@hachyderm.io ah understood. I didn't quite get how the fund worked, but it makes more sense now (and is much simpler—organizationally—for Nivenly!) I don't think we'll add exclusions for security fund recipients I would say, though, that one of the requirements has to be that the affected software accepts the vulnerability. Plenty of self-proclaimed "security researchers" have filed reports, and some go as far as to publish CVEs (against our own software!) without our permission. Quite the opposite of responsible disclosure.