ActivityPub

> Just from a cultural homogenization point of view, it’s been a negative. You’re not wrong, and so I think the future of this is meant to be opt-in rather than opt-out. Realistically what a two-way opt-in looks like would be: A topic is created A cross-post request comes in OP (or mod) approves or rejects Topic is cross-posted. However that in general introduces a significant amount of overhead and mental burden that would disincentivise usage of cross-posting. I’m not sure what the answer is. I used to be very bullish on the idea that cross-posting would solve so many problems via inteconnection, but there are some very significant social concerns that would absolutely taint the very idea. So, we tread carefully.

Hey @approxinfinity@community.nodebb.org! Long time no see You guys will always have a special place in our hearts, because you were one of the very first people who put their trust in NodeBB. Waaaaayyyy back when we were a scrappy little forum project run by a couple of guys, you trusted NodeBB to power your forum. I think that probably makes kubuckets.com one of the oldest NodeBB forums still running (although I think community.nodebb.org probably beats you by a bit)! That you’ve discovered ActivityPub on your own and found the NodeBB connection is just great we’re around as always to give you a hand!

The Discourse ActivityPub plugin is developed by a sole developer but I believe it is ready for use. I also believe he is still working on the plugin so that’s positive news. Federation with Discourse forums is tricky, it’s been difficult getting NodeBB to work reliably with Discourse. Are you able to load Discourse categories in Lemmy?

informapirata indeed! This is configurable under the site-wide ActivityPub settings under “auto categorization rules”. For that site I have hashtags like “ActivityPub” and “fedimod” set up to automatically categorize discussions. It only matches for discussions that don’t already have a category of their own (so, microblog stuff.)

rimu@piefed.social I’ve been using web+acct for the acct URI format. https://en.wikipedia.org/wiki/Acct_URI_scheme

Jon-Pincus hey check out that topic loading from within this NodeBB cc admin@discussions.thenexus.today

trwnh@mastodon.social yep exactly that’s what I was going for. If you paste an URL to an ordered collection into NodeBB it’ll try to load the thread. That’d be ideal. But I will settle for understanding name and summary!

@julian Also, speaking of fixable deficiencies, my edits here don't seem to propagate to SocialHub . Without knowing the code I'm confident it's fixable because my edits did propagate to the NodeBB thread at https://community.nodebb.org/topic/18932/final-thoughts-re-fedicon-2025/14 , great to see!

Jon P said in Fedicon Livestream: > nteresting. I usually see social networking defined as a subset of social media. Indeed. This is how it’s often used in the social sciences that study online activity. Social Networking Sites are sites like Facebook, that require account following, or even bidirectional follows, while “social media” is everything from BBSes to forums to blogs with comment sections to, well, Social Networking Sites.

Furbland-Channel-2 Looks like it’s working now after some updates. The request stayed pending until I unfollowed and followed again. Maybe add a way to check and fix this automatically. Also, I wish I had more reputation to post faster!

evan@cosocial.ca that’s cool, so hopefully I’ll have something to test against besides another NodeBB server

> Getting a critical mass of people to create yet another account was always a major obstacle. I see and have experienced this effect time and time again, and we’re getting closer and closer to the point where the protocol implementations can abstract away the messy bits. Gaining critical mass among devs is the first step!

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.

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

julian@community.nodebb.org Yeah, being able to treat Mastodon and Lemmy/mbin/piefed like a bulletin board continues to feel like magic.

goten@piefed.social hi, from NodeBB !

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

לאצי 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