@eeeee @julian There are topic-specific Lemmy-based websites. startrek.website, ttrpg.network, etc. exist, and function much more like a traditional forum than a catch-all "general purpose" social networking or social media aggregation site, like Facebook or Reddit. And I personally have argued, and continue to argue, that the Reddit model doesn't really work on the Fediverse. That the desire to create a simulacrum of large scale, centralized social media doesn't really scale well once you have multiple websites, and that focusing on a local-first framework is the more logical and more sustainable model long term. I don't think modeling Lemmy communities as being the equivalent of an entire nodeBB website will stand the test of time. The idea that the hosting website matters continues to seep into the thinking of many Lemmy users, and so it should matter to non-Lemmy websites, too. People on Lemmy sometimes ask if there's a way to view communities by hosting site. This is a view that the Reddit-like UI has no natural way of supporting, but forums do. I would love to be able to see remote groups listed as categories in sub-forums ('sections' seems to be the nodeBB jargon?) I've brought up elsewhere, too, about being able to create my own categories-style layout in /world; assigning remote groups to my own pseudo-sections would be amazing. Having the option to have these personalized pseudo-sections show up in the main categories view would be even better. I've also mentioned in the past having a way for regular forum users to 'boost' posts from /world into official forum categories. There are a couple of ways to imagine this, with the most straightforward being just moving/copying the topic into the category, just as admins can currently do. But there's also the cross-post feature from Reddit/Lemmy, where there's a back-link to the original post, and the content displayed in a block quote. I see value in both of those options, though I can't imagine any given forum would want to support both. User pseudo-categories could even be shareable. There's no reason they need to be strictly private (though, of course, users should be able to choose to make them so, if they were shareable). They'd functionally be like lists on Twitter, or custom feeds on Reddit, but with a section/category UI. Or not, I guess -- they could be treated as feeds, too, but I'm kinda sorta very, very over "feeds", personally.

@bentigorlich@gehirneimer.de okay Apologies for not mentioning you up top. I did not know you were the maintainer for mbin, but now I do!

@beaware@mementomori.social @andypiper@macaw.social as I heard from Peter directly, the legal issues also come from internal pressure. Fediverse integration implies giving up control over content, and that's a huge pill to swallow for a company that is literally described as a data silo.

@trwnh@mastodon.social given that one way a context collection is discovered is via reference via a collection member itself, that's one way to define it. Admittedly, direct access to a context collection is also a legitimate use case (e.g. a NodeBB topic URL itself is the context collection), so something more explicit might be required.

@openrisk@mastodon.social not a bad idea. NodeBB actually already does this. We have a configurable max on hashtag usage, and so if a post comes in with > 5 (the default) we just remove everything after the fifth hashtag. They're still in the post content, but only the first five count in indexing, etc.

@silverpill@mitra.social I think given the addressing limitations of collections, this by-proxy method of determining who to send an as:Follow to makes sense as a stopgap measure until ActivityPub's next version...

@naturzukunft@mastodon.social that's what I plan to do at least at a smaller scale with FEPs that deal with threaded conversations

@Jakub-Urbanowicz can you please: create a test account on ActivityPub.academy Run your NodeBB in dev mode (./nodebb dev) mention your account on your forum? Have your forum account reply back. See if there are any errors logged. ActivityPub errors are only logged to console in dev mode.