![](https://lemmy.world/pictrs/image/94c74e9b-3514-482f-ba31-a66bc7858270.png)
![](https://lemmy.world/pictrs/image/13c64711-f6bb-429b-a54a-4e65e4e37046.png)
I use this installable web app for cleaning extra parameters from links - https://linkcleaner.app/
Adds a share target to Android once you install it as well, makes it easy to send links to. Open source too!
Hello World!
I use this installable web app for cleaning extra parameters from links - https://linkcleaner.app/
Adds a share target to Android once you install it as well, makes it easy to send links to. Open source too!
It was a server-side block, from Cloudflare (security rule specifically). I’m very familiar with it, having used the same service over a decade. They are able to tweak the overall security level, or specific WAF rules for the endpoint in Cloudflare. They also have analytics that will show them exactly how many cancellation requests would be blocked. The fact that they totally ignored these details in my ticket, is concerning.
Maybe, but it would also be very easy to blame on misconfiguration / mistake. Honestly, it wouldn’t surprise me if the behavior itself isn’t purposeful, but ignoring / not fixing it is. I’ve definitely seen such behavior at other companies, where they drag their feet on fixing a bug that is bad for the user, but helping them.
On a related note… I went to cancel a membership a few weeks back, and the site displayed a message “you don’t have an active membership to cancel”. I thought it was strange, so I checked out the network requests being made, and turned out the cancel API call was getting blocked for “security reasons”. Nothing else on the site was blocked for me, just the cancellation endpoint.
I opened a ticket, and it took them nearly 2 weeks to respond, and there was zero acknowledgement on why cancellation would be blocked.
Not sure if it’s a purposeful dark pattern, but it sure seems like it!
Worth noting that this should not affect you if you are only using tunnels (no DNS entries / open ports).
Netdata is fantastic, but not sure I’d call the UI mobile friendly (unless I’m missing something? 😂) To me, that’s really one of the only weak points with it.
They actually recently opened a beta for sending emails from Workers as well. There are already a few projects to make use of this, examples:
I’ve looked at mTLS certs as well, but think you’d run into the same issue there as Service Tokens (app needs to support it).
It really is a shame, because Cloudflare Tunnels / Access is great otherwise. Just troublesome to have non-browser access.
You can use Service Tokens with Cloudflare Zero Trust (Access). Unfortunately, the companion App then has to support setting custom request headers, in order to send the token. Not many support this in my experience.
The only other option would be to use Basic Authentication, instead of Cloudflare Access. This isn’t as secure, but would be supported by most Apps (since you can simply inline user:password in the API URL). You can even setup a Cloudflare Worker to add basic auth to any Route you want.
Ideally, would love some hybrid of these approaches, where I can keep Access enabled, but override with basic auth for ‘legacy’ apps. Don’t know of a way to do this though.
Edit: Forgot to mention a third option, if you just want access while home, you can setup a bypass in Cloudflare Access policies for your home IP address. Then if you really need access when remote, you could also use VPN, but not as seamless of course.
It’s an installable PWA, click the … Menu in Chrome browser and choose “install”. Hope this helps!