i'm looking @ different ways use various web/internet technologies in order able identify , blacklist user of website rather host. if didn't make sense, let me explain little:
as might aware, sites (particularly forums , message boards) have unwelcoming visit of spammers every often. forum moderators able blacklist accounts used this, it's occurs after that's problem.
in many cases, same user able bypass blacklistings, create new account, , continue on rampage. of course, there tools such ip address blacklists, little bit knowledgeable internet typically know how obtain new address, , once again able bypass ban meant them.
another interesting method i've seen using unique encrypted cookie (at least) identify host used blacklisted user. is, when user blacklisted, server-side makes note of value in cookie, next time same host used create new account, cookie sent server can identify they're bypassing blacklist. again, problem adept users able delete browser's cookies, allowing them once again become anonymous.
so i'm looking different methods of being able enforce such blacklist, if 1 exists. i'm aware of other browser storage methods such localstorage, , plugin-based ones such "flash cookies", similar these kinds of ideas preferrable (although ideally, great able make successful identification using regular http technologies. ie. without javascript, flash, etc...).
there's fair bit of thinking in terms of "well sure, idea may not 100% foolproof since user change or delete various settings, if don't understand or realise works way, works". mean here is, example gave above use of cookies; though cookies can deleted, if user doesn't understand they're being used way, blacklist remains enforced.
you may interested website http://panopticlick.eff.org/, , report containing mathematical things way fingerprint browser based on data collected.
you can check tools used new html5 database storage, 1 used by ringleaderdigital here's opt-out link may usefull better privacy plugin firefox.
this reading can give quite lot of technical details on how use lso flash cookies or local databases. , can read there or on wikipedia page on lso javascript tools can used handle flash cookies, dojo framework.
you should try handle "do not track" policy, see faq. users send headers telling you should'nt try track them. in terms of blacklisting can become problem. maybe should try build tracker, compare blacklist , throw if cannot find him there.
Comments
Post a Comment