@FrankM Vielen Dank, das wird definitiv helfen, den Fehler zu finden! Ich habe hier einen Fehlerbericht angelegt: https://codeberg.org/forgejo/forgejo/issues/7614Weißt du bei welchem repository/welcher Datei das passiert und möglicherweise welcher git blame das auslöst (gerne auch im Issue antworten)?~ @mahlzahn

@_DigitalWriter_ Kann man einfach besser lesen, vor allen Dingen im Alter

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

I just realized that while we now have the ability to browse and follow remote communities, we don't have a page listing communities ordered by popularity or recency... time to add to my ever expanding list

@trwnh@mastodon.social sure, makes sense. That to/cc already exist in the wild as arrays means one less thing to worry about with multiple cross posts.

@jsonculverhouse@flipboard.social yes, that's right. If a Flipboard post is organized within magazines, then including the magazine in the cc will allow recipient software to correctly slot the post with the magazine. So not only would it fix the issue for NodeBB, it'd also fix it for Lemmy, PieFed, Mbin, etc.

@AltCode This should be fixed in the upcoming v4.3.0. https://github.com/NodeBB/NodeBB/issues/13352 It won't proactively remove the duplicates, but they'll be pruned out within ~7 days.

Good lord @liaizon@social.wake.st did you just necro a 3 year old topic