While the mostr.pub bridge isn't fully recognizing the account yet, we can now say that @619edd6f is the first Threads account that's bridged over to Nostr!
I sent over a merge request to update Mostr's regex check to support the formatting used by BridgyFed's Bluesky <=> Mastodon bridge. This would in theory allow Bluesky profiles to be more seamlessly bridged to Nostr through BridgyFed/Mostr!
haha it's very much a work in progress! To clarify, the Lemmy functionality is only partially bridged. What that means is, the first step of pulling in posts based on topics uses the Lemmy API directly, and it's only when clicking on a post to be directed to that Lemmy community when the bridging occurs.
That bridging of Lemmy community into a Nostr profile is done primarily using @alex 's awesome Mostr.pub Nostr <=> Fediverse bridge. While it doesn't fully support Lemmy yet (more Mastodon focused), it works decently well! As a fallback, I use RSSLay to generate a nostr profile from the rss feed of that Lemmy community.
Thoughts on why there's such a huge difference between total users and monthly active users for Lemmy, especially compared to Kbin? Did Lemmy just get a huge number of bot accounts made that aren't active?
The protocol (AT Protocol) is basically activitypub except more seamless switching between instances and following people on different instances isn't a clusterfuck like on Mastodon.
Bluesky is just a client for the AT Protocol, like Damus/Amethyst/Snort etc
Hmmm, maybe the relay could detect when a specific string is being posted in quick succession by any pubkeys period, and block posts that contain that string, at least temporarily.