Doing some testing with my Mastodon account bridged over to Nostr, would be super helpful if y'all could follow it!
nostr:npub19l74aeh29qtsfkswrxeaw2mxepwqfl6d5v3ts2edc9gxx0w4qtuqum8825
This is a post from a Threads account that recently started federating and was then bridged over to Nostr with
mostr.pub
Epic!
Interesting project that seems closely aligned with nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m 's goals for a decentralized github! Even uses a gossip protocol similar to Nostr's
"Radicle is a sovereign peer-to-peer network for code collaboration, built on top of Git."
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.
Chicago seems dope, but nothings topping NYC, the literal capital of the world. The fact that i’m from there is just a coincidence 😛
Hi everyone👋🏻.
Thought my first post should be a photo as a get to know me. So here’s one of my favourite photos taken this last Christmas with my best friend nostr:npub1jcjxjg92200kdp8guw8sysg8gr0ez29hahrfdy49h30hgnkpa4kqfvmtwx which most of you already know 🥰
Very new to this, so hopefully I get the hang of it soon 🤞🏻
#plebchain 
Welcome!
Just noticing that nostr:npub1plstrz6dhu8q4fq0e4rjpxe2fxe5x87y2w6xpm70gh9qh5tt66kqkgkx8j has a web client that's pretty solid!
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
you seem mentally ill, get help dude. it’s not tantalizing because it’s nonsense and doesn’t follow logic and critical thinking.
Testing NIP-95 uploading images directly to relays
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.
> In the outbox model you’re giving control of what relays you connect to other people. Until my client is hardened I don’t feel comfortable doing that.
As far as i understand it, it only tells your client what relays to fetch another users posts from, you’re not adding those relays as a permanent part of your own relay list. So what would be the dangers?
If most people used clients that support NIP-65/Gossip, that problem shouldn't exist. As far as I know, nostr:npub18m76awca3y37hkvuneavuw6pjj4525fw90necxmadrvjg0sdy6qsngq955 still doesn't utilize NIP-65, and it's the most popular Nostr client. nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s thoughts?
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.
nostr:npub1e4qg56wvd3ehegd8dm7rlgj8cm998myq0ah8e9t5zeqkg7t7s93q750p76 is working on a new logo for nostr.build, what do you all like best:
A, B or C?
B
is it the length of the URL, or is it the asterisk that trips it up?