#[0]
Good evening. We have an amazing business opportunity for you tonight.
#[0]
You need webfinger and an inbox. And endpoints to fetch objects. Thatās about it.
This was an excuse, and really not the real reason. He misunderstood how federation works and was speaking theoretically. It isnāt a resource hog, they just didnāt like what theyād see.
Few things make me as violently angry as scammers/spammers. Itās pure selfish destruction instead of creation, primarily with the aim of slowing down people who are building a better future. So yeah, Iām going to fight back.
You need their pubkeys, which you can get by pinging mostr.pub/.well-known/nostr.json for each of them.
Hey guys there was a problem with the bridge that required the data to be reset.
1. If you were following Nostr users through the bridge: unfollow and refollow them again.
2. On the Nostr side, you'll want to unfollow the old account and refollow the new one by looking up their NIP-05 identifier (eg alex_at_gleasonator.com@mostr.pub )
The problem has been fixed and shouldn't happen again. Thank you for using this beta software!
How many clients actually support NIP-26 (contributed by Minds)? https://github.com/nostr-protocol/nips/blob/master/26.md
Also wonder if any relays return events by the delegator when you query for that author.
#[0]
But who and how? Surely she has more information.
#[0] help us be a detective.
Posting the photos is pure evil.
hey #[0] mostr AP-side usernames for the nostr side sux dlux. Shit needs to get fixed. You already have NIP05 support for bridge participants (eg https://nostr.sharivegas.com/ShariVegas_at_pleroma.nobodyhasthe.biz@mostr.pub ), how about aliasing the other direction? (eg: @sharivegas_at_nostr.sharivegas.com@mostr.pub )
Could we utilize the alsoKnownAs property and expect it to work in Mastodon/Pleroma/Soapbox?
The only way to fix it is by exposing a new property to the frontend and patching it there. Every client will have to update. Iām figuring out how that will work now.
Umm based??
