Is NIP-01 going to be modified with a filter flag so one event per pubkey can be returned?.. .Emulating the filter behavior of addressable events.

Local resolution is the goal, gateways were a stop gap. This is how the `nsyte run` command works, though it was built as an example and for debugging purposes. This is over nodns yeah?

Why?

Ideology has a tendency to dilute art.

Yes. I contributed to @snort/worker-relay

I didn't develop snort btw

https://youtube.com/shorts/YFQm8Hk73ug?si=_oSkAUJnXTgpXY8y

Bacon. All roads lead back to bacon.

I would actually buy this btw

Already sold out?

bacon. I want nostr to make me bacon.

... ?

I opened minibits randomly and the payment was there. When the payment failed I was in a spotty service area. Is there anything you can do to make incomiong lightning transactions more fault tolerant?

Yes. I posted a reply to the root note to clarify this a little while before your reply.

👆 I would like to clarify that I haven't ever been "rugged" in the true sense of the word specifically by a cashu mint, but rather I have been rugged in many different ways over the the last few days: was robbed for around $10k in possessions including my laptop, a CC was skimmed at a gas station and the card was maxed out, having unknowingly maxed out cards added significant friction to travel and then while traveling, was "randomly" searched extensively and intrusively (4 times in one airport!). And to top the cake I was unable to pay with Bitcoin at a "Bitcoin Bar." Having LN transactions disappear indicates systemic issues with minibits infra, and feels like being rugged, but definitely isn't. Probably should have clarified or omitted the "rug" statement. Having a bad few days.

I am almost certain this issue has nothing to do with cashu, but rather with their lnaddr/LUD-16 backend provider. If they automatically mint tokens from all incoming lightning transactions, then alternatively that is the source of the problem.

Good question.

That is fair if all they were doing was developing a wallet, but that is not the case. They offer LUD-16 addresses, they run a custodial LN node and they run a Mint.

Whoops

It was a lightning transaction via LUD-16, I wasnt melting cashu tokens. This is an ongoing issue that many have experienced, and the silence is deafening. I would do the recovery method, but according to many i have spoken with in person, this can result in loss of a lnaddr, which makes fixing this issue more difficult.

It is. They run a node. They are funded to develop a wallet. Having 150k sats disappear and having people like you gaslight me into believing it is my fault is the problem. That isn't entitlement. I've been around here far longer than you have. GFY.

Only pseudo-decentralized clients! Dont use cloudflare! Dont use CDNs that use cloudflare!

Why? If you use a client that properly integrates outbox you would be unlikely to ever see content from them. Remember, nostr is protocol not a platform. It doesn't matter if people you don't like use it.

Haven't noticed

How to use relays would be self-evident if relays had types and those types were expressed programmatically.

Nostr is doing great at many other things. I think the problem people have is that they lopk at a protocol like nostr as though it is linear. Protocols grow cyclically. If nostr got 10m users tomorrow it would likely require abandoning everything that makes nostr stand out.

AsyncAPI is an implementation decision, and most of your rebuttal has nothing to do with what I said. There is a long history of "the smartest guy in the room" coming to nostr telling people what to do, I assume you are the next one?

Oh, and btw, 25 years here, 3 companies and 4 sites/apps/experiences with 100k+ users. I have worked every role from Junior Dev to CTO + Sales, Marketing, Accounting. 3 years on nostr.

Significnatly less efficient than NIP-66

Inherently produces***

I will also add it to nostr.watch eventually.

@nostrwatch/auditor checks this if I remember correctly, but I also broke that. I will fix it eventually 😂

nvite is the most exciting IMO, but also needs some work to make it usable. nvite ia contextual onboarding shared via code.

The motivation was to use the schemas in fuzz testing and to identify interop issues. I also use these, and more specifically the validator, on nostr.watch

How it wasnt built prioritizes maintenance and was written in TS for tooling; the js json-schema ecosystem dwarfs all other languages.

follow lists are kind 3, store the pubkeys of people an npub follows and are signed and published by each npub (user). Me losing the list would not affect you following me, only me following you.

Please note the typo, not nostr.watch api will go offline, not the nostr.watch relay.

I did release https://nadar.sandwich.farm recently, but it has a slightly different purpose.

Only relay operators know what is being request, who is doing the requesting and habits around requests (timezone inferrence, etc)

Clients could expose the TOS and PP via NIP-11, which is how users could see it.