It's not a NodeBB in particular but it's worth mentioning another mismatch: Misskey and forks will also delete replies when a post is deleted.

@hamishcampbell @ricmac @evanprodromou @julian Thanks for your kind words. I won't interrupt your discussion with Julian anymore. I hope you reach some accord!

In principle that sounds like a problem with NodeBB or other platforms you are using. Lemmy doesnt do anything special to fetch remote communities. But if you notice any error responses served by Lemmy you can open an issue.

@thisismissem damn @Sarahp killing it with the fediverse coverage lately!

The remaining questions here are: whether preferredUsername is meant to be unique to the instance (in which case having multiple ids point to an identical preferredUsername would be a violation), and what exactly AP software should do when it encounters this situation... store a list of "known alias" IDs? There are potential security issues to doing so.

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

@julian we have recently rewritten the addressing logic and it seems mapping the mentions to to for public toplevel posts has fallen short. After fixing this it seems to work fine now: #^https://community.nodebb.org/topic/cbbf1640-2295-4fc5-b86f-5b1fd259cccb/test2@Scott M. Stolz

@julian Nevermind! Typo in the header...

@raphael@mastodon.communick.com hmm interesting, can you share the code that's making the call? Usually if it's working with curl it'll work with Node, so this suggests there's something different with the way the call is made with node. For what it's worth, internally, NodeBB uses the built-in fetch method from Node.js.

@julian Thanks, tells me what I needed to know. Even on Mastodon I only really use Hashtags on posts and not on replies so that tracks for personal usage.

Thanks for the confirmation @jsonculverhouse@flipboard.social, any chance we could have the post list the magazine as a recipient, so that a backreference is established? See: https://community.nodebb.org/post/104013 @mike@flipboard.social mentioned you, but a typo got in the way

@julian or, rather, if you stretch the concept a little bit, every outbox could represent a "category", just with unknown rules

@AltCode One significant potential issues with listing all followed categories in the same kind of layout as /categories is the below-the-fold effect, or the page-2 effect as one might have called it in earlier times. Whatever categories end up falling below a certain scroll distance will just never been seen by most users. If you follow a lot of categories, the ones that end up closer to the bottom of the list than the top will just end up ignored. It doesn't encourage participation, and it also doesn't discourage following a lot of categories that you don't actually care about. And follow relationships are very important under ActivityPub, since they dictate content flow. Bringing in a lot of remote content that no one on the local forum is actually reading or engaging with is very wasteful. An easily accessible compact list might be better, with different sorting options so that users can choose to have categories with new content float to the top. Usually with forum categories, you want the ordering to be static, but that expectation won't necessarily be there for just a list.

My first experience with Federation was with Calckey, (fork of Miskey.) I liked some things about it, but there were forks of forks and I never knew in the end which variant of it was best to use

I asked in that issue whether Lemmy finds community via to/cc (it does). Does PieFed do the same? Yes - PieFed does the same. It looks in 'audience', then 'cc', then 'to'. It has to, to support all the platforms that haven't adopted 'audience. It's a convenient field, but PieFed won't be affected if Lemmy goes through with removing it. Would this also open up the possibility of a topic/context being part of multiple audiences/communities? Not at present. If you do something like cc: [community1, community2] it will only go to community1 (on both Lemmy and PieFed). There's so many activities that are effectively duplicates, both in normal operation and when platforms are bugged (both Lemmy and Mastodon have gone through phases of sending the same activity multiple times), that you need a way to make sure you're only processing one. On PieFed, this is done by having a UNIQUE constraint of the 'ap_id' column of the Post table (the ap_id of your post is https://community.nodebb.org/post/103806), so it means you can't have the same post in more than one community.

Yea, odd, I made a second account on mysite and that follows and unfollows normally. So its a mystery why my first Admin account is doing it differently. Maybe one day we will figure out whats altering the behaviour

That sounds good

Hi @julian@community.nodebb.org! Sorry to revive such an old thread. Is this still the case with nodebb 4 with ActivityPub? I vaguely remember that in other ActivityPub software it's somewhat problematic to change hostname.