Re:The top-ranking HTML editor on Google is an SEO scam
by geek_at on Tuesday June 08, 2021 @08:34AM
(#27434288)
Wow that sucks. It's not just HTML Cleaners though. A few years ago (before snowden) I analyzed free proxy servers and found that most of them blocked https and many even injected JS or HTML into all requests [1].
I also wrote a tutorial on how you can build an infecting proxy too [2]. Doesn't work anymore though since HTTPS is everywhere. Thank god
[1] https://blog.haschek.at/2015-analyzing-443-free-proxies [2] https://blog.haschek.at/2013/05/why-free-proxies-are-free-js...
[dead]
Re:The top-ranking HTML editor on Google is an SEO scam
by dang on Tuesday June 08, 2021 @01:33AM
(#27430961)
Please don't be an asshole in HN comments. We're trying for a different sort of internet here.
Re:The top-ranking HTML editor on Google is an SEO scam
by fossislife on Tuesday June 08, 2021 @10:51AM
(#27435938)
Just my thanks for keeping HN so absolutely clean, in comparison to other online forums.
Re:The top-ranking HTML editor on Google is an SEO scam
by wolfd on Monday June 07, 2021 @08:59PM
(#27429418)
Everyone starts somewhere.
Re:The top-ranking HTML editor on Google is an SEO scam
by Noumenon72 on Monday June 07, 2021 @08:37PM
(#27429266)
And without version control, or they could have just looked back to see how the links got in there.
In 2015 I was fired because some issues on a site that I was working on because some friction with the company owner. Two months before I was fired I reported that some links to others sites non related to our service was on the initial page (some porn and some scams pages). After that I heard from my ex-coworkers that a manager from another area from the company told that I was fired because I was linking porn on some pages from our service. I didn’t knew at the time that those tools existed, but only today I realized that it is an option.
I was really sad with that manager and didn’t understood the reason to lie to my friends the reason of my demission. But is nice to know what may have caused the issue. Better late than never hahaha.