As I understand it, NIPs are essentially “if you want your client to do this use case, here’s the standardized way that the official repo recommends.”
If you’re not interested in your client handling that use case, you could just ignore that NIP, no?
NIPs seem like they’re an opt in thing, whereas we’re conditioning to view these things from the lens of 3rd party APIs that require calls have certain info, and regularly change those rules so that the API call has to change.
I've been brainstorming of a way to adapt Tor's Snowflake proxy approach, but for allowing users to access nostr in countries that are blocking/censoring access to either web clients or relays.
The gist of the idea is that say for example a user in China is trying to access nostr: anyone would be able to host a nostr proxy that then connects that user in China to an assortment of relays, but all their ISP would see is that they're connected to wss:// *random generated relay address*
The challenging part is there would need to be a way for all these proxy addresses to be compiled and accessible to that user without involving pinging a centralized URL/API that can just be blocked.
The proxy itself could be a modified fork of nostr-proxy, since that already does the "connect to many other relays to read/write on behalf of the user" part.
Similarly, if we make it as easy as clicking a button in order to deploy a web client like Snort or Iris on the cloud, and then have an automatically compiled list of all the Snort/Iris instances deployed, then a user could better avoid blocking of the web clients too.
Yup, or deploy your own instance of blastr relay
"Mozilla.ai’s mission is to make developing trustworthy AI apps and products easy. To start we will focus on developing tools to build safety and transparency into the heart of recommendation systems and generative AI technologies."
https://blog.mozilla.org/en/mozilla/introducing-mozilla-ai-investing-in-trustworthy-ai/
What a beauty of a client, looking great #[0] #[1]
Never thought I'd see myself on Nostr.band's trending profiles! I'll make sure to keep up a healthy volume of my usual tech/history/transit/shitpost material 😁
This took me down a rabbit hole learning about the "Neomexicanos", the modern day descendants of Spaniards who migrated to New Mexico.
"The descendants of these New Mexican settlers make up an ethnic community of more than 340,000 in New Mexico"
"some have proposed that there may be a significant number of Latinos in New Mexico who are descendants of Anusim, or crypto-Jews fleeing the Spanish Inquisition."
Interesting "Wallet-as-a-service" from Coinbase unveiled
clearly the maroon beanie is a critical part of your appearance!
Listening to the relays panel right now, they're talking about making proxies which use relays specified by the client, and COUNT. I'm going to release an update to Coracle this week that does both thes#[0] | rbr.bio has built a relay implementation that supports COUNT, and I'm working on a new multiplexer implementation.
If you're interested in this, NIP for COUNT is in draft here: https://github.com/nostr-protocol/nips/pull/144
That’s awesome! stoked to try that out
Hmm you might need to add wss://rsslay.nostr.moe to your relays for rss feed profiles like this
Nice! Is this nostr-proxy or something else? https://github.com/Dolu89/nostr-proxy
I guess it’s fair for Europeans to get this since the Mach E is cheaper for Americans
https://fordeurope.blogspot.com/2023/03/exploring-reinvented-new-electric-ford-explorer.html
“Doing construction work in New York City’s streets is complicated and costly. This report examines obstacles and offers solutions for delivering a more modern, multidimensional right-of-way.” #nyc #urbanplanning