Fixed it ⚡

I don’t know. But the fact that you flagged it so early is a good start. There isn’t one answer. And the solutions I have in my head I can put out here.

Yes, but how?

I need to carve out some time in a few weeks and try to make it work, but I had a funny thought about the PSBT construction that folks are using for trust-less offers/trades of inscriptions: I *think* you could use that same construction for trustless offers and trades of taro assets. So that means you could do an actual decentralized exchange of bitcoins and stablecoins (or whatever garbage you please).

That’s pretty wild.

Going a step further, what if you did that but with something like a DLC construction on the bitcoin side of the trade. I *think* you could do decentralized trustless borrowing protocols on bitcoin. We could have bitcoin-backed loans, but p2p, decentralized, nokyc?

Attempts to build apps "on top of" Nostr or that "use Nostr" are wrong, harmful and abusive, and will necessarily fail.

Nostr wants open protocols to be built on it, not proprietary shit that is trying to use relays as their private free databases. This behavior should not be encouraged.

I have an idea for a nostr GitHub replacement but it seems too simple. 😂 There’s no code. 🤣

Maybe this could be a NIP?

To create a repo you create a new pubkey (maybe with multisig).

The repo pubkey will publish notes (repo notes) that include nothing but a list of noteID’s.

eg

noteID1

noteID2

noteID3

(these noteID’s are the files, but how? Each of these notes contains a path/file.name and the source code of a file, they are code notes)

These code notes listed on the repo note can be created by anyone, but the repo pubkey only publishes repo notes. Repo notes only contain lists of noteIDs that make up the source code of the repo, the code notes. Whoever controls the repo pubkey controls which noteID’s are on the repo notes published by the repo pubkey.

Each source code noteID, listed in the repo note that is published by the repo pubkey must have the following syntax:

Line 1: path/file.name

Line 2: line 1 of source code

Line n: line n-1 of source code

To get the files from a nostr repo all you need is the pubkey. You pull the latest note of the repo pubkey and then download every noteID that is listed in the latest repo note from the repo pubkey and you run a script that creates path/file.name from line 1 of each code note and injects the source code from line 2-n of the note.

Anyone can make changes to the source code, but only when the repo pubkey publishes a more recent repo note that references new noteID’s that represent code changes do the changes actually go live.

Does this make sense? 🤔

This is insanely powerful. Everything already exists!

❤️‍🔥

V strong on new moon

One of my obsessions has been learning about Complex Systems Theory and Emergence. It's a rabbit hole that's probably done more to change how I think about the world. The past. The present. The future. It's been humbling intellectual journey, because of how much it reveals about what we don't know.

Understanding path dependence is another important concept. Looking at the way systems of culture, politics and economics are *path* *dependent* can help focus you better on how to bend the curve of history, rather than getting stuck in a spiral of moral outrage about injustice in our society.

Moral outrage about "the system" is probably just about the least productive way to reason about the world and make it a better place. If anything, it can be counterproductive, and cause you to justify bad things, in the name of revenge or because you've managed to convince yourself that your perceived enemies are so bad, that hurting them is morally justified.

The world is the way the world is right now. There's nothing that's going to change the present. All you can do is bend incentives towards the future.

Yes, it’s ⚡️⚡️😂

Fixed for you ⚡️⚡️😊