Ugh I didn't realize clicking randomly on the heart would take me to a porn site. The only red for me was HN.
HN is in the list? I'm here all the time and I don't see a red HN dot.
Show HN: A Simple Website for Checking Cloudbleed from Browser's History
21–29 of 29 posts
Re: Show HN: A Simple Website for Checking Cloudbleed from Browser's History
#22I've been to hackernews and transferwise, but I don't see red blocks for them.
Re: Show HN: A Simple Website for Checking Cloudbleed from Browser's History
#23Ugh I didn't realize clicking randomly on the heart would take me to a porn site. The only red for me was HN.
HN is in the list? I'm here all the time and I don't see a red HN dot.
It's because he broke it. He changed it so it puts www in front of all domains. But that won't work for all domains
Re: Show HN: A Simple Website for Checking Cloudbleed from Browser's History
#24Earlier quoted context omitted.
For a temporary fixed, I prepend 'www.' to all the links. It could be improved by having all the related frequently-used url of the sites listed e.g. other subdomains. Thanks!
This breaks where the link is a subdomain e.g., www.news.ycombinator.com
Fixed it. Thanks!
Re: Show HN: A Simple Website for Checking Cloudbleed from Browser's History
#25Interestingly, news.ycombinator.com is showing as red.
Re: Show HN: A Simple Website for Checking Cloudbleed from Browser's History
#26I've been to hackernews and transferwise, but I don't see red blocks for them.
Fixed the url of hacker news and changed the url of transferwise. Thanks!
Re: Show HN: A Simple Website for Checking Cloudbleed from Browser's History
#27Why Cloudbleed and not Cloudburst? Seems like a missed opportunity (though I understand it's a reference to Heartbleed.)
Re: Show HN: A Simple Website for Checking Cloudbleed from Browser's History
#28Re: Show HN: A Simple Website for Checking Cloudbleed from Browser's History
#29One thing I didn't see discussed at all (mind you, there were thousands of comments on various threads) was crowd sourcing the search for exploited domains in people's browser cache (as opposed to search engine and archive caches).
If I understand this, it "simply" matches against the already known list of known to have leaked domains. Right? But what about potential other leaks that didn't get cached by search engines but that might live in people's caches??