Stop arguing about whether AI ruins craft.
Fix the incentive structures so that increased productivity buys humans time, not disposability.
Then see what kind of craft emerGe
Generally good thinking, but few "real world" notes
A) you first need to run the service to get any customers
B) this might take long
C) you maybe don't want / can't get VC money at this stage
D) you maybe are not the most advanced dev who can properly utilitize s3 from I/O perspective, getting you to higher costs than possible
E) there might be a time period between introducing the service and getting traction which yields enough feedback, so you can start adding more business features
F) when you are burning your own money, you are more senstive to the cost side - which is not ultimately wrong
This approach leads us exactly where we are - having 100x more HW resources, yet page load times still suck ;)
And simple request to webdev - would you please make your js app build any faster then 5min always yields the same, confused look - like, where in the mess of 100+ libs should I start?
Umm, you make it look like a trivial problem to solve, which IMHO is not the case when you take the fact you can risk life in prison or death in to the account. I'm from ex-communism country - where a lot of successful broadcastings happened, nevertheless, they got always identified at the end of the day - and then, guess what happened. When you are facing such restrictive conditions, even signal itself is good cause to get you in trouble - no matter whether the information carried is understood/sniffed or not, bounced or not. Anti-triangulation measures you are talking about have IMHO no practical use as long as anyone on the other side is using mobile radio signal detectors. Or if you know about real world application - I'd love to learn about it. Cheers