I am once again astounded by how unreasonably effective FEP 1b12 is at federating content completely.
On NodeBB I have a list of “popular” topics, which is mainly populated based on number of posts within a given time period. For most content from Mastodon-based servers, this supplies a decent signal of a given topic’s popularity. The more people you follow, the more effective it is, but overall it’s pretty shit at getting you the whole conversation.
Enter 1b12, Lemmy’s preferred federation method. Follow a community actor and you start receiving everything that happens in that community. Replies, likes, the whole lot.
It also absolutely dominates my popular feed. It’s all Lemmy stuff now because the Mastodon stuff literally can’t compare.
Albeit the SNR is a tad lower, so give and take…
deleted by creator
ok this is half working, seems I can reply to this nodebb post from feddit, but none of the other replies are showing here.
@[email protected] correct, there is a bug with sending replies to Lemmy at the moment.
@[email protected] @eeeee the federation issue with Lemmy has been hopefully resolved :hand_with_index_and_middle_fingers_crossed: with the latest commit to
develop
Thats great, and your reply shows on Feddit!
I’ve signed up for a Lemmy instance to try that, waiting on approval. Lemmy has a box so you can type in answer to question, e.g. ‘Write a line saying why you want to join this forum’ It would be a useful feature addition if nodeBB had this option built in, or on ACP plugins list, because I am still getting a lot of Spam registrations, and without knowing why someone wants to join its still hard to know who to authorise and who to reject
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.