thisismissem@hachyderm.io it was a very weird exchange! I don't understand what that was about.

tom@tomkahe.com That's a fun idea... I'm doing it (using FetchRSS, though) in NodeBB. community.openbeta.io pulls in a bunch of climbing news websites via their RSS feeds and re-publishes it onto fedi

benpate@mastodon.social honestly whatever you ramble on about is always a good show. Stoked you're presenting!

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

nutomic@lemmy.ml let me know if I got any of the details wrong. Much thanks to your team for the assist in debugging!

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

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