Lastly, there are so many others in the long-form text space who were not at FOSDEM, but are open and willing to work together!

@rimu@mastodon.nzoss.nz (PieFed), @scott@authorship.studio (Hubzilla), Mike MacGirvin (whose handle I forget at the moment) and so many more.

Just because you weren’t here does not mean you were forgotten. Your software was mentioned and discussed too!

@tommi@pan.rent let’s all just give up and keep pressing this button

I should also mention that we had great conversations with the Mastodon team (hi @renchap@oisaur.com and @dave@upp2.com!), and their commitments to working towards better support for long-form text is evident.

Good vibes all around.

@freamon v4.0.1 contains this fix.

@arachnibot@nodebb.arachnibot.com said in Is ActivityPub too complicated?: > Mainly wanted to sync remote group actors to a category for organizational purposes.

Yeah that’s a great use case, and definitely what it ought to be used for. Let me look into nodebb-to-nodebb folllowing, that definitely should be working!

I opened an issue on Lemmy’s repo

https://github.com/LemmyNet/lemmy/issues/5354

The thing is, what is the actual end-result you’re looking for? It sounds like you want stuff from a remote lemmy community to be sent to your NodeBB. If that’s the case, you could just follow the community as a user. Search for technology@lemmy.ml (for example) in the search bar, and once you follow the community, you will start seeing those posts in your /world feed.

The category synchronization options are for if you want to see a Lemmy community’s posts in a category of your own. Might be that’s what you want too.

But at present Lemmy doesn’t support it :)

The logic is a little tricky to get right because there’s a set sequence of steps that needs to happen in order for the group sync to succeed.

For example, between NodeBB and Lemmy:

1. NodeBB admin tries to follow a Lemmy community
2. NodeBB marks the follow as pending
3. Lemmy records NodeBB as a follower
4. Lemmy community tried to send an Accept back
5. NodeBB marks the follow as established.

If steps 1-3 succeed but 4-5 fail, then posts might be sent to NodeBB, but NodeBB will silently drop them because they’re not addressed to anyone it thinks is following the sender.

@freamon thanks for the heads up about lemmy’s accept shenanigans, I’ll take that into account… or maybe ask Felix about it.

@arachnibot @FrankM

@arachnibot happy to take a closer look, since the category sync functionality should be working but might have broken in the interim during development.

Can you let me know the Lemmy community you’re trying to follow from your instance?

Edit: same for you @FrankM

@scott@loves.tech just mention the category actor in a new post and NodeBB will associate it with the category 🙂

@andrew@pythag.net thanks for pointing this out, let me get the user agent updated to report the hostname.

NodeBB right now only reports 4.x though. Exposing the full version could aid targeting for malicious users in the event of a security vulnerability.

cc @tankerkiller125

@altcode@social.vivaldi.net thanks for reporting. It’s a persistent bug that has been evading capture for some time.

For whatever reason, occasionally some accounts will lose their handle-to-id association in the database. That is why you are not able to access the profile page, because NodeBB doesn’t think it exists anymore.

For now the workaround is for me to manually reassociate, but I still have not figured out the root cause of the issue.

testing @altcode@social.vivaldi.net and @vivaldi@social.vivaldi.net

@sabrew4k3@lazysoci.al ah I think I can explain that… an unrelated boost caused my instance to fall over for a little while heh.

@blaze@feddit.org hi! It should. Let me know if it does not.

Except if it doesn’t work you’ll never know I replied 🤣

@silverpill@mitra.social not yet, although I should open an issue, thanks for the reminder!

@scott@loves.tech correct, and while NodeBB has one for publicly available content /api/recent, it doesn’t have one for ActivityPub content… but that can be amended.

However I can’t fault Threads for this too much considering that it’s not really their job to research every implementor and find their public feeds. I simply am surprised by the short-sightedness of assuming that hasMastondonApi == AP server. Most other software would’ve looked at the problem, realized that the fediverse doesn’t consist solely of Mastodon, and approached the problem from a different angle.

… but then again maybe I’m wrong :sweat:

@evfan@feddit.uk @eeeee the federation issue with Lemmy has been hopefully resolved :hand_with_index_and_middle_fingers_crossed: with the latest commit to develop

@evfan@feddit.uk correct, there is a bug with sending replies to Lemmy at the moment.

A lot of the effort I’m championing with the ForumWG deals with combating the inability for Mastodon (and other non-1b12 implementors) to federate content thoroughly. A lot of that is due to design decisions that were thoughtfully made, so this isn’t a critique, per se.

It really does highlight that 1b12 is actually quite good at what it does (federating content out), and that 7888, et al., would be a great complement for post-hoc backfill.