Has anyone thought about how to disseminate Opentimestamps OTS proof data attesting to Nostr events across the relay network? I've been trying to implement this such that OTS data is by default treated as trusted if it's signed by the same key as the reference event that is being attested to. The idea is that you are already trusting the pubkey that signs the reference event - if you didn't, you wouldn't be interested in the reference event (or its OTS data) at all. So if you see a purported OTS proof that's signed by the same key as the reference event, you can by default treat this as trusted without the need to perform a verification against what's recorded on Bitcoin. In that situation, the only time you need to perform an audit against Bitcoin is when there is some positive reason to suspect that the OTS data you were provided with is incorrect. #nostrdev #asknostr #OpenTimestamps

Monaco reminds me of L.A. A combination of Rodeo Drive and the Sunset Strip and Wilshire Blvd.

So I think Nostr supports encrypted direct messages, right? Or not really? Or there are different competing protocols, and some of them work, and others don't? Or none of them work? #asknostr

So I think I'll have to set up some sort of AI agent and play around with it. I kind of don't want to, but it's probably inexcusable not to at this point. But how can I do it safely? I don't have a dedicated computer for that sort of thing. Maybe on a fresh Linux install on a USB?

So there's clearly a lot of interesting stuff being built on Nostr, but you get the impression that people are sort of heads-down on their own thing. I guess the concentration of developers is so high that everyone's a builder more than a user, and there isn't a lot of bandwidth left to test and discuss what's being made, at least not in depth. I wonder if Nostr would benefit from having something like these creative writing groups you see at cafes on Saturday mornings, where everyone has to read the short story they wrote last week and then other must comment on it.

Inkan enables you to revoke and replace key pairs when your private key has been lost or stolen. You can also perform periodic key rotations preemptively. You can do all this in a decentralized manner. That way Inkan gives you a decentralized permanent online identity that only you control, and that you can be confident you can keep over the long-term. For example 50 years. Inkan is open for testing and comment. Let me know if you'd like to try it out.

Figuring out the right time of day to transition from "bongiorno" to "buonasera" is tricky. I always seem to walk into a store when it's like 2:53 pm - what do I say?

So I do wonder what may get people interested in Inkan. The ability to revoke and replace lost/stolen private keys or perform key pair rotations doesn't seem to have mass appeal. Maybe people want pictures? Let's see - who can guess what this does: