Biden lookin like the next CEO of Nostr

Say what you will about how truly "open and decentralized" #Bluesky is, but I gotta give them credit for making a solid onboarding flow for new users.

Just noticing that @Openvibe has a web client that's pretty solid!

Plebstr

Experience decentralised Nostr protocol. Now in user-friendly on mobile & web.

A mastodon instance shutting down because the new Taliban gov probably won't like "queer.af" using the ".af" TLD of Afghanistan, never a dull moment on the interwebs View quoted note →

and this goes for Nostr relays as well. View quoted note →

By far one of the more annoying things about #ActivityPub/#Mastodon, the fact that instance admins can have so much impact on something as fundamental as who you can follow/find, not because the instance has illegal/explicit content, but because they want to be petty and block bridged profiles from Twitter. View quoted note →

As with most things, it seems like the optimal way to go about this is somewhere in between. - Completely obfuscating any mention of Nostr from users makes it so that they won't know the decentralized/censorship-resistant benefits of the protocol that a client like Flare is built on, and it just becomes another video sharing service. - On the other extreme, throwing a bunch of Nostr terminology at a user with the expectation that they'll just go google it and read through Nostr documentation is simply delusional from a UX perspective. A nostr client needs to decide whether it wants to cater to the average user, and make the UX intuitive, or focus on a specific enthusiast userbase that will understand the terminology and have the understanding and willingness to do their own digging to understand the guts of the protocol. You can't have it both ways. For a client that wants to cater to average users, this is what onboarding should look like for a first time Nostr user: - A signup button that simply generates a nostr account, and then tells the user: - "think of this first string as the user ID people can find you with" - "think of this second string as your password, only you should know it and it can't be changed" - Whether it's a webapp or a native app, it's super beneficial for the app to then signal that the npub is a username, and the nsec is a password, so that the respective OS/browser asks whether the user wants to save that login to their autofill, and they then never need to worry about their npub and nsec again. - This way, if they ever need to log back in to their account, their browser or OS can just offer to autofill their login. On web, there could/should of course still be an option to login with extension, for users who understand how those work and why they're beneficial. - However, as much as login with extension is more secure for web clients, it should never be the only way to log in >>**if the client aims to cater to the average user**<< As for content discovery/curation/etc after this step, that entirely depends on what kind of app it is. View quoted note →

Great to see mostr.pub works with threads now! View quoted note →

While the mostr.pub bridge isn't fully recognizing the account yet, we can now say that @npub1vx0d...ku9p is the first Threads account that's bridged over to Nostr! @rabble @Alex Gleason View quoted note →

test

Surprised so few of the popular relays have implemented NIP-50 keyword search. Seems ideal to have NIP-50 search on as many relays as possible, so that the few that do have it (like nostr.band) aren’t having to shoulder the load of user search.

Checking in from #Boston with the first snowfall of the season #snow #christmas

oooo new Snort design is crispy