We just need "Keywords" to help ChatGPT decide what to include in summaries. This will lead to keyword stuffing. And eventually it comes full-circle with SEO-like word soup so that ChatGPT is forced to output recipe blog spam. It's perfect.
Working in video production, I know there are a lot of videographers and photographers "abusing" the unlimited nature of this service. It's not my business how BackBlaze does things, or if the usage falls within their acceptable use policy, but I see so many in my industry brag about the insanely cheap rates BackBlaze offers on their computer backup.
From my armchair, it seems like a bunch of personal users subsidize the freelance photo/video production industry. I wonder why BackBlaze doesn't give those extreme users the boot? Or, put in place a reasonable storage limit (e.g., 5 TB or something that 95% of users will be okay with.) I like BackBlaze but it always rubs me the wrong way when I see people in Facebook groups using the Computer Backup solution as if it were B2 or a higher-tier service.
Neat app, I could see myself using this. However, one thing that makes me hesitant is bitrates and deeper information on file exports. Does it maintain the same bitrate as the original video? I see you have a lot of information (Cmd + F) on "export" but nothing regarding bitrates. An FAQ page would be useful instead of the long single page. I work in video production so bitrate is an important thing-to-know before purchasing. Anyways, cool app.
I believe my app (launching soon) is close to solving your "what do I want" but currently wrapping up the API. Are there some other communities, links to other blogs or people that are doing what you are doing? (Tracking this much data, etc.)
In my benchmark testing, SSL appears to be the bottleneck; e.g., Apache vs. Nginx does not really matter. I assume the benchmarks above 10,000 RPS are not using SSL and regular HTTP? How are people doing benchmarks at 10k-100k RPS?
If you haven't tried SQLite, please do. For years I ignored SQLite and used MySQL (it does the job) but once you see how fast SQLite is, and advantages of having a DB contained in a single file... just go play around with SQLite instead of ignoring it for years like me. It's neat.