Speaking as a jew, "only the jews could make that argument" made me laugh. Not unfollowed.
However, in the case of nations, governments are undeniably chock full of psychopaths.
+1 for obscure demolition man reference.
Although a lot of signage is not in English (though a lot also is), Japan is extremely easy for english speakers. 50% of the people on the street will just walk up to you and start trying to help you in English if you even vaguely look like you might be lost or confused.
What do you think about the idea of using kind 30000's for default saving of follow lists for client interoperability?
Personally, I'd much prefer that my default list of follows was private. I know other people like having public follow lists and having both kind 3 and kind 30000 makes both possible. I just think the safer default is to use kind 30000 for this purpose.
I either don't understand what you're saying or you missed my point.
If my friend bob creates a pubkey to be used to post stuff anonymously but because we're friends, he tells me that pubkey is his. Since he's using that pubkey to post anonymously, he's not going to put "bob" in his kind0. And whatever he may have in his kind0, if I petname that pubkey "bob" so I can remember it's him and then my kind3 list goes up to relays, i just doxxed bob.
I know not to do that. You may know not to do that. I'm not bringing this up for you and me.
If petnames are part of the kind 3 data that clients store publicly on relays then encrypting them would be critical to avoid inadvertent doxxing.
Let's say I have a friend who has a pubkey they share with me that they want to use anonymously. I follow that pubkey and give it a petname. Then I intentionally (with some clients) or unintentionally (with other clients) save my kind 3 follow list to my write relays.
For that matter, maybe it would be better by default to use kind 30000 (from NIP 51) for saving contact lists to relays for client interoperability and then let kind 3's only be for intentionally saving public lists of people for other purposes.
Maybe they think you hate peach.
More on moron glasses.
I'm very much a live and let live kind of person. I don't need you to talk like me or think like me or be like me.
If you prefer or just don't mind having your life surveiled by people you don't know or have any reason to trust, that's ok with me. I think it's stupid but I'm 100% ok with sharing this world with stupid people.
What I'm 100% not ok with is you splashing that stupid on me by pointing your face at me while wearing your little .gov-approved, big brother, meta-ray-ban panopticon ports, piping video of me minding my own business on the street directly into Mark Zuckerberg's anus and then on into the never-forgetting NSA hard disks in the Utah desert.
Starting from October 17, if you are wearing Ray-Bans anywhere near me, you and I will have a problem. A real problem. A serious problem.
I'm cancelling Ray-Bans.
Thank god for Mark Zuckerberg; now you can BE a jerk without LOOKING LIKE a jerk.
Seriously, starting from October 17, if you are wearing Ray-Bans, you and I have a problem. A real problem.
Exactly. Perfectly said on both. Most especially the parts about keeping the protocol as simple as possible. I worry that nostr is getting too fat too fast.
I also favor you, as nostr CEO, running rampant through the existing NIPs and sprinkling in a lot more MUST and MUST NOT.
nostr:npub16dmvfhm7uwkxnhxg30k6aczw23wxhgvs62n3puzl5tykpa4aa8esja83yd
The answer to all those "what happened to you" posts should definitely be "what happened to YOU?"
Sorry, but welcome to the other side of "embrace the chaos".
Personally, I favor tighter specs throughout. Discipline is the paradoxical path to freedom.
That will be a fantastic addition to gossip - my fondest wish. The only thing I miss (at all) about twitter is the tweetdeck ability to have separate lists in columns.
You must look at veilid. https://veilid.com/docs/overview/
"Veilid is an open-source, peer-to-peer, mobile-first, networked application framework.
The framework is conceptually similar to IPFS and Tor, but faster and designed from the ground-up to provide all services over a privately routed network.
The framework enables development of fully-distributed applications without a 'blockchain' or a 'transactional layer' at their base.
The framework can be included as part of user-facing applications or run as a 'headless node' for power users who wish to help build the network."
Would have been dead on if they were talking to each other through their devices while sitting across the table from each other.
Uhhhh... it's Android.
Tried anysoft and I wanted to like it. Gboard is so much better.
My use-case is probably different from yours but I can 100% honestly say that Graphene works better for me as a daily driver than the stock Android on a Samsung A71 that I switched from. I only have one profile. I was expecting to have to spend a lot of time setting things up and tweaking, but it ended up being less than I feared, and since I got the phone set up and configured, it's been surprisingly stable and reliable.
FWIW, I'm using GrapheneOS specifically to de-Google (in the sense of them vampiring my data). I've tried all the open source keyboards and they are all unusable for me. I am running the latest version of Google's GBoard which is the best keyboard for me functionally by many miles.
The beautiful thing about Graphene is that you can install GBoard and very simply give it zero permissions; no networking, no contacts, no microphone, no photos and videos... and then you get a fully functional keyboard and none of the siphoning.