Excited to have another artist on @Creatr 🎨 View quoted note →
Mazin
_@mazinkhoury.com
npub18kzz...x5sz
Used to play poker now I build things and fly planes.
🍷 relay: wss://nostr.wine
🎥 relay: wss://creatr.nostr.wine
Filter and API: https://docs.nostr.wine
Translations: https://translate.nostr.wine
Adventure awaits
Got to do some cloud surfing on the way home today ☁️
🍷 filter.nostr.wine now requires NIP-42 AUTH 🎉
It’s time to drop the /npub path from your relay list and connect directly to wss://filter.nostr.wine instead!
Broadcast=true is now the default and no longer needed. You may still set ?broadcast=false if you do not wish to use our public relay/NIP-65 broadcaster.
Add Nostromo to the list of NIP-42 supporting clients for all platforms! View quoted note →
Randomly assigning relays to new users without any reliability or performance metrics will not end well.
Primal has the benefit of their caching service to mask the problem but those users will suffer on other apps that don’t support it.
This framing of outbox vs proxy relays on separate sides is disingenuous at best.
My main criticism of outbox model has always been that it will REQUIRE intermediaries to be usable on most clients if nostr users spread out across more relays.
If all I wanted was for the “smart proxy relays to win” I wouldn’t bother having these conversations.
The fact that any criticism of outbox model is received as “you must have another agenda” or “you must be too lazy to update your client” doesn’t help convince anyone that it’s a good idea. View quoted note →
🍷 nostr.wine and filter.nostr.wine now support up to 4000 event tags and larger websocket message size limits to help with your follow list struggles!
Our NIP-11 json has been updated to reflect this change.
Just tested this and it works! Should be able to get it deployed very soon. View quoted note →
Close to finishing up NIP-65 support for the broadcasting side of filter.nostr.wine 🚀
In addition to our usual list of public relays, we will soon also broadcast your notes to your “write” relays and any tagged user’s “read” relays.
I’ve got a new 🍷 nostr.wine landing page to finish and release today.
It’s only the first phase of our new site migration since we plan on integrating all of our relays and services in one place.
I’ve got a few too many projects in the air at the same time and it’s paralyzing my brain. Keep spending hours thinking instead of doing.
Finally made some progress today but seem to clear anything off my plate.
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 →
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 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 →