chuckroast
Subscriber
Worst case, use a free VPN like Proton that will make it look like you originate from one of their countries of choice.
Thanks npl and snusmumriken
npl it just seems strange a configuration on the server side would be the cause when not one person so far has reported an issue Are you able to access it yourself?
My impression but I may easily be wrong is that on a relatively static site like unblinkingeye which has remained the same for many years in a form of stasis so to speak, would be having any work done to it
Does Geopeeker give a real time view of the situation in each of the countries shown? So if I link to it right now it shows me any problems with unblinkingeye right now? I can see no change from about 4 hours ago
snusmumriken Your suggestion is one that may hold out the best hope but as things stand the Firefox solution, if that is the solution, only lasts another 6 weeks
I looked but could not find any assurance from Firefox that it is likely to extend its support for Win 7 beyond another 6 weeks but it is something to consider as it may be the only way
I'll sleep on it
pentaxuser
Thanks npl I have just refreshed and now Singapore now just has the revolving circle so the situation is worse than before but when I tried Photrio all the sites it gives you can now access Photrio with the exception of Virginia which say "render unavailable" and Singapore where the circle is still revolving so that would seem to indicate that maybe unblinkingeye is more difficult to access than Photrio but can take it that there is definitely a problem with unblinkingeye and will it be one that the configurers know about and are working on?
So is it as simple as waiting for a few days for a fix?
pentaxuser
On the principle that fooling the system sometimes works, try opening the page by typing just "unblinkingeye" and then Ctrl+Enter.
Worst case, use a free VPN like Proton that will make it look like you originate from one of their countries of choice.
Thanks for the advice on trying other browsers. snusmumriken's suggestion on Firefox may prove to be the best browser in it still provides support for Win7 and may do so post August this year but it has not declared its hand on this yet
However the pessimist in me says that my original thought that older unchanging sites should be more likely to work on former Windows may be naive. Indeed it may be that due to its age and its not generating any revenue that I can see, makes it less likely to change its configuration to accommodate users of older Windows
It may be simpler and thus cheaper to just exclude users of older Windows. It's annoying not to be able to access it but it is far from disastrous
pentaxuser
It is much more likely that your browser - which stands between Win7 and the site - is no longer letting the two work with each other, because the combination of both the security vulnerabilities of Win7 and the security vulnerabilities of the old site is just too much!
I suppose the crucial question which I should have posed is : If there is still anyone on Photrio still using Win7 can they please try to access unblinkingeye and let me know if they had any success?
Thanks
pentaxuser
Windows 7 really doesn't have anything to do with this. Websites in general don't care what OS runs on the machine that the client uses. The risks of an outdated OS are on the client's side, not so much the server's side.It is much more likely that your browser - which stands between Win7 and the site - is no longer letting the two work with each other, because the combination of both the security vulnerabilities of Win7 and the security vulnerabilities of the old site is just too much!
This can sometimes helps if the problem is specifically related to SSL. There's no indication here that this is the case. However, many browsers are now starting to categorically block non-SSL traffic at least on public networks.I have had similar problems with some websites. My solution is to remove the security tag from the https: address.
Coming back to this: this is really a misunderstanding. The 'secure' bit refers to the traffic itself, not so much website content. It's also intended to prevent the situation where e.g. malicious scripts pretend to be the unblinkingeye.com server and try to inject their code to take control of the client machine and/or collect data from it. It doesn't matter what the website is used for originally. Also, the website is not a static page; it's loaded with ads served through Amazon and Google and it features an integrated Google search engine that's actively loaded on every page. There's a number of scripts running on the site and those inherently bring risks of malicious code execution, especially if someone manages to spoof Google or Amazon traffic.What I find strange is that unblinkingeye is largely a site which has changed little in all the years I have used it. It is an almost a static site where there is little happening and where no financial transactions occur so not a lot for it to worry about in terms of needing to keep it "secure " in the same way as a transactional site such as say Amazon
I looked at the site using Safari's Developer mode. If you scroll down to the bottom of the main HTML page, there are several links to online gambling platforms, including some Russian or Russian-speaking ones. What's all that about? I tend to regard ads for gambling sites as indicative of a dodgy website. There's no sign of such ads actually appearing when I visit UnblinkingEye, though, perhaps because of the adblocker I'm using.Windows 7 really doesn't have anything to do with this. Websites in general don't care what OS runs on the machine that the client uses. The risks of an outdated OS are on the client's side, not so much the server's side.
@pentaxuser I do not recommend running an outdated version of Windows on a machine that is actively used to surf the web. On the other hand, it does not explain this particular problem.
This can sometimes helps if the problem is specifically related to SSL. There's no indication here that this is the case. However, many browsers are now starting to categorically block non-SSL traffic at least on public networks.
Coming back to this: this is really a misunderstanding. The 'secure' bit refers to the traffic itself, not so much website content. It's also intended to prevent the situation where e.g. malicious scripts pretend to be the unblinkingeye.com server and try to inject their code to take control of the client machine and/or collect data from it. It doesn't matter what the website is used for originally. Also, the website is not a static page; it's loaded with ads served through Amazon and Google and it features an integrated Google search engine that's actively loaded on every page. There's a number of scripts running on the site and those inherently bring risks of malicious code execution, especially if someone manages to spoof Google or Amazon traffic.
What's all that about?
Surely it wouldn't normally be written into the HTML? Or is this actually what you normally get if you use a website builder, or get someone else to do it? (My only experience is of coding my own webpages.)Just normal ads on a website whose owner has a hands-off approach and hasn't indicated they want no gambling ads.
Photrio.com contains affiliate links to products. We may receive a commission for purchases made through these links. To read our full affiliate disclosure statement please click Here. |
PHOTRIO PARTNERS EQUALLY FUNDING OUR COMMUNITY: ![]() |