I've recently switched my blog over to Bear, and I've been having a great time with it. One thing that Bear does lack is native comments. This is by design, and a number of solutions exist to...
I've recently switched my blog over to Bear, and I've been having a great time with it. One thing that Bear does lack is native comments. This is by design, and a number of solutions exist to generate a comments section onto a given page. However, a growing trend in the community is to put "Reply by email" or similar at the bottom of the comments section, often with their personal email address in plaintext in a <a href="mailto:"> tag. I quite like this idea, and I wanted to try it myself, but I know through bitter experience that having a plaintext email address on the open web is just asking for endless spam, so I went looking for solutions to the problem that didn't involve putting together a form, and found this page. It's interesting to look at what works and what doesn't, and I was surprised by how well some of the more trivial solutions work!
One thing I once did to protect my email was split it into a bunch of elements (one for each character) that weren't actually in order, and then use css properties to make the scrambled characters...
One thing I once did to protect my email was split it into a bunch of elements (one for each character) that weren't actually in order, and then use css properties to make the scrambled characters display in the right order to form the full email. Downside of this was that copying didn't work properly. Based on this blogpost though, my solution was way too overengineered and simpler things are enough, which is great to know for the future
I like this article. The SVG method being better than the HTML entities surprised me a little bit (I know sample size is small but still). I'd expect most scrapers to be something like:...
I like this article. The SVG method being better than the HTML entities surprised me a little bit (I know sample size is small but still). I'd expect most scrapers to be something like:
html_content = download_page();
parts = html_content.split_by(/* whitespace or HTML tag stuff*/);
for word in parts {
if word.contains('@') {
if word.validate_email() {
send_spam(word);
}
}
}
Where if the SVG element is in html_content, it would probably catch it.
The "remove .fluff" downside might actually be a benefit, as it would also filter out people that don't read things when commenting :D
I've recently switched my blog over to Bear, and I've been having a great time with it. One thing that Bear does lack is native comments. This is by design, and a number of solutions exist to generate a comments section onto a given page. However, a growing trend in the community is to put "Reply by email" or similar at the bottom of the comments section, often with their personal email address in plaintext in a
<a href="mailto:">tag. I quite like this idea, and I wanted to try it myself, but I know through bitter experience that having a plaintext email address on the open web is just asking for endless spam, so I went looking for solutions to the problem that didn't involve putting together a form, and found this page. It's interesting to look at what works and what doesn't, and I was surprised by how well some of the more trivial solutions work!I love this resource, I use the JS conversion method from here myself! Really quick and easy solution.
One thing I once did to protect my email was split it into a bunch of elements (one for each character) that weren't actually in order, and then use css properties to make the scrambled characters display in the right order to form the full email. Downside of this was that copying didn't work properly. Based on this blogpost though, my solution was way too overengineered and simpler things are enough, which is great to know for the future
I like this article. The SVG method being better than the HTML entities surprised me a little bit (I know sample size is small but still). I'd expect most scrapers to be something like:
Where if the SVG element is in
html_content, it would probably catch it.The "remove .fluff" downside might actually be a benefit, as it would also filter out people that don't read things when commenting :D