This is now deployed on all 4 nostr.wine mirrors. It may not be noticeable on the outside but we expect a slight performance improvement from these changes. Monitoring now 🚀 View quoted note →

Whoa it worked out of the box. Was not expecting that 😂 Singapore 🍷 nostr.wine is once again up on the load balancer. View quoted note →

Trying a websocket performance improvement update today. I’m removing our Singapore nostr.wine mirror from the load balancer to do some testing there. You should not experience any connection issues. Stand by 🫡

As long as nostr is open (and to me that’s the most important part) nobody gets to dictate what other people do. Not what type of new kinds or events they create, not what relays they choose, not what their relay’s policies are, not what clients they use, not how they manage their private key, not who they follow, not who they mute, and certainly not what they say. That’s the point.

I think a lot of you drastically underestimate how quickly notes currently propagate across relays. Both client design and relay syncing play a role. Most notes written to small relays are visible on many large relays within a minute.

Too many clients automatically broadcast notes when reacting, replying, zapping, etc for this experiment to work. Two screen shots for you. One from right after you posted the note, one from after 2 reactions. View quoted note →

@aljaz Hi I noticed relay.nostr.net was down. Wanted to give you a heads up in case you didn’t know.

I don’t really know where I stand on blastr conceptually but I know these @OpenSecret guys know how to run software. Consistent and reliable services are pretty rare on nostr and blastr is clearly one of them. View quoted note →

I’ve finally been around nostr for long enough that a lot of the “new ideas” being proposed are just (unknowingly) reworded proposals from a year ago.