dopp0

> But if your terminal can't keep up with your typing speed there is something deeply wrong with it. For the poor sools that had to work in VDI with radio link...

I have fond memories of scripting for mIRC, it was one of my first dev languages, together with clipper and delphi/pascal.

the world belongs to the braves

I think what he meant is that the wildcard is not supported in the origin itself, for instance: https://*.somedomain.com.

per documentation, it's either "*" or "https://subdomain.somedomain.com"

if it's just travelling: most streaming services allow downloading music so you can listen offline for some time (ie spotify)

why 443? are you assuming ssl here? serious question, I'm not sure. But if it is, wouldn't it be hard to disregard the weight of SSL in the metric?

> fairly robust DNS setup that consists of not only giving A records to all my hosts

looks nice, can you give more details on this? tks!

which LLM are you using for those frontend usecases? chatgpt? and you ask in prompts for some framework such as tailwind?

Thanks for the memories. Good old times I was programming in SuperWaba for palmOS!

if they were obfuscated the urls the app itself would need to process it to un-obfuscate, then the performance would take a hit, but I get your point. It's just the wrong service to host this.

PS: could not check the link, as my country blocked twitter.

you can check the CHANGES.md [1] or here [2]

[1] https://github.com/openssl/openssl/blob/master/CHANGES.md [2] https://github.com/openssl/openssl/compare/openssl-3.3.2...m...

for chrome users, to bypass this: just type "thisisunsafe" while focused on the error page. not very helpful in this scenario, but for other HSTS issues it might be! 2c

I think this concept you mentioned would be called sharding? It's kinda required for apache Kafka and others.

1. Download PDF from publisher. 2. Open it in your PDF viewer. 3. Press print. 4. Physically print the document. 5. Re-scan the printed PDF pages. --->6. Run OCR to rebuild the document 7. profit!

7. Compress the PDFs (ghostscript).

it's not funny when you compare "profits over other's knowledge" to "share knowledge without profits", it doesn't make sense at all. potatoes and oranges

hence the "predict", not "infer"

but never forget that AWS uses us-east-1 to host core services that, when they go down, they take almost the whole thing down, no matter which region.

What you don't consider about the MVP is that you can release early/release often and then re-evaluate and improve upon it based on data, not your mind or guesses.

Taking 18 months to release it might cause you to waste a lot of valuable time with features/requirements that does not deliver any real value to your customer, and the competitors can gain this space delivering a much less complete product, with less quality, but with the right features because of MVP concepts.

Not teasing in any way, but just 2 cents to consider, as I see a LOT of issues with the MVP approach.