Not sure if I've posted about this but #mostr bridging to the #Fediverse seems to have been down for some time now.
Discussion
Hey just following up on this, I've been trying to research this issue... my results so far are here:
nostr:naddr1qvzqqqr4gupzptujz495l5qzjfqrzwr0wyenkzhajaq6qah4cuutcfsr5k6e6eclqy28wumn8ghj7mn9waejuat50phjummwv5hsz8mhwden5te0dehhxarj94ex2mrp0yhxgetjv44hymmnwvhx6ef0qythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0qq09g6r9wdjj6snjd9jxwetn948x2ety94tk7unt95u85et8xaaq8cte66
As far as I can tell nostr:nprofile1qqsqgc0uhmxycvm5gwvn944c7yfxnnxm0nyh8tt62zhrvtd3xkj8fhggpt7fy is completely AWOL on this. I'm trying to shift my "bridged" content over to Momostr, but it's not easy.
Sorry, I don't check this account very often.
How have you been trying to get your content bridged with #momostr?
Yeah NP.... Can you read the essay in the previous post, "These Bridges Need Work"?
Basically, what I do is (a) find people on Mostr but (b) follow and interact with them through Momostr.
As far as I can tell, Mostr is still relaying Mastodon posts into Nostr, but not the other way around. So it's kind of deceptive in that it makes users think they can actually talk to people when really they can't.
I've tried notifying Gleason about this but he cussed me out so I'm trying to tread lightly about it. 😶
I'm not sure where that essay it, can you send me a link?
I was looking back at the official #mostr and #momostr documentation and realized I completely forgot that you need to follow the relays for content to federate.
https://soapbox.pub/blog/mostr-fediverse-nostr-bridge/
I know both have had outages of their own, so there is definitely a chance that those broke federation/bridging and caused issues. This explains why some accounts I can view across both networks from #mostr, and why for some I can see them from #momostr.
Just curious, are you posting this on Mastodon or Nostr?
If you're on Nostr, this should reference the original "long form" article in most clients like Amethyst, Coracle, etc:
nostr:naddr1qvzqqqr4gupzptujz495l5qzjfqrzwr0wyenkzhajaq6qah4cuutcfsr5k6e6eclqy28wumn8ghj7mn9waejuat50phjummwv5hsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshszythwden5te0dehhxarj9emkjmn99uqpu4rgv4ek2t2zwf5kgem9wvk5uet9vsk4wmmjdvkns7n9vumh5tz9605
Otherwise here's a Web version: https://habla.news/a/naddr1qvzqqqr4gupzptujz495l5qzjfqrzwr0wyenkzhajaq6qah4cuutcfsr5k6e6eclqq09g6r9wdjj6snjd9jxwetn948x2ety94tk7unt95u85et8xaaq0gn3jk
I'm not sure what you mean by "follow the relays"... That's not quite how it works on Nostr, you can have relays be part of a "relay set" that you use, otherwise you can follow specific npubs (like nostr:nprofile1qqsxhcu0333a7ldlsndha39xumammrgemj3mnq8045v9shzx7p9jd7g7wu50f for instance)...
That being said, I've followed nostr:nprofile1qqsxhcu0333a7ldlsndha39xumammrgemj3mnq8045v9shzx7p9jd7g7wu50f throughout all the tests I describe in my document, and it still doesn't work. So I don't think that's the issue.