Radforum Düsseldorf

bh4-tech that's good to know, thank you!

Can you point me to where Mario is asking for feedback?

> One weakness I have noticed in NodeBB's current federation is that posts which are in reply to a topic (e.g. a Lemmy comment) show up as individual threads until (or if) the root post of that topic shows up in the local NodeBB. No, Lemmy does not implement either strategy, they rely on 1b12 only. If NodeBB is receiving parts of a topic that don't resolve up to the root-level post that might be something we can fix. I'll try to take a look at it.

Yes. When the reply is posted to C, it is sent to A. A then sends as:Announce to C, as well as any other communities that follow it. B seems to be irrelevant here.

Das ist eine Kopie aus dem alten Forum, deswegen stimmen die Zeitstempel nicht. Wollte diesen Vorgang aber unbedingt behalten.

Hey rimu@piefed.social thanks for responding (and sorry for the late reply!) I am not married to the Announce([Article|Note|Page]) approach, so I am definitely open to Create([Article|Note|Page]) with a back-reference. I think I went the former direction because there is a known fallback mechanism — the Announce is treated as a share/boost/repost as normal. However, sending the Create also is fine I think. However, do we need a backreference? In my limited research, it seems that Piefed, et al. picks the first Group actor and associates the post with that community. If I sent over a Create(Article) with two Group actors addressed, could Piefed associate the post with the first, and initiate a cross-post with the remaining Group actors? Secondly, is how to handle sync. 1b12 relies on communities having reciprocal followers in order for two-way synchronization to be established. On my end since I know it is cross-posted I will now send 1b12 activities to cross-posted communities, but can Piefed, et al. send 1b12 activities back as well, in the absence of followers? cc andrew_s@piefed.social nutomic@lemmy.ml melroy@kbin.melroy.org bentigorlich@gehirneimer.de

@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

deadsuperhero@forum.wedistribute.org you can use the latest master or develop branch commits if you want to try out the fix ahead of time.

sir that's just a picture of Eddington.

לאצי the usernames work fine locally (that is, on the site itself). It's when interoperating with other sites not running NodeBB where there are issues, it seems

Das ist eine Kopie aus dem alten Forum, deswegen stimmen die Zeitstempel nicht. Wollte diesen Vorgang aber unbedingt behalten.

phoenix you can always test with ActivityPub.academy, live Mastodon servers can sometimes be delayed.

ska correct, since web-push relies on more modern browser supported technology and doesn't require a third-party service (in this case, ntfy.sh)

trwnh@mastodon.social before, I was not sending Accept at all, now I am sending application/jrd+json.

Erster Tag ohne Blech. Alles freigeräumt. Wenn die Stadt daran beteiligt war, dann sage ich Danke. [image: 1688486535713-20230704_160706_ergebnis.jpg]

I suppose you're right in a way. The context owner is not supposed to be set by someone other than the context owner. It's a fallback mechanism intended for better compatibility with Mastodon. When a group is addressed and it is one of the local NodeBB categories, it will assume control If it is another group that it knows about but isn't same origin to the author, then no category is assumed.

@iso@lemy.lol what's a "lemmy-like" PM I think this explains why I can't log into the site.

ussmojave@startrek.website yeah, I'm watching it now! It's pretty well done.

Thanks! It's something that I personally feel is more performant and future proof for other important things like private discussions (which Mastodon also doesn't support natively yet — mention spamming doesn't count.)