HN user

aeharding

1 karma
Posts12
Comments225
View on HN

I’m being bitten by this right now. Registered a domain in personal account, want to move to a different cloudflare account and I can’t since that’s completely unsupported. The recommendation is to transfer out to external registrar, wait 60 days, transfer back in.

Can’t even change the name servers, since that’s not configurable with cloudflare.

And I can’t move the domain out of cloudflare so I can change nameservers for 60 days because I just registered the domain…

Support very unhelpful, situation sucks.

Nice. I wish there was some web API to record geolocation in the background over time. I understand the privacy implications, but if it was an API only available to installed PWAs, and with an indicator similar to native apps when recording geolocation in the background, I feel like that would be acceptable.

I just really hope the onboarding experience is improved. Right now it's very convoluted and messaging is extremely difficult, in some places impossible.

For example, in SFSafariViewController there is no “add to home screen” button in the share menu, but in actual safari there is. Despite them both being web view experiences controlled entirely by Apple.

(And you can’t detect SFSafariViewController vs Safari as a web app, so good luck onboarding users for your PWA.)

The share button also has actions that vary unnecessarily.

For example, in SFSafariViewController there is no “add to home screen” button, but in actual safari there is. Despite them both being web view experiences controlled entirely by Apple.

(And you can’t detect SFSafariViewController vs Safari as a web app, so good luck onboarding users for your PWA.)

the move from a persistent background.js script to a sevice-worker will just make a number of use-cases impossible or very hacky

Yep.

Chrome is even crippling some of their own APIs, like chrome.tabCapture (not available in service workers, and in mv3 will be "foreground only")

AKA, if you want to use chrome.tabCapture in mv3, you have to run it in a tab. And because that tab can be closed at any time, you need to serialize megabytes of data to the chrome.storage api every few seconds.

Yup. This drunk driving detection is just a symptom of the larger problem: car dependency.

You don’t need alcohol detection in cars if everyone can just walk or bus safely to their neighborhood bar or friends. Virtually nobody wants to drive drunk, but it’s basically encouraged by the way we design our cities.

Because in this country the options are

1. Buy a car because it’s required in order to literally feed yourself, or

2. Live in one of the highly desirable, expensive pre-war neighborhoods that remain walkable

Many Americans can’t just “give up cars” even if they wanted to. Car dependency is literally codified in out zoning and street building (MUTCD)

Maybe if car dependency wasn’t such a requirement in order to live, maybe if everyone could easily walk to the bar, we wouldn’t need alcohol detection in cars.