Sesi Tanya & Jawab Hari ini hadir untuk memberi kami SuperUser - subdivisi Stack Exchange, pengelompokan komunitas situs web Tanya-Jawab.
Pertanyaan
Pembaca SuperUser, Kyle Cronin ingin tahu apakah teknik obfuskasi email seperti itu layak untuk kerumitan:
Most of the time when I see someone post their email address online, especially if it’s a personal address, they use something like
me [at] example [dot] com
instead of the actual email address ([email protected]). Even top members of this community use similar styles in their profiles:
jt.superuser[AT]gmail[DOT]com
quixote dot su over yonder near that gmail place
The typical rationale is that this kind of obfuscation prevents the email address from being automatically recognized and harvested by spammers. In an age where spammers can beat all but the most diabolical captchas, is this really true? And given how effective modern spam filters are, does it really matter if your email address is harvested?
Mengingat bahwa itu merepotkan untuk manusia sebenarnya yang ingin Anda ajak berkomunikasi (dan mungkin tidak terlalu merepotkan bagi bot penuai yang ingin Anda hindari), ada baiknya menggali lebih dalam untuk mengetahui apakah teknik tersebut benar-benar efektif.
Jawabannya
Kontributor SuperUser, Akira menawarkan studi tentang masalah ini untuk mendukung penggunaan obfuscation:
Some time ago I stumbled upon the post of someone who created a honeypot and waited for differently obsfucated email-addresses coming back:
Nine ways to obfuscate e-mail addresses compare
CSS Codedirection 0 MB
moc.elpmaxe@zyx
Tampilan CSS: tidak ada 0 MB
xyz
@example.com
Enkripsi ROT13 0 MB
[email protected]
Menggunakan AT dan DOT 0,084 MB
xyz AT example DOT com
Membangun dengan Javascript 0,144 MB
var m = 'xyz'; // you can use any clever method of m += '@';
// creating the string containing the email m += 'example.com';
// and then add it to the DOM (eg, via $('.email).append(m); // jquery)
Mengganti ‘@’ dan ‘.’ Dengan Entitas 1,6 MB
[email protected]
Memisahkan E-Mail dengan komentar 7,1 MB
xyz@contohcom ?> var13 ->
Urlencode 7,9 MB
xyz%40example.com
Teks Biasa 21 MB
[email protected]
Ini adalah grafik statistik asli yang dibuat oleh Silvan Mühlemann, semua kredit berjalan ke arahnya:
Kontributor ak86 membebani, mencatat bahwa apa pun yang Anda peroleh melalui obfuscation Anda kehilangan melalui ketidaknyamanan untuk diri sendiri dan sesama emailer Anda:
There was an interesting article by Cory Doctorow recently on this subject here which argued that email obfuscation doesn’t serve much purpose, and a more optimal approach is intelligently managing the spam you get. TL;DR version:
- The objective of this entire exercise is not to reduce the amount of spam you get in your email, but the amount of spam you manually have to remove from your inbox.
- Email obfuscation is a constant battle to come up with ever sophisticated bot-proof, human-readable encoding, and is a drain on the productivity of both the creator, and the correspondent.
- “Almost any email address that you use for any length of time eventually becomes widely enough known that you should assume all the spammers have it.”
- “The convenience of stable, easily copy-pastable email addresses” wins over trying to hide from the spambots.
Memiliki sesuatu untuk ditambahkan ke penjelasan? Bicaralah di komentar. Ingin membaca lebih banyak jawaban dari pengguna Stack Exchange yang paham teknologi lainnya? Lihat diskusi lengkap di sini.