> Also it's interesting that in both ActivityPub and Nostr, people write posts more often than they Like/React to posts, which goes against the conventional wisdom.

That does seem weird to me, too, and when I look at my timelines on both, they don't seem to support that fact. However, people on Nostr definitely don't interact with my bridged posts usually. So I think this might only be true for bridged accounts, but not for the native ones on both sides. 🤔

Already solved for XMPP (which also has other benefits): https://migrate.modernxmpp.org

And not even an issue to begin with for SimpleX (since it literally has no user IDs): https://simplex.chat

Yes, of course. It would be much easier for them to investigate crimes in the future, if they wouldn't push everyone to fully E2EE comms.

However, with most of the industry moving to E2EE protocols, the peak value of a full takeout of unencrypted comms from Telegram is probably just about now.

Telegram is unencrypted by default. This is about the open drug and prostitution markets that Telegram facilitates. It has basically replaced dark markets on Tor for most of these things at this point.

Tired: Requesting a feature from people who almost definitely won't do a ton of work to integrate something they're not using themselves as of now.

Wired: Built the feature, prove how it actually works, and allow instance operators to merge your code and run it on their nodes/instances.

It's complete fantasy. Not a good look tbh.

Shell out to nak perhaps?

https://github.com/fiatjaf/nak

Regarding Cloudflare not wanting to run a gateway anymore, I can add a fun fact from our running a public gateway in the past:

At some point, we were wondering why our nodes were serving so many requests and creating so much traffic and resource usage. It turned out that the developers of some Chinese movie streaming sites had figured out that they could just use public IPFS gateways as a content distribution network. So whatever new gateways they found, they just added to a list loaded up by the streaming clients to try and load movies from. It looked like a DDoS attack to us, because it basically was. And the only way to stop it was to stop serving anything but our own content. You could call it a tragedy of the p2p commons I guess.

https://blog.ipfs.tech/shipyard-hello-world/

Nice, I like the idea!

I'm sure you already thought about how to handle forks, multiple maintainers, and more? For example, since Git is already content-addressed, I guess we could detect full repo forks by watching for the same hashes to be published to other Git servers/URLs which are initialized (published to nostr) by other npubs. And multiple maintainers wouldn't even need to be solved via Nostr, since their merge permissions can still be managed on Gitea, etc., right?

Do I understand it correctly that when you "push" a pr branch, it publishes the changeset to relays as notes? So there is one maintainer who then updates the original/upstream repo with merged commits?

Since when do you sign tweets with your private key and send them to multiple servers run by different people?

Isn't the entire point of Nostr that it's irrelevant how many relays there are at any given point, or if a large one gets compromised or goes offline? This sounds overly dramatic to me, since hardly anyone is directly "dependent" on the Damus relay (except for maybe Damus users; no idea what the app defaults are for relays).

So when you leave your car in a garage in the city, based on the contract you have with the owner of the garage (usually via T&C), you don't own your car anymore?

Ownership is not the same as possession. You don't possess those coins, but you may legally own them. The contract may specify that the coins cannot be rehypothecated for example, so it's pretty much the same as your parked car. In both cases, your property may not be returned, but in both cases you may be OK with leaving a small part of your net worth with someone else for convenience and efficiency.

What's the point in trying to take the word "wallet" back in this way? It's been used for custodial wallets for so long by now, that the chances of you ever having success with this language change are pretty much zero. Apple Wallet, Google Wallet, whatever other "wallet", all the things you use those with are custodial accounts.

We can agree on us as developers calling custodial wallets "accounts" instead, but if you just call something a "wallet", you will have to specify if it's a key chain or not. Do you have a better term to propose for making that distinction clear?

I'm just a connoisseur of barbarian cultures, but originally from a civilized part of the Roman empire. :blob_monocle:

Butcher only, and same day is obligatory. We're not barbarians, are we?

Yeah, so that rule is kinda useless now. I shall follow your example soon!

Ah, got it. Thanks!

You may also get deported for eating this in the evening, since the wurst cannot possibly still be fresh enough. They're not even supposed to hear the 12pm bells ring...