upcoming show schedule in nyc
Mar 20, 2023, 6:00 PM at Magnet Theater (254 W. 29th Street)
Mar 26, 2023, 4:45 PM
Apr 2, 2023, 4:30 PM
Apr 16, 2023, 4:30 PM
please boost if you're in nyc
If you keep engaging with trolls, eventually you'll wind up marrying
Don't get engaged
i always require proof of work and posk for anonymous connections to my (pre-nostr) relays. all that required a socket. for auth comnections, a hash or token in the header is probably fine
The Federal Reserve System was created by bankers for bankers. It was meant to make the rich richer and the poor poorer. That people believe anything else about it is a superlative example of the power of propaganda.
If you’re not using the Fold card for everyday purchases / Bitcoin rewards, what are you doing with your life?
https://use.foldapp.com/r/H3CUC9JL
List of things you can’t use it for
Here’s the list of things you can’t use it for: Yes. Purchases cannot be made at certain classes of merchants:
Security Brokers/Dealers
Dating/Escort Services
Massage Parlors
Betting/Casino Gambling
Government Owned Lotteries
Government Licensed Online Casinos (Online Gambling)
Government Licensed Horse/Dog Racing
Internet gambling
Money Services businesses
Firearm-related businesses (manufacturing and selling)
Marijuana-related businesses
Wires, Money Orders
Non-FI, Money Orders
those are all the things I need
useless
nostr: the chaos is real
also, the so-called privacy layer is a waste of time
all claims should be public claims about the provenance of public keys
all certificates are also public
dids are a bad idea
exactly
and it's possible to create something of an identity-based system as well where you can publish an event with a set of structured claims
then anybody can respond to that bet with a set of structured assertions
boom now you have a web of trust
All claims are public all assertions are public
If you don't want somebody to know something about your public key don't publish it on the internet
dids suck. they're overly complex and have a privacy model that's totally broken
it depends on people not leaking them
which of course they will and then the privacy is gone
All structured claims and certifications about a public key should be public or you shouldn't structure them
in nostr anyone can publish a structured event with some public claims
anyone can respond to that event with public structured assertions of those claims
the absurd notions of privacy in the did system and the insistance on using xml reflects everything wrong with the w3c
The entire system was authored without actually thinking about what people needed or wanted and instead it was authored with a series of intents instead of coming from industry coming from protocol designers
The proper way to build a protocol is to observe what's happening in the wild in the chaos of something like an NOSTR and then look what most people are doing and codify it so that new people coming on board can be compatible
indeed the embedding of proofs just makes dids broken, imo
The whole system is based on a premise of identity that isn't necessary for anyone in this ecosystem
I articulated precisely what was needed for a pki infrastructure. can you articulate in technical terms how DIDs and VCs satisfy that and only that?
But I have thought through the problem
and I've made concrete proposals to nostr
It's merely a set of signed structured claims and a set of signed structured certifications of those claims
and since every event is signed and is unique then we can not worry about the signatures and just use events to create structured claims and certifications of those claims

