Not quite, it's the issue with the "invalid post id" error. Is it also accompanied by the post not federating out? That's interesting...

@andreasgoebel Ich bin aktuell auf einem Manjaro Testing mit KDE Desktop und habe den Desktop so eingerichtet, wie ich mich wohl fühle. Wenn ich vor einer Neuinstallation stehen würde, würde ich Fedora eine Chance geben.Aktuell richte ich Fedora 42 so ein, das ich mal einen "Notfall-PC" habe, wenn der erste rum zickt

@heiseonline Warum glaube ich nicht, das das stimmt? @ccc Bitte überprüfen.

@radkolumne #Autojustiz

To give a little bit of context from another implementation, NodeBB implements a follower system like ActivityPub. Out of the box we don't have the concept of "friend", but if we think of the usage as that of early Facebook, then a "friend" relationship implies a reciprocated follow... similar to a LinkedIn "connection". In AP-land, that'd be a follow-accept and then a follow-accept from the other direction. Whether this is completely automated or manual is dependent on the implementation, I suppose.

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

@reiver@mastodon.social apologies if this is inappropriate to ask, but has there been any thought given to speaker fees? I'm enthusiastic about ActivityPub and love to speak about it, but I'm not in an secure enough place financially to fly myself to Vancouver without some sort of arrangement in place.

@silverpill@mitra.social it sounds like @fedify@hollo.social was generating one activity for each recipient, which if combined with relatively heavy database calls, would scale quite poorly, even when processed asynchronously. Batching those db calls is always a low hanging fruit in terms of code optimization.