Is there a way to validate DNS txt records from the browser? On the other hand, its much lower barrier of entry if you have your own domain to upload a file instead of mocking with the dns entry.

For one, we have relays, they have pubkeys, and yet, we still rely on the certificate chain. In a better world, relay lists should contain the relay host (or better, its IP) AND its pubkey, and those pubkeys should be directly used in diffie-hellmann key exchange when initializing secure connection. The problem with this approach is that there is - to my knowledge - no technology embedded in browsers by default that achieves it effectively.

Plebs Tube is coming!

I'm a plebs.app maxi, this is going to be huge. Actually nostr is very well positioned for this use-case with being inherently social + blossom servers becoming very common these days. A way to monetize could be a service that provides extra bandwidth for popular podcasts around the release time when the load exceeds the blossom servers' capacity. Alternatively this task could be done in a crowdsourced way: allow anyone with bandwidth earn sats by providing the extra bandwidth, and you can take a cut for managing the connections. So many ideas and possibilities to explore. I'm planning to release one episode of a podcast for my local community in January to shill nostr, and see how ready people are for this kind of goodness.

good vibes over good tech, something to live for!

plebs.app maxi here

Primal doesn't create a relay list event for you. (kind 10002) You can use jumble.social -> settings -> relay settings to set a few relays wss://relay.damus.io wss://relay.primal.net wss://nos.lol Then, when you see your profile on njump.me, it should display exactly those same relays. ("seen on") A product targeted at newbies should do this for you. There is a (good) reason why many people dislike primal. They are good in zero-config startup, but fail in a few other areas miserably.

In part life experience you are not controlling. In part forgiveness that you are also not controlling.

💡 Turns out it's quite simple to write. Not very performant, but will do for now. import { matchFilter, type Event, type Filter } from "nostr-tools" export class MemStore { events: Event[] constructor() { this.events = [] } add(event: Event) { this.events.push(event) } req(filtr: Filter): Event[] { let r: Event[] = [] this.events.forEach(e => { if (matchFilter(filtr, e)) { r.push(e) } }) return r } }

today's post, last sentence. About information gathering.

Like your asknostr.site though! Great initiative, might answer my 2nd question :)

Hogymicsoda lenne mi? az aszknoszter teg jó ötlet volt, lemaratt. :/ Rohadtul nemjó és nemhatékony az infóáramlás. A Shitposztok közé kell befércelődni egy ilyen kérdéssel, ehh...

TY!

I need a simple JS nostr in-memory event store. Filters should be supported. e.g. events = eventstore.req({kinds: [1,6], authors: [pubkey1, pubkey2]}) window.nostrdb is good, but I want it to work in nodejs. nostrify/NSet is good, but I need it to understand the filter API. There is a test relay, in-memory (dunno the name), but it listens on a port, I don't need that. Any ideas? I am kind of clueless where I should seek such information, but that's a story for another day.