protocol VS twit

We have already have a clear stack. there's Gitcoin Passport for sybil resistance, git (and wrappers like Radicle) for version control, Lit PKPs & Gelato for account abstraction, Farcaster/Orbis/Lens for social architecture, OpenStreetMaps for geographic markets, OPStack, etc.

These services exist outside of the protocol and depend on a few centralized and trusted authorities.

Another solution that is arguably more resistant to capture and censorship would be to use a blockchain to manage user name aliases - like Farcaster is doing with fnames.[1]

[1] https://github.com/farcasterxyz/protocol#22-farcaster-names

one XMPP server gets big and usernames get squatted and dealt with at the discretion of the server admin.

Only solution is something like how Farcaster does it

https://github.com/farcasterxyz/protocol#3-identity

That's sad to hear, but it makes total sense to shut down the server given its sensitive data, rather than hand it off to another person.

Mastodon/ActivityPub is a poor fit for a social network IMHO.

- Accounts should not be tied a single server and their continued maintenance.

- Private data and DMs should be end-to-end encrypted rather than entrusted with a single administrator.

- People don't want to self-host.

The core problem of a lot of social networks comes down to name aliasing, and who controls the name registry. In the case of nostr[1] this is not a problem because everything is using public keys. Another protocol is Farcaster[2] which plans to use a smart contract to maintain a name registry without requiring a single controller.

[1] https://github.com/nostr-protocol/nostr

[2] https://github.com/farcasterxyz/protocol

Which processes up to 8k requests at a time, waiting up to 10 ms for a batch.

Similar techniques should work on read batching, but I haven't tried that. You can also speed that up some more with the COPY protocol, but IIRC you need to be more careful about escaping/SQL injection.

On my 6 year old mid-range desktop (this CPU[1] and this disk[2]) this program can process ~30k `create`s per second. For about $1500, I could buy a new computer with a Ryzen 9 7950 with 4x the core count/8x the thread count and 2x the single-threaded performance, so around ~10x more processing power, 128 GB of RAM, and a Samsung 980 Pro SSD, which can do 1M Write IOPS (25x more than my SSD) or 5GB/s sequential writes (10x more). So a $1500 computer with a single disk should be able to do around 300k/s. PCIe gen 5 is now coming out, which will allow for another doubling of disk performance.

128GB of RAM means you can keep at least 100M rows worth of index in memory. It's not that expensive (under $10k) to build a server with 1TB of RAM.

Totally feasible for a hobbyist to do without tons of tricky optimization; people spend $20k on a jetski or $80k on a truck. Like I said, the most expensive part is going to be the storage, but you could do something like only store the most recent 1000 tweets per person, and charge $10 to bump that up to the most recent 10 million tweets or something. You'd come out at a substantial profit with that model if you got a few thousand takers. Similarly you could charge to let someone follow more than a few thousand people so you could pay for a read replica or two.

[0] https://github.com/ndriscoll/twit/commit/19b245677b978b42a6f...

[1] https://www.cpubenchmark.net/cpu.php?cpu=Intel+Core+i5-6600K...

[2] https://www.disctech.com/SanDisk-SDSSDHP-256G-256GB-SATA-SSD