TSR Privacy Violation
snowbawl:
My brain hurts.
SiuPang:
There's one thing I knew about TSR: they were bad;
and there's one thing I didn't know about TSR: they had become that bad!
Oh gosh! It's such a shame to the Sims community when the so-claimed largest and oldest Sims fan site has grown that nasty and hideous >:(!!!
Let's mourn for the days when there are no such sites! :-\
Noukie:
Quote from: wes_h on 2009 March 31, 15:32:44
Quote from: Lorelei on 2009 March 31, 07:11:54
In other words, U R WRONG.
You are too wrapped up in this to see that your statement is petty, whiney and proves nothing... the logs show she looked, and prove nothing about use. If you want to win arguments and converts, use provable assertions. If you just want to be perceived as a whiney bitch that dislikes some ho, well, carry on.
So if they are 'looking at' content, we should assume the same for everyone else that goes to the Booty to 'look at content' they had nothing to do with.
Marhis:
Quote from: wes_h on 2009 March 31, 15:32:44
the logs show she looked, and prove nothing about use.
Code:
69.242.46.150 - - [05/Oct/2006:02:34:53 +0800] "GET /booty/sml/SML_Set2_AphelionTV.jpg HTTP/1.1" 200 8386 "http://paysites.mustbedestroyed.org/booty/sml/" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; {526A1FA0-F6B7-6529-D79A-81A3DF9B9B97}; .NET CLR 1.0.3705; .NET CLR 1.1.4322; Media Center PC 3.1)"
Roughly translated, she had a succesful response from the server; HTTP 1.1 protocol, status code 200 means "OK". GET method means the entity SML_Set2_AphelionTV.jpg was sent in response to the client. In short, the SML_Set2_AphelionTV.jpg picture appeared on her Exploder 6.0. It was 8386 bytes long.
Code:
69.242.46.150 - - [05/Oct/2006:10:45:03 +0800] "GET /booty/wallsims/ws_pleasure.rar HTTP/1.1" 200 97382 "http://paysites.mustbedestroyed.org/booty/wallsims/" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; {526A1FA0-F6B7-6529-D79A-81A3DF9B9B97}; .NET CLR 1.0.3705; .NET CLR 1.1.4322; Media Center PC 3.1)"
Another OK in response, this time 97382 bytes were transferred. Oh, look, what kind of PICTURE is a .rar file?
But wait, she didn't download: the ws_pleasure.rar file is bigger than 97382 bytes, right?
Right. In fact...
Code:
69.242.46.150 - - [05/Oct/2006:10:49:19 +0800] "GET /booty/wallsims/ws_pleasure.rar HTTP/1.1" 206 2555733 "http://paysites.mustbedestroyed.org/booty/wallsims/" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; {526A1FA0-F6B7-6529-D79A-81A3DF9B9B97}; .NET CLR 1.0.3705; .NET CLR 1.1.4322; Media Center PC 3.1)"
Status code 206: partial content. Usually used by clients to resume a download. Typical log line when a downloaded file is big, and the protocol has to deal splitting the stream of data served. Another 2,555,733 bytes. Wanna do the math?
Is the RFC 2616 a source reliable enough, for you?
eevilcat:
Quote from: Liz on 2009 March 31, 18:51:09
I just love that, in all of this, the party line from TSR is ,"Oh yeah, we were hacked a few months ago. Must have been them."
If their member database had been compromised in any way then surely the members should have been informed about the breach at the time and advised to change their password(s). Smells like a steaming pile of kermit flailing bullshit to me.
Navigation
[0] Message Index
[#] Next page
[*] Previous page