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

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

That sounds good

@xbermusic@mastodont.cat can you try renaming the handle to something else and back again?

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

Just a test reply.

> Doesn't this mean Mastodon users et al will no longer get boost notifications when their posts are reshared into a topic? Correct, only OP will be shared. Unless I am mistaken this is how Lemmy implemented it. Announce-ing activities only, and one single Announce(Note) for compatibility with Mastodon.

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.

@rikudou maybe? Nullish coalescing sounds really cool, but I've avoided it for years because of browser compatibility. Node has had support forever (since v14, I've discovered), but I just don't know how to use it is all

Im not familiar with the specs, for now Im only implementing basic OAuth (and only the part where users can login to Ibis with an account from another website). I didnt know about Openwebauth, maybe that could be supported at some point in the future.

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.

I would honestly have been worried if the main people behind the protocol were busy trying to gatekeeep it.

I think you're right

@johnonolan@mastodon.xyz no worries, and thanks! Will do.

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

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

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

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

The numbers are down to 1.3M today, which matches Fediverse Observer. So it seems like this was pretty clearly some data problem on the side of Fedidb. On the positive side, if Fediverse Observer has been consistently correct, the number of monthly active users has increased every month since October last year. So at least there's that.