Thanks for the context! Very helpful.

It’s more why is the @ in the middle in the first place? I’d like to understand the problem we’re solving so we build the best ux experience

Earlier this month nostr:npub1pu3vqm4vzqpxsnhuc684dp2qaq6z69sf65yte4p39spcucv5lzmqswtfch released in app NIP05 creation. If you dont have one definitely check it out!

During the development we had a long debate about the display of NIP05’s in app. Presently Nostr defaults to making them appear like email addresses with [name] @ [domain].

This presents challenges in the UX of how people interact with these handles.

- some apps send people to the website host of the nip

- some apps treat the nip as an email address

- what happens when there’s actually an email address vs a NIP05

- nostr already supports an @ ux pattern for Npubs and by extension n profile which renders as @ display name

Is there a reason NIP05’s dont follow the same @ pattern? I’m curious what problem are we solving for users of Nostr with the current format?

#asknostr

A fascinating read on book publishing and who benefits and who doesn’t.

https://www.elysian.press/p/no-one-buys-books?utm_source=cross-post&publication_id=298634&post_id=139785658&utm_campaign=296132&isFreemail=true&r=kx2v&triedRedirect=true&utm_medium=email

I’m a big fan of beaches on the shoulder season.

I am curious why search isn’t isnt neutral in your view? Is the NIP itself not neutral or does the bias come in at the interface? Would love to know more about what you mean by DVM and how that could work as well.

It seems like as a network we’re missing the opportunity to build more resilience into the system. We’re also asking a single relay to do a lot of heavy lifting.

I replied to your question instead of Matt’s answer so you will only be tagged.

In many of the “what should Nostr do next” threads over the past few weeks some users have noted search isnt great across Nostr.

This morning our team looked up the relays that support NIP50 - the search NIP and there are some but very few of the major ones folks connect to support search.

We have built our relays on strfry which prioritizes speedy return of npubs rather than indexing.

Curious if folks are relying on something other than NIP50 for search?

Also curious what is or is not motivating implementation of NIP50 amongst relay managers?

Based on coversations with users other apps are not supporting web of trust. So someone noted they had a bumch of harassment last week they were not seeing by default in Nos bc of a combination of WOT and content warnings but when they logged into Primal all the posts were visible.

lol that is some serious fragility on the part of those CEO’s. In all seriousness it is incredibly hard to build firmware and software that works well and accomplishes everything it needs to in a short amount of time and to get it right on the first try. They crammed too much in and released way too early.

This is being proposed bc parties are in gridlock. This is not a proposal on its own. Proposing radical ideas is a way to get the center to move. I would be interested in seeing how it played out personally. Would cycling adoption increase for example? Would communities have more local events on the weekends?

I’m unclear if the bear has a really sore shoulder or if some testosterone loving raccoons have moved to town. The wire cable straps are still intact but the bags were ripped open both in and outside the can. Regardless we will be having a long conversation about recycling at dinner tonight.

At the height of rhe eclipse last week, all of the wildlife had something to say including the coyotes who only chimed in when the sun was mostly covered. It’s faint but you can hear them twice near the beginning. https://video.nostr.build/983c391ac9496bdd095652ddf9c90b6a9e732a52997a22b6b54f8649c2fbbf97.mp4

Yeah I’m mistaken about the protocol layer as the place where mutes of replies and mentions should happen. Based on some conversations today it makes the most sense that the clients and relays screen for these.

In terms of filtering out the random jerks - other protocols are experimenting with mute lists - similar to what you suggest above and I think it’s a good option for Nostr as well. A user can subscribe to a mute list of their choice based on whatever criteria they have - it could be words / content or people. Another framing is feed curation.

The beauty of Nostr at its basic level is that the user is in control of their feed, rather than an algorithm. Sorting through harassment challenges makes that control truly possible.

You can do a search for roya in primal https://primal.net/search/roya and see the conversations - i suggest you dig through there.

We dont have block in Nostr. We have mute which is different. Block implies they can’t post in replies or mention someone.

It’s an experimental bot people can subscribe to that will label offensive content so they don’t have to see it in their feeds. If you search for Reportinator you can follow it. It’s a bit broken at the moment bc it’s picking up nprofiles when it should only be picking up nevents.

Well Rabble is being harassed at the moment for the Reportinator. So you could look at that as an example. However Roya (I believe that is her display name) quit two weeks ago because of harassment. There was a long thread about the topic. I looked for it the other day but couldn’t find it. I can try again, but you could also go and look at threads in her feed to see what she was experiencing.

You can also create a new account as a woman and talk like you normally do (as a man) and experience it yourself. If you code, you can set up a github profile that clearly indicates you are a woman and also see what sort of experience you have submitting code.

It’s not the women who are fragile, it’s the men who can’t handle women having an opinion that is different from their own that are fragile. I cannot even begin to tell you the number of times in my career that people have said - “if you were a man, we wouldn’t be having this conversation, but as a woman you have to watch how you speak so as not to offend.”

By giving aggrieved users the right to harass Nostr is protecting fragility.

One other thing I forgot to mention is that across Nostr we are not implementing mutes the same way. If I mute someone on Nos, they are not muted on Damus. I’m not sure how often people use different clients, but it would be good to have mutes work across the network as a starting point.