October 30, 2005

  • 1) Ever been to someone's blogsite and they force you to login to Xanga to see their page?


    2) Or you want to visit someone's blog and you know they have a Xanga tracker and you, for personal reasons, would rather stay under the radar?


    I once wrote (actually rewrote and improved) scripts that implemented both #1 and #2.  Used them for awhile.  Shared them with others.  Then abandoned their use for myself.


    The other side of the coin, which I now share with those of you not aware of it, is that you can avoid #1 and #2 quite easily.  One way: don't visit those sites.  Another way: use an "anonymizer" or "web proxy"" to avoid engaging the javascripts that bloggers load in their Look and Feel.  Doing the latter, you'll not only avoid #1s and 2#s, but all the other annoying, resource-hogging, time-consuming scripts that are rampant throughout Xanga.


    I occasionally use an SSL (Secure Socket Layer) VPN (Virtual Private Network) anti-script access called Megaproxy.  It's $10 for 3 months, but you can try it free here.  There are others, too, such as Anonymizer, with both paid and free (upper right hand corner) versions.  Of course, the free versions are limited (usually to the amount of free surfing you can do).  But then again, this may be something you only want to engage occassionally and then the free versions are just fine.


    And, in case your wondering, my Xanga tracker, which I hosted on my own domain and called the "cRacker-tracker", though not utterly sophisticated, had, and still has, a few distinct advantages over the many other trackers. 


    First, it's not detectable by Got'em's xanga-tracker Sniffer. 


    Secondly, the logs, in the latest version, are entirely non-public so that no one else can spy on you tracking on them.  For instance, the outsourced Xanga Anti-Stalker module which is in place on my blog but which I never look at, is viewable here.  If someone else has a Xanga Anti-Stalker module, you need only insert their username in the URL to see who they are tracking.  Even Got-Em's tracker, though seemingly password protected, can be circumvented by an unpublished alias URL.


    Third, the final version of my  script was refined so that it was not liable to "tracker poisoning".  What's that?  That's when some miscreant copies your script and places it on any number of numerous other sites that get hits.  Your log then reflects not only your actual hits but all the other noise the script is collecting.  Matters can then get down to being like a whore trying to figure out who the baby's daddy is.


    Though I work in Information Security, my best buddy has always said of me: "When it comes to information systens, he can break into things as well as he can guard them."


    Hey baby, I'm your handyman.  But please, no request for codes.  I'm not "into them" anymore and find them abhorent.  And, in the end, if you can't trust, you won't be trusted.

Comments (728)

Comments are closed.

Post a Comment

notforprophet

Recent Posts

Categories

The End of Days

October 2005
M T W T F S S
« Sep   Nov »
 12
3456789
10111213141516
17181920212223
24252627282930
31