Today we were made aware of multiple Fediverse blog posts incorrectly attributing “vote Trump” spam on Bluesky to the Mostr.pub Bridge.

This spam is NOT coming from Mostr. From the screenshots used in these blogs, it's clear the spam is coming from an entirely different bridge called momostr.pink. This bridge is not affiliated with Mostr, and is not even a fork of Mostr. We appreciate that the authors of these posts responded quickly to us and have since corrected the blogs.

Mostr.pub uses stirfry policies for anti-spam filtering. This includes an anti-duplication policy that prevents spam like the recent “vote Trump” posts we’ve seen repeated over and over.

It is important to note WHY there are multiple bridges, though.

When Mostr.pub launched, multiple major servers immediately blocked Mostr, including Mastodon.social. The moderators of Mastodon.social claimed that this was because Nostr was unregulated, and suggested to one user that if they want to bridge their account they should host their own bridge.

That is exactly what momostr.pink, the source of this spam, has done.

The obvious response to the censorship of the Mostr Bridge is to build more bridges.

While we have opted for pro-social policies that aim to reduce spam and build better connections between decentralized platforms, other bridges built to get around censorship of the Mostr Bridge may not — as we’re already seeing.

There will inevitably be multiple bridges, and we’re working on creating solutions to the problems that arise from that. In the meantime, if the Fediverse could do itself a favor and chill with the censorship for two seconds, we might not have so many problems.

Reply to this note

Please Login to reply.

Discussion

I see your tactic for shutting down the competing bridge. Nasty.

(this is a joke)

Mastodon: *Blocks nostr:npub1d03clrrrma7mlpxm0mz2dehmhkx3nh9rhxqwltgctpwyduztymustepzfs bridge*

User: "How can I bridge my account to Mastodon then?"

Mastodon: "Host your own bridge"

User: *Hosts own bridge*

Mastodon: "nOt LiKe tHaT!"

nostr:note1zfjvcsz3mdv6lx3p7l7sq87l2gf5yn643656k94pkq20eg39pt6sjl50vj

Yea...I was a victim of the mostr.pub mass blocking on Fediverse because it was added to a public blocklist without anyone knowing. So I accidentally blocked it for awhile and now my account can only be federated with Momostr.pink

This apparently causes issues when trying to interact with fediverse users who are bridged with Mostr.pub because the bridges don't interact. Therefore, the conversations with those users on Fediverse don't show up on Nostr.🤦