NodeBB-ActivityPub Bridge Test Instance

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

@eeeee I believe LemmyBB was a proof-of-concept, to show that Lemmy as it existed back then was able to be represented in the front-end as a tradtional forum. But also, nutomic (who may have made LemmyBB? not sure.) is a busy person who has a day job and doesn't work on lemmy full-time

Hi @robz@toot.robzazueta.com! (Thanks @beaware@social.beaware.live for bringing this to my attention) You're right, our website is more about our self-service hosting option, and that's because that's what pays our day-to-day bills. It's an unfortunate reality of the open-source development model. The project itself is licensed under GPLv3 and has always been this way. Your concerns over Automattic are well-founded and they also worry me. That said, NodeBB is free and open-source, and you are encouraged to self-host it. That has been our mantra from day one, and still remains that way today.

omega Honestly, I don't think the basics of federation are that big of a problem for people. The idea is simple enough, it's just that it's kind of unthinkable for most folks in the current internet paradigm. "Imagine if you could follow stuff on Twitter, and talk to Twitter users, from Facebook". That captures the whole promise. The whole idea. And it's aided by the fact that Facebook and Twitter are so very obviously different things. Different companies. Different websites. Different apps. Different services. They look different, they're labelled different, their apps are different, etc. And it would be understandable that if they did communicate between them, that there might be some rough edges. Now look at mastodon.social, mstdn.social, and mstdn.ca. They look the same. Try lemmy.ml, lemm.ee, and startrek.website. They look the same. The fediverse has adopted "make every website look like a dumb terminal" as a design aesthetic, and "the website you use doesn't matter" as a recruitment philosophy. And it just doesn't work.

@pfefferle@mastodon.social it was actually because of @ in actor IDs - the codepath for choosing a webfinger lookup over just accepting the URL as the ID only checked for its presence, and the code for webfinger lookups was only meant to run for the acct: protocol. So yeah, not WP fault at all, just a combination of a bug and missing feature Now both should be fixed.