View quoted note →

What should be #nostr’s unofficial motto? 1. Be Kind 2. Just Do Things. 3. F**k Platforms. #asknostr

one npub, one vote.

It’s becoming easier and easier. The exchange I use gives me a virtualized Visa Debit Card that I have on my phone. It also gives me a Lightning address. Yesterday, I sent funds from my #nostr #safebox to my exchange Lightning address and then loaded the funds on the card. Then I went to the grocery store and bought groceries with these funds. A few manual steps today, but soon it will be completely automatic. All that I will need is a ‘card’ to access my funds for a local spend. It won’t matter what network will be underneath.

cryptography-based international order

keyspace > namespace

Proof of Pea Soup (still in the making)

This is nuts. I’ve heard that AI can’t be AGI because it lacks embodiment’ (doesn’t have a physical body). But what if the ‘embodiment’ is the machine itself?

X (formerly Twitter)

Marshall Richards (@marshallrichrds) on X

I have had a lot of fun lately letting Claude fully control my old ThinkPad. This finally feels like the correct way to interact with computers, l...

I am on pea soup duty today.

Sharing on how I have implemented Web of Trust (WoT) and Root of Trust (RoT) in #nostr #safebox. There are four steps to the verification: 1. Validation: Is the record crpytographically valid? 2. Presenter: Is the record coming from whom to whom is was issued? 3. Attested By Owner: Did the owner attested that the issuing safebox was theirs? 4. In Trust List: Is the Owner in Trust List. Steps 3 and 4 are independent attestations. For Step 3 the verifier looks up an event signed by the owner that they are indeed the owner of the issuing safebox. Step 4, the verification process has a list of 'root authorities' that are simply npubs, looks up the followers of those npubs and uses that as the 'Trust List'. In this example, there is an account called 'Safebox Trusted Entities', but it could be any account maintained by an organization, such as a College of Physicians, that might want to manage a list of doctors. Up until now, these schemes needs to be managed by 'specialized authorities' such as certificate authorities, or organizations with proprietary databases. Now with #nostr, we can make these schemes completely open, transparent - not capturable by a technical authority. In short, everyone can become their own root of authority, manage their own trust lists, and also decide which roots to trust when verifying. This is just a prototype, but it already demonstrates technical capabilities that are stronger and more reslient - and more open than any certificate authority program or public key directory that is out there, including what is being used by passports, driving licenses, or national authority. Onward!

It's time for snow bank removal!

It took me a couple of years to figure this out. The core reason why #nostr is going to win as a protocol: By creating a unique event id that is the digest of its: - author (pubkey), - meaning (kind), - timestamp (created_at), - metadata (tags), - message (content), and: signing of this resulting event id (sig) That means you can sign whatever the hell you want with whatever meaning you intend, and it can be uniquely stored or relayed anywhere. #nostr become the sword of simplicity that cuts through the Gordian Knot of interoperability bullshit and semantic capture. This simple format allows anyone to define whatever they want, with only a simple rule for cryptographic validation that it was actually they who created the event. With a few additional conventions it becomes a baseline protocol for social media, but can be expanded to an infinity of possibilities. Thanks for this genius, @fiatjaf

I want a natively addressable npub mesh network that is globally available. Have npub? Connect directly to the the mesh.

Bitcoin enabled permissionless transfer. Lightning enabled reciprocal transfer. Cashu enabled blinded transfer. #privatepayments