@EricHubbell@MengTo Scenario A - SSL not deployed everywhere
Some servers have valid cert
Some don’t
You’re hitting a bad on
Scenario B - DNS / routing inconsistency
Your ISP or region resolves to a broken IP
Others resolve to a working one
Scenario C - misconfigured proxy after backend failure
@EricHubbell@MengTo Short answer: you’re not crazy — this is almost certainly not your fault, and you don’t need to “hack around” it. What you’re seeing (Supabase error → now SSL / Safari refusal) is a classic backend + SSL misconfiguration or partial outage. "ChatGPT"
@MengTo @blossomcodes_ Can you look into the issue I have been commenting about the last 3 weeks? For some reason your site won't open in any of my browsers after I logged in the first time I cant get in since, keeps saying
Respect the history, but the web isn’t frozen in ’95. Pretext isn’t a “thick client, it’s precision tooling for layouts CSS can’t handle: multi-language, emojis, virtualization, AI-driven rendering. That isn’t strangling the DOM, more like unlocking what the Web already can do, faster and smarter.
@sama I cut on the voice message by accident trying to hit the mic and so I x’d out and it literally cleared my session from like 75% of that chat conversation, like completely gone. I don’t imagine your company can recover that?
@NamebaseHQ It’s still the 31st in the U.S., whose time zone we talking, sites already down still had some things to do before midnight or does that not matter 🤝?