That's why I've gone to using open models, they are getting there slowly. A bit much of hand-holding but that's fine by me. If a customer of mine decides to use Google's models, I will have them sign a disclaimer that I'm not responsible of them getting insta-banned or similar. I just can't recommend it.

- Making assets embedded as base64 (img src the header logo as base64, all CSS should be inline, etc.).

- Leveraging CSS as much as possible (if you use animations and transitions, use CSS as much as possible for these, avoid JS for them).

- Make sure your website is mostly rendered on the backend. If you're to have JS, your website should work without it.

- Security becomes REALLY fun, as in, avoid XSS, CSRF, SQL Injection attacks and any other injections as much as possible.

As someone summarizes in another comment[0], keep the chattiness as minimal as possible. By chattiness I understand they mean, pack as much data as you can in the same Keep-Alive connection. Avoid making new HTTP requests as much as possible, as each one might get assigned to a new Onion route making things slow.

If you can ship your website to the browser in a single connection, you've won.

I've always been impressed by performance of these big Onion sites, they really push the limits of software engineering creativity, given these constraints and nature of Tor.

--

[0]: https://news.ycombinator.com/item?id=49872320

EDIT: Formatting of bullet points.

Gmail is not particularly difficult in terms of software engineering. The moat with email servers is IP address reputation.

I could, today, install Postfix SMTP and some IMAP as well, and watch my email all go to spam directly, if delivered at all (ISP might block them).

I am losing karma because of my opinion, but that doesn't make it any less true. After all, you can just observe how the feedback goes against border radius. Hardly it will change back now to edgy corners like it's supposed to be.

Respectfully, that doesn't make any sense.

That logic doesn't follow, sorry.

You can be inclusive, yet not become the thing you're inclusive to. That's a mental stretch.

If I tried to keep up, I'd be run over. It's too much input for the normal individual I am.

Not necessarily, great engineers do also ship temporary code they didn't have the time to trim.

Our process is of 1) make it work, 2) make it right and 3) make it fast; not necessarily that engineer had time for the 3rd step.

And unlike Telegram, for a WhatsApp bot you need to apply with a bunch of paperwork. If you're an SMB, you got little chances of ever getting access. They'll tell you to go with their Technology Partners and make a chatbot with these other BigTech companies like Freshworks, etc.