twit VS nostr

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

Some resources if you're interested in learning more: https://nostr.com/ https://ron.stoner.com/nostr_Security_and_Privacy https://github.com/nostr-protocol/nostr/ https://nostorg.github.io/clients/

I think your best bet here is Nostr (Notes and Other Stuff Transmitted by Relays): https://nostr.com https://github.com/nostr-protocol/nostr

Nostr isn't a federated platform like Mastodon or Lemmy, it's more similar to the AT protocol created by Bluesky, whilst being far simpler to understand and write apps using it. The nostr protocol is defined by a series of NIPs (Nostr implementation possibilites https://github.com/nostr-protocol/nips), the most basic of which can be implemented in a client or a relay in 50-100 lines of code in any modern programming language.

Each user runs a client, anyone can write a relay or run any of hundreds of existing implementations, both clients and relays can choose to support a number of NIPs. Users have a public-private keypair, and distribute notes to relays signed with their private key, which are verified by relays. Clients subscribe via websockets to any number of relays (I usually have 20-30), and receive notes from all users on those relays' databases, or filtered by the public keys of the users you're following. Relays for the most part don't communicate with each other. If you're ever blocked or banned from a relay, you'll still be able to have your notes seen as long as you have at least one relay in common with anyone who wants to see them. I run my own as well for extra resiliency.

At the moment there's ~50 standardised NIPs, which add features like likes, zaps (bitcoin tips for notes), user status, post expiration, mentions, search, DMs, and public chats. Nearly all of these are supported by popular clients and relays. While nostr is primarily used for social media at the moment, it's already possible to build upon as a protocol for pretty much any online service.

The total active user count on most public relays I'd estimate is somewhere around 500k to a million, though the nature of the protocol makes it impossible to estimate its true size. The perceived community on most relays before following anyone frankly can get pretty cancerous, mainly due to a lot of clients sorting notes by new by default, so I can only hope to high heaven it'll improve as it grows.

Though like any new non-centralised platform, it's more difficult to get started on for most non-technical users as they have to pick one of hundreds of clients to install, and requires caution to never leak your private key and be very wary of which clients you trust it with.

I hope this was not too technical and all over the place. If you are interested in knowing more please ask me or check out https://github.com/nostr-protocol/nostr or https://nostr.com/get-started

Without movement on this [1] I can't see adoption.

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

I think the next stage is decentralized social media. Something like nostr (1) where there’s no centralized entity determining the algorithm to boost. It’s up to the individual to follow users.

Perhaps the next challenge would be human verification, even with this protocol we’d need something to index public people by to handle discovery.

Even before LLM’s became as mainstream as they are, most social media platforms were riddled with spam: affiliate marketing, drop shipping crap, and people who are running some sort of con.

1 - https://github.com/nostr-protocol/nostr already has 8k stars on github

Considering that Reddit might not be able to negotiate better pricing for API usage, it's worth considering a different approach. The future of social media seems to be moving towards protocols rather than specific platforms. This means that instead of relying on a single platform like Reddit, Apollo should focus on using a protocol called NOSTR (you can find more information at https://github.com/nostr-protocol/nostr).

Holding me back from posting updates of what I had for breakfast is the problem of private key sharing with services that I can use in order to post updates of what I had for breakfast.

A client or service will inevitably be compromised. And with it, the private keys of all using it whether stored by the service or logged on entry by a compromised system.

Private keys should be chained, master->subkey, with subkey the public key of the service __or a solution like that or that ends in the same result. When (not if) a service or key is compromised, the key can be blacklisted and/or any key co-signed by a compromised service blacklisted.

I'm confused by the oversight. It's also been raised here https://github.com/nostr-protocol/nostr/issues/97

Until then, I'll have to keep my updates of what I had for breakfast to myself.