@bot@coin Because they think account portability matters more than anything else, and because the protocol is “simple” (aka not feature complete) and well-documented unlike the Wild West of ActivityPub.
I think it was genuinely easier to implement. So we’re going to have to deal with Nostr in the ActivityPub world. But I wish the effort were spent towards making AP do the thing we want it to do instead.
@alex Well you know it more than everyone since you are the guy who helped them at least lay the groundwork with federation. They just went "nah we'll go that way instead" So dumb...
Do you think you can make an appeal to them to scrap NOSTR and go with AP again? Talk to them directly?
what really sucks is he's been on JRE twice and he seems to have a lot of relationships with other notable folks. his bullshit has slowed this evolution and may still be having that effect. there's so many people in the lefty and libertarian dissident space that only talk about the fedi/mastodon, if they do, to mock it.
You can see a protocol finally get hot (even if the outside world still thinks it’s all Mastodon, who cares, most users don’t know how tech actually works), and you pick another one that isn’t hot?
@cjd@coin@bot Yes, it fixes the dependency on DNS - at the cost of terrible user experience.
I expect when I move from my laptop to my phone that I can see the same content. But that’s not true in Nostr world.
We have to build upon Nostr until it essentially becomes ActivityPub, and at that point we have to ask why we did so much work instead of just adopting DIDs and account portability on the Fediverse - a problem which @silverpill has already solved btw.
@GoodPerson@coin@silverpill@cjd@bot Yeah dude it’s built in C and uses IPFS, has no unit tests (automated testing is bad) and every variable is a single letter and there’s basically no whitespace. Sounds maintainable.