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.

@mastodonmigration@mastodon.online while this is a known workaround, I don't think it's a tenable long-term solution. You can have "real decentralization" without the quirks, too.

@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.

@pfefferle Wow, danke für das super Video! Für mich ist das Fediverse noch ganz neu, hab jetzt mein Blog föderiert und mir einen Account bei Mastodon erstellt. Fühle mich noch etwas verloren, aber bin überzeugt auf dem richtigen Weg zu sein

@mario@hub.somaton.com thanks, I tested that payload and it successfully edited the post, so at least from the payload point of view there is no issue. Perhaps there is a problem with the http signature on update? Is that handled differently than a create?

@eeeee I believe LemmyBB was a proof-of-concept, to show that Lemmy as it existed back then was able to be represented in the front-end as a tradtional forum. But also, nutomic (who may have made LemmyBB? not sure.) is a busy person who has a day job and doesn't work on lemmy full-time