IaC is great.

Unreliable buggy low performance garbage

that video never gets old

It is a crime against humanity

MongoDB should not exist

Unless your relay collects that information for you :)

You can’t build it elsewhere either. You need to somehow find all users’ servers that might be following you.

Where link

You can build anything on Nostr.

Synonym has tried to build their own “Bitcoin web” in the past. An unnecessarily complicated and bloated ecosystem. Their most recent pivot is Pubky as they try to grasp onto what remains of the market that hasn’t been captured by Nostr. All they do is reinventing the wheel for corporate capture. ActivityPub solved a problem in what they thought was the best way. And to be fair it was good for its time. Now ATproto is trying to leverage a similar design but with more marketing bullshit and a new platform to capture people. Pubky is no different. Nostr solved a problem and they are looking for the newest marketing hypeshit to push, so they can capture users.

And there’s nothing stopping people from bridging over Pubky data. Or Mastodon. Or whatever.

Everything from ActivityPub to Nostr to ATproto to Pubky is built on entities and events. They share 90% of the concepts. The rough details will remain the same. The specific choices are what make or break protocols and what make Nostr inherently more flexible and developer friendly

Except that Nostr already works and is inherently more flexible by design. Less is more.

Nostr.land already supports fax* * Fax notes will be delivered via avian carrier only. Only available in certain regions. Address information available on an “if you know you know” basis,

I should write a FDB document layer

And what prevents building a list of all of these exit nodes

Which SE does it use?

Well I can’t help you with this supposed issue if you didn’t reach out when it happened. The correct configuration also requires you have hist.nostr.land in your list which you don’t. While there is a best-effort attempt at syncing lists it is not guaranteed unless you write directly due to the nature of Nostr.

Nostr.land restore works much better as it can show you multiple versions while not requiring manual backups.

https://nostr.land/restore

There’s also the question of do you need transactions. There is transactions for consistency, and there’s transactions to ensure correctness of the system state (like indexes) Many Nostr use cases actually do not need strict consistency. There is only some level of correctness required. CRDTs and conflict resolution fixes this. A notes app for example can be represented as a set of diffs on top of each other, and two updates to the same note can be merged. This is also why Dynamo and eventually consistent databases exist. You could also have slightly smarter relays that can do slightly smarter queries if you want.

Damus currently allows editing note content by trusted relays. So that could be used to replace media links with optimized versions