484 karma · joined September 23, 2015
From what you've written so far, while the tech is cool, I'm not sure you're trying to solve a problem that actually exists. This is coming from someone who is bullish on both cloud gaming as well as decentralised architectures for gaming (esp VR) but for other reasons.
You seem to consider updating and rendering millions of players client-side to be a bottleneck; it's not -- human perception bottlenecks kick in long before that. Players can't -- and don't want to -- see all other players that are in the same area. And if they're not, then sharding by area is a much easier solution.
Even if it were a bottleneck, the solution is not to offload that rendering to cloud GPUs, it's many well-established LOD tricks. Game servers don't send millisecond updates of every player in a world to a client, the bandwidth they end up using for good UX is almost always lower than streaming video. You said networks keep getting faster, true, but client GPUs keep getting better and better too. Shard-less horizontal scaling sever-side has already been done btw (see SpatialOS (https://ims.improbable.io/products/spatialos) or WorldQL (https://github.com/WorldQL/mammoth)) or the many proprietary implementations (think Fortnite, Roblox, etc) but I don't think it's as useful as we think it is.
Besides this, I can tell you for a fact that "we have more players than we can handle" is an extremely rare thing actually, even on launch days, even though it might not seem like it to us. The biggest problem for games is getting players in the first place. The ones that do tend to have big budgets to spend on their servers, and it's usually not budgeting that's the bottleneck, but bad planning.
I would be curious to know if you've validated this idea with any studios, and if so, how? Or is the 10-20 hrs mainly focused on building?
As an aside (and maybe this is my inner Unix proponent talking), architecturally it would be much cooler if some of these things were separated into smaller microservice-style products, e.g. a URL that you pass a YouTube URL to and it gives back an "article" with video and transcript. Then you can chain that URL with another that gives a GPT-3 TLDR on top (perhaps even passing your own API key to keep provider costs down/free). Seem like killer use cases for Cloudflare Workers. If in the end everything's RSS, users can have their choice of readers and still have cool features, though of course that would make your product less compelling.
The other big positive is that the closer PWAs are to native apps in functionality, the less of a stranglehold Apple and Google will have over app distribution.
For the sake of your sanity, minimise the number of interactions you need to do with the app stores. Submit a bare bones app to the stores with all the native libraries you might need, then live the rest of your days on OTA updates (expo-updates, codepush, etc). This is against store policies but everyone does it and I've never heard of an app being taken down for it.
Using the same methods to measure wildly diverse people is a tragedy that causes individuals who could otherwise contribute to society in very meaningful ways to have fewer doors open to them.
Personally, I dream of a future where 90% of content is delivered over RSS or similar and the middle man (bloated web pages) are cut out entirely.
I've had some fun with this before where a developer with a clearly Chinese accent, and of course no webcam, posed as German (mispronouncing his own name) and freaked out when I switched to conducting the interview in German. Of course I notified the person whose identity he stole and reported the profile to Upwork, but it's a drop in the bucket of the scams.
Afterwards, when I tried to validate this as a product (libfabric.com) I realised that I'm trying to solve a problem that nobody has, except for a very small niche. The main problem that developers of large-scale networked games have is acquiring players. They use whatever existing service+SDK (like Proton) for networking and don't think about it. Once they have good traction, then they can afford scalable infrastructure that others have already built, of which there are many.
There aren't as many clients as you think, and the majority of them are quite bad. The only client with any firepower behind it is Element, and the UX is really not great there, and there are a lot of critical bugs that have been open for years, with nobody with enough knowledge of the codebase able to go in and fix these (especially with E2E encryption). As far as I can tell, their $30 mil raise has gone into focusing on enterprise instead.
Matrix bridges are buggy and decaying because the main ones are maintained by basically one guy who's now focusing on building proprietary products around his work (fair enough).
This is irrespective of the whole federation side, which is also buggy, and until the setup/maintenance cost of running your own homeserver (pure P2P federation and homeserver-agnostic identities have been TODO for years!), it's not gonna catch on. Even today, Matrix is hardly decentralised -- compare the matrix.org homeserver with literally the sum of all other homeservers and you'll see.