Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2025 Poal.co

520

I often develop websites and this morning I'm being bombarded with annoying browser alerts as I test my website:

This website may be harmful [Continue anyway] [Go back]

This dialog is definately coming from my mobile browser. The url is http://192.168.1.123:5003/page

Specifically, I implemented a swipe feature to navigate back and forth to various pages. As I swipe, this dialogue pops up.

I believe browser vendors are starting to conspire to block people from visiting certain web sites. In this case, the browser may be using heuristics to determine when to display this message. I'm thinking Google is already conspiring to establish some sort of protocol in Chrome to block websites that aren't "verified".

Buckle up everyone!

I often develop websites and this morning I'm being bombarded with annoying browser alerts as I test my website: >This website may be harmful [Continue anyway] [Go back] This dialog is definately coming from my mobile browser. The url is http://192.168.1.123:5003/page Specifically, I implemented a swipe feature to navigate back and forth to various pages. As I swipe, this dialogue pops up. I believe browser vendors are starting to conspire to block people from visiting certain web sites. In this case, the browser may be using heuristics to determine when to display this message. I'm thinking Google is already conspiring to establish some sort of protocol in Chrome to block websites that aren't "verified". Buckle up everyone!

(post is archived)

[–] • 4 pts

Clean up third party js that are calling home and are tracking you, but the key is to host them locally, like Poal and Vid8 do. So you’re sure they don’t get silently updated.

[–] • 0 pt

Yeah, didn't jquery have that problem? Like all of the websites using it were instructing the client to download it from jquery, a completely different website.

[–] • 2 pts

I'm using an old sanitized jquery for a few functions (I'll eventually convert to pure js)

[–] • 3 pts

I maintain internal sites on a corp network. Chrome can be picky about those at times.

For my personal use, I keep a version of Arora around, it doesn't understand modern SSL and doesn't give a shit that 192.168.1.223:5593 is insecure.

[–] • 3 pts

made Arora, it's obvious. https://pic8.co/sh/XwIXeV.png

[–] • 2 pts

Perhaps....

[–] • 1 pt

You fake and stupid gay bird, earth is flat and gay!

[–] • 1 pt

Well, shut it down, the goyim noticed us.

[–] • 1 pt

I get the "http not https website of hell" warnings a lot. Sonsabitches. Go back old school bbs's and frigging dialup (insert modem sound).

[–] • 1 pt
[–] • 1 pt

Or did you just recently register the domain and the ssl certificate hasn’t resolved everywhere yet?

This happens to me when I have a 2AM brainstorm, register the domain, then get to setting up the framework.

[–] • 1 pt

Well, I'm running it via my IDE Visual Studio, and I don't have an SSL for it. It could be my browser doesn't like that, but I do use localhost and that is supposed to be OK not to force SSL.

[–] • 1 pt

Always some little annoying shit getting in the way of progress. Godspeed.