ActivityPub

I'm seeing issues with loading remote categories. I can't load the NodeBB bug reports category at all, and for the ActivityPub category, I can find it in my world category search, but I get a 404 when trying to load it. Also can't load general-discussion@community.nodebb.org for example. It seems the NodeBB development board is the only one really federating for me. Any way I can solve this? I am running beta2 of 4.3.0.

@jsonculverhouse@flipboard.social yes, that's right. If a Flipboard post is organized within magazines, then including the magazine in the cc will allow recipient software to correctly slot the post with the magazine. So not only would it fix the issue for NodeBB, it'd also fix it for Lemmy, PieFed, Mbin, etc.

@AltCode This should be fixed in the upcoming v4.3.0. https://github.com/NodeBB/NodeBB/issues/13352 It won't proactively remove the duplicates, but they'll be pruned out within ~7 days.

I recognize that this makes the Delete activity work differently for S2S than it does C2S, which is to say that a user or client cannot distinguish between "soft delete" and "hard delete" this way. Otherwise, the "cache invalidation" idea is a sensible one.

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

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

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

@raphael@mastodon.communick.com great!

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

@kirk@social.coop just wanted to drop a note that your two issues have not been forgotten

Yep, everything works!

I think you're right

@Kichae said in Organizing the many worlds you're part of through NodeBB: > But man, do I ever desperately want the bulletin board experience in /world. It really feels like what the fediverse was always meant to be, to me. I've been inspired by some teaser images from @johnonolan@mastodon.xyz's Ghost blog, which physically segregates microblogging content apart from long-form content (e.g. blogs). Forum topics fit somewhere in the middle, although since title and body are present we tend to align more with long-form content. It's a really neat idea I'd like to play around with more.

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

Just wanna add to this convo that we've been working with interaction policies in GoToSocial for a while now, and the protocol extension described here is extensible to include a canQuote property on an interaction policy: https://docs.gotosocial.org/en/latest/federation/interaction_policy/Reply, Like, and Announce controls and approvals etc are already running in GoToSocial since v0.17.0 last year. It would be pretty neato if Mastodon could reuse the interaction policy properties and approval flow for quote posts, insofar as that's possible. Have discussed this in the Mastodon discord with Claire as well, but just putting it here too.

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