I read elsewhere that neo only tracks the ip of when you log in and out.
so when you're actually ABing, playing, etc, you don't have to be on a proxy.
so
T/F ?!?
What works and what is paused · Email is limited to account activation and password resets.
Posted 24 March 2012 - 11:28 AM
Posted 24 March 2012 - 11:28 AM
wow awkward title is awkward.
I read elsewhere that neo only tracks the ip of when you log in and out.
so when you're actually ABing, playing, etc, you don't have to be on a proxy.
so
T/F ?!?
Posted 24 March 2012 - 11:30 AM
Posted 24 March 2012 - 11:32 AM
No idea.
Posted 24 March 2012 - 11:33 AM
Posted 24 March 2012 - 11:35 AM
i hope its appropriate to ask o.o
but on codex, can admins see users' IP on any page, or is it just the login/logout?
Posted 24 March 2012 - 11:35 AM
I should add. I know someone who used this method for about 3 years and was never iced until score sending came out. I'm not saying do this as it wouldn't be hard for them to add the tracking on other pages (like buy pages).
Posted 24 March 2012 - 11:40 AM
Posted 24 March 2012 - 11:55 AM
I'd imagine that they do IP logging for when people send scores/log in or out/buying things from user shops/maybe some of the high-end main shops (like Magic), but yeah I don't know D:
It'd be awkward to send a ticket to them and ask, heehee....... >w>
Posted 24 March 2012 - 12:09 PM
Posted 24 March 2012 - 12:18 PM
Posted 24 March 2012 - 12:27 PM
Send an editorial question then? But chances are they'll never reply, or never reply truthfully. *remember to throw random meepits or plushies for higher chances*
I think I read that logging IP on login and logout on an editorial too.... can't remember.
I don't believe it though.
Edited by Turnip, 24 March 2012 - 01:26 PM.
Posted 24 March 2012 - 12:41 PM
Posted 24 March 2012 - 12:42 PM
Hi TNT! *gives you lots of cakes and cookies and hides them from the Meepits!!*
So a couple of friends and I are going to be making a virtual pet site, and were wondering a few things about how to see/prove if there are people cheating.
Posted 24 March 2012 - 12:45 PM
Probably shouldn't do that... I'm pretty sure TNT won't give ideas for a possible rival site.
Posted 24 March 2012 - 12:52 PM
Probably shouldn't do that... I'm pretty sure TNT won't give ideas for a possible rival site.
Edited by Fireworks, 24 March 2012 - 12:54 PM.
Posted 24 March 2012 - 01:15 PM
Posted 24 March 2012 - 01:19 PM
you guys know that you can see straight through most proxies right?
Posted 24 March 2012 - 01:25 PM
& very entertaining editorial question you have there Turnip! -now I kindda understand why mine are never answered-
edit: TNT would know you're lying if they saw your original question here~ :x
Posted 24 March 2012 - 02:21 PM
Posted 24 March 2012 - 05:29 PM
Yep. We have eyes everywhere. Though this requires me to sift through a large 2 GB access log....Any and every page.
Posted 24 March 2012 - 05:41 PM
2012-03-24T05:12:48+00:00 heroku[router]: GET shopworth.heroku.com/price dyno=web.1 queue=0 wait=0ms service=637ms status=200 bytes=13 2012-03-24T05:12:48+00:00 heroku[nginx]: 74.192.103.146 - - [24/Mar/2012:05:12:48 +0000] "GET /price?next=240&user=featheralley HTTP/1.1" 200 13 "http://shopworth.heroku.com/?user=featheralley" "Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20100101 Firefox/11.0" shopworth.heroku.com 2012-03-24T05:12:49+00:00 heroku[router]: GET shopworth.heroku.com/price dyno=web.1 queue=0 wait=0ms service=776ms status=200 bytes=13 2012-03-24T05:12:49+00:00 app[web.1]: 74.192.103.146 - - [23/Mar/2012 22:12:49] "GET /price?next=320&user=featheralley HTTP/1.1" 200 13 0.7648 2012-03-24T05:12:49+00:00 heroku[nginx]: 74.192.103.146 - - [24/Mar/2012:05:12:49 +0000] "GET /price?next=320&user=featheralley HTTP/1.1" 200 13 "http://shopworth.heroku.com/?user=featheralley" "Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20100101 Firefox/11.0" shopworth.heroku.com 2012-03-24T05:12:50+00:00 app[web.1]: 74.192.103.146 - - [23/Mar/2012 22:12:50] "GET /price?next=400&user=featheralley HTTP/1.1" 200 13 0.7301 2012-03-24T05:12:50+00:00 heroku[router]: GET shopworth.heroku.com/price dyno=web.1 queue=0 wait=0ms service=735ms status=200 bytes=13 2012-03-24T05:12:50+00:00 heroku[nginx]: 74.192.103.146 - - [24/Mar/2012:05:12:50 +0000] "GET /price?next=400&user=featheralley HTTP/1.1" 200 13 "http://shopworth.heroku.com/?user=featheralley" "Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20100101 Firefox/11.0" shopworth.heroku.com 2012-03-24T05:12:50+00:00 heroku[router]: GET shopworth.heroku.com/price dyno=web.1 queue=0 wait=0ms service=446ms status=200 bytes=13 2012-03-24T05:12:50+00:00 app[web.1]: 74.192.103.146 - - [23/Mar/2012 22:12:50] "GET /price?next=480&user=featheralley HTTP/1.1" 200 13 0.4426 2012-03-24T05:12:50+00:00 heroku[nginx]: 74.192.103.146 - - [24/Mar/2012:05:12:50 +0000] "GET /price?next=480&user=featheralley HTTP/1.1" 200 13 "http://shopworth.heroku.com/?user=featheralley" "Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20100101 Firefox/11.0" shopworth.heroku.com 2012-03-24T05:12:51+00:00 app[web.1]: 74.192.103.146 - - [23/Mar/2012 22:12:51] "GET /price?next=560&user=featheralley HTTP/1.1" 200 13 0.7139 2012-03-24T05:12:51+00:00 heroku[router]: GET shopworth.heroku.com/price dyno=web.1 queue=0 wait=0ms service=723ms status=200 bytes=13 2012-03-24T05:12:51+00:00 heroku[nginx]: 74.192.103.146 - - [24/Mar/2012:05:12:51 +0000] "GET /price?next=560&user=featheralley HTTP/1.1" 200 13 "http://shopworth.heroku.com/?user=featheralley" "Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20100101 Firefox/11.0" shopworth.heroku.com 2012-03-24T05:12:52+00:00 app[web.1]: 74.192.103.146 - - [23/Mar/2012 22:12:52] "GET /price?next=640&user=featheralley HTTP/1.1" 200 15 0.6381 2012-03-24T05:12:52+00:00 heroku[nginx]: 74.192.103.146 - - [24/Mar/2012:05:12:52 +0000] "GET /price?next=640&user=featheralley HTTP/1.1" 200 15 "http://shopworth.heroku.com/?user=featheralley" "Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20100101 Firefox/11.0" shopworth.heroku.com
Edited by Inkheart, 24 March 2012 - 05:42 PM.
Posted 24 March 2012 - 05:46 PM
Posted 24 March 2012 - 05:52 PM
Just to put this to rest, every single server logs all requests, by default. I can't imagine TNT would have gone to the trouble to not log, so yes, every time your computer interacts with neopets.com, your IP address goes into the logs. When you load a page, when you submit a form, when you start a flash game, when you submit a score... everything has your IP attached to it; that's just how a web server works.
2012-03-24T05:12:48+00:00 heroku[router]: GET shopworth.heroku.com/price dyno=web.1 queue=0 wait=0ms service=637ms status=200 bytes=13 2012-03-24T05:12:48+00:00 heroku[nginx]: 74.192.103.146 - - [24/Mar/2012:05:12:48 +0000] "GET /price?next=240&user=featheralley HTTP/1.1" 200 13 "http://shopworth.heroku.com/?user=featheralley" "Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20100101 Firefox/11.0" shopworth.heroku.com 2012-03-24T05:12:49+00:00 heroku[router]: GET shopworth.heroku.com/price dyno=web.1 queue=0 wait=0ms service=776ms status=200 bytes=13 2012-03-24T05:12:49+00:00 app[web.1]: 74.192.103.146 - - [23/Mar/2012 22:12:49] "GET /price?next=320&user=featheralley HTTP/1.1" 200 13 0.7648 2012-03-24T05:12:49+00:00 heroku[nginx]: 74.192.103.146 - - [24/Mar/2012:05:12:49 +0000] "GET /price?next=320&user=featheralley HTTP/1.1" 200 13 "http://shopworth.heroku.com/?user=featheralley" "Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20100101 Firefox/11.0" shopworth.heroku.com 2012-03-24T05:12:50+00:00 app[web.1]: 74.192.103.146 - - [23/Mar/2012 22:12:50] "GET /price?next=400&user=featheralley HTTP/1.1" 200 13 0.7301 2012-03-24T05:12:50+00:00 heroku[router]: GET shopworth.heroku.com/price dyno=web.1 queue=0 wait=0ms service=735ms status=200 bytes=13 2012-03-24T05:12:50+00:00 heroku[nginx]: 74.192.103.146 - - [24/Mar/2012:05:12:50 +0000] "GET /price?next=400&user=featheralley HTTP/1.1" 200 13 "http://shopworth.heroku.com/?user=featheralley" "Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20100101 Firefox/11.0" shopworth.heroku.com 2012-03-24T05:12:50+00:00 heroku[router]: GET shopworth.heroku.com/price dyno=web.1 queue=0 wait=0ms service=446ms status=200 bytes=13 2012-03-24T05:12:50+00:00 app[web.1]: 74.192.103.146 - - [23/Mar/2012 22:12:50] "GET /price?next=480&user=featheralley HTTP/1.1" 200 13 0.4426 2012-03-24T05:12:50+00:00 heroku[nginx]: 74.192.103.146 - - [24/Mar/2012:05:12:50 +0000] "GET /price?next=480&user=featheralley HTTP/1.1" 200 13 "http://shopworth.heroku.com/?user=featheralley" "Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20100101 Firefox/11.0" shopworth.heroku.com 2012-03-24T05:12:51+00:00 app[web.1]: 74.192.103.146 - - [23/Mar/2012 22:12:51] "GET /price?next=560&user=featheralley HTTP/1.1" 200 13 0.7139 2012-03-24T05:12:51+00:00 heroku[router]: GET shopworth.heroku.com/price dyno=web.1 queue=0 wait=0ms service=723ms status=200 bytes=13 2012-03-24T05:12:51+00:00 heroku[nginx]: 74.192.103.146 - - [24/Mar/2012:05:12:51 +0000] "GET /price?next=560&user=featheralley HTTP/1.1" 200 13 "http://shopworth.heroku.com/?user=featheralley" "Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20100101 Firefox/11.0" shopworth.heroku.com 2012-03-24T05:12:52+00:00 app[web.1]: 74.192.103.146 - - [23/Mar/2012 22:12:52] "GET /price?next=640&user=featheralley HTTP/1.1" 200 15 0.6381 2012-03-24T05:12:52+00:00 heroku[nginx]: 74.192.103.146 - - [24/Mar/2012:05:12:52 +0000] "GET /price?next=640&user=featheralley HTTP/1.1" 200 15 "http://shopworth.heroku.com/?user=featheralley" "Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20100101 Firefox/11.0" shopworth.heroku.com
That's a short snippet of the logs from the shop worth calculator I posted a couple days ago. It has a timestamp, an IP address, the exact URL requested, the response code, the number of bytes returned by the request, the page from which the request came, and the visiting browser's user agent. Neopets likely uses Apache, but I'm sure the logs are very similar.
Posted 24 March 2012 - 06:07 PM
0 members, 1 guests, 0 anonymous users