I'd go for redis a bit earlier, it's just so easy to use! I wouldn't cache much at all to start, then at like 10k users (or wherever my benchmarking says to) I

I'd go for redis a bit earlier, it's just so easy to use! I wouldn't cache much at all to start, then at like 10k users (or wherever my benchmarking says to) I'd include it w/redis. React is a decent choice also here because you can port it wherever. One code base for web/iOS/Android is probably critical given how few dev resources you'd want to spend on it (you've got the right idea there too). Also agree w/r/t decentralization. I think this is a fantasy for nerds but most people really do not care about privacy no matter how much people try to explain it to them. I guess one thing I would add here is I'd work very hard to minimize operational costs for as long as I can, until you can show the explosive growth that'll interest investors. There are a ton of scrappy ways to save money on a tech stack like this early on, and you can probably find a way to get that AWS/GCP/Azure credit money to basically make this free to operate until your F&F round. One you have a userbase, just... idk, iterate with them. Everyone and their mother probably has ideas for what they'd like Not-Twitter to be, but finding what the GCD is for that would be important to sustain growth I bet.