I have no idea, sometimes I think down these scenarios and run into a solid wall... Then back out and think some more. Lot goin' on w this stuff.
For the auth, yea, it's clear it needs implemented. That's all I really know at this point. 😁🦀
Auth is for controlling reads. Without it currently, anything can be read.
My current approach is, do what it does now for writes (whitelist/payments) with the addition of auth in the coming months, it can also control reads with these same rules. I will also add fine grain acls for kind lists. This should cover everything I can think of. (DM circus and all).
Ok cool, so then yes, for the public events, your plan is a good idea, it's what I would think everyone would want..
and I am simply trying to ask around to see if client devs lives could be made easier by a field in the nip-65 relay list, that clients can show their users "hey, if you wanna message the inbox of this person, here's a link/payment/etc". For some reason they're really stuck on these free access relays for inboxes.. might have to habla.
That sounds awesome, maybe Colby can figure out all new DMs after the gitnestr 😎
Clearly have been gossip too much and I'm no longer sure if by inbox, you mean the nostr DMs or just public comments/events, or both 😂
Many problems with nostr DMs, is why even with auth, most people agree that they suck in current form. There is no key rotation or 'forward secrecy', and a compromise for either parties key, means leak of all messages. Auth is barely a bandaid. Some clients trying to innovate with giftwraps, but I haven't seen this working despite claims it's implemented in coracle and amethyst for 'advanced dms', also not sure about the rotation there. Private groups, those do have key rotation, just in coracle only and unaudited by a security team afaik.
Relay week! 🐳😁
I think they decided it should never have been created. Gossip was the only client, didn't implement DMs. Then compromised and now shows them, but you can't use them. (Gossip protocol prob never was meant to work with DMs, because DMs are DOA). Now that I'm saying this I doubly realize why I shouldn't bring it up in gossip discussions.. but I still want gossip to work with acl based public events.
I guess it is kinda clients.. I keep thinking it's relays cause I wasn't able to implement auth yet. But there are relays that do, so I see your point.. DMs have been broken a long time, but not for lack of them trying to come to a consensus.. just they haven't come to a consensus. Lol
dude.. chill man, don't have to be mean like this.. it's un-necessary
Or how about, "the popcorn model", that's catchy. Not all the notes pop, but most do, and then butter and stuff.. 🍿
Ya I'm trying not to confuse everyone too much with the DMs .. that horse has been beaten to death. And I agree though and auth, is important for many uses. What's really important though is paid relays /acls. Auth just adds the read acls to what currently is write acls. Nothing is free, or you're the product, etc. posting spam and annoying people's inboxes, is certainly not free.
Funny, this was a reply to a long form article from inside amethyst, but somehow it just created a regular post out of it or something. 🧨
You do yes, earlier I was looking at your logs to see if I could find why blastr wasn't making it and there were like 5-6 negentropy synchronizers latched on there 😂 soh popular and yet, a nice forest.
Been thinking about inboxes for a while.. Trying to think of the perspective of a popular user who gets probably an overwhelming amount of inbox spam. So far all the gossip specs are missing something, they're missing the idea of paid relays. Paid relays, even for small amounts, think how nice this would be for popular users. Someone has to pay, to send to their inbox, send them a DM etc (even just a one time payment). This cuts malicious users/bots down at their kneecaps because it becomes possible to moderate your inbox. Without this, bots can just spin a million keys and destroy your nostr experience while laughing all the way to the bank (the bank that cost them nothing to use).
So, what I think needs to happen, is gossip spec should to expand to think more about the paid relay case, clients should make it clear to a user that the inbox for that user is paid, and help them do this, or point them at a secondary inbox (which is not checked that much because think about it, this is a common twitter problem too, big social media accounts don't even read their comments and they think this is a solution. Nostr can do better than this. Large accounts should not have to go into broadcast only mode or get constantly screwed by bots).
nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z thoughts?
If I were to add to the "what is wrong with gossip" category here, I am starting to realize that it's paid relays. This doesn't bode well for the direction I'm going with relays as I only want to support paid relays, list based acls, or obfuscated relays. IE, relays that have not been discovered by bad actors, or that have enough barrier to entry that keeping them at bay is possible by one person or small team.
All I mean here, is I think the nip-65 needs to expand to include paid-inbox and/or auth. And maybe the word paid is now frowned upon, by people who don't want to require lighting. So acl-relays? 😅 Potentially need to provide an API or way (event kind) for checking if a pubkey has access to a paid or auth relay..
The blastr code is very straight forward. It queries nostr.watch API for online relays and simply sends the notes to them using queues.
Any additional propagation is people running streams between relays (very common, even by non relay operators it seems), negentropy syncs, and that the popular clients when reacting or commenting republish the referenced note to their relay list (which may include blastr). I would be curious to see how much of nostr has blastr in their relay list, but not curious enough to get off my couch.
Overall, with the amount of my events moving around to relays I don't know about, I have to use blastr periodically to set the record straight on important stuff like relay list, profile. Or many clients that use hardcoded relays or search relays get confused, and likely so does anyone wondering where to find or zap me.
Huh, why was I watching this crap 3 star sci-fi when the new 3 body problem is out? 🤦♂️🥳
What do you see when you look at people lists? And active relays?
Lol, there was 3 hour notice ser 😎 it's where everyone zaps and everything gets zapped. If there's too much notice, it gets less fun. Better to zap first and advertise later. 😂
I've done both a few times, flip flop, right now pretty rural. Upsides and downsides to both. City upsides for me were the public transit or biking/walking almost everywhere (except to leave the city). I could go to a bar and cut loose and not worry about how I'm getting home. Interesting people, tons of meetups for my field(s) of interest and more social stuff. Downsides were it was not sustainable, it felt very much like I had to plan for an escape or end up burnt out and homeless. Gold rush town mentality was readily apparent, always on the watch for getting taken advantage of. Almost like an extended 10 year visit to somewhere that could never feel quite like a permanent home.
If cities were a little cheaper, it'd make more sense.. I feel like maybe they used to be. Need to create new cities.
I would try it if my client supported.. I tend to comment + react or zap(w no comment) mostly anyway. I only tend to use reaction at the end of a convo as a marker for that I read the last message. Yeah it's funny the patterns we create.