« first day (59 days earlier)      last day (4434 days later) » 

acl
12:30 AM
@Heike seems like there's a lot of us like that around...
 
 
4 hours later…
4:03 AM
@Heike it's up. Congrats on the first tag badge!
 
CHM
4:34 AM
Is anyone familiar with Android phones?
 
 
4 hours later…
8:28 AM
@rcollyer Thanks, @rcollyer
@CHM I'm familiar with one model.
 
9:21 AM
@yoda You were right, serial upvoting reversed.
Thank you for the support to that person who tried to undo the unupvotes yesterday :-) But rep is not that important, it's really not necessary. Better to let the SE system work the way it does.
I'm more worried about why someone (who must have been quite active based on the number of votes) deleted their account.
And I really wonder who it was.
There are several people who have stopped posting some time ago
 
 
2 hours later…
11:11 AM
Well, I'm back to using my old computer, which means a painful several times slowdown :-(
But the 15" screen is so much better than the 14" one :-)
 
 
3 hours later…
1:47 PM
@Szabolcs I have asked a question on Meta, hopefully not a duplicate. This is really very strange:
1
Q: Strange "unupvote" pattern across multiple users

Mr.WizardYesterday there was a large series of "unupvote" events all at 12:08:55Z that affected all of the "top users" on the mathematica tag. This also appears to have affected users in the matlab tag and probably others as well. These users were hit particularly hard: yoda Leonid Shifrin gnovice The...

 
2:23 PM
@MrWizard Thanks for asking that, I'm curious if there'll be any official reply!
 
2:40 PM
yesterday, by yoda
I lost 1.7k, and judging by the questions voted on, I think it was an old colleague of mine
1
A: Strange "unupvote" pattern across multiple users

Nick CraverA user was deleted and (as has always happened) the votes were removed. I have a major change in the pipe that will show all of these events as a single "user removed" and an accurate number for how much rep impact it had...but this won't go out until after out team call Monday afternoon.

 
3:15 PM
@yoda I have figured out that the user was d00b, and that all (or at least multiple) SE accounts were deleted. I am trying to find out why.
 
you can try pinging/emailing comm team, but not sure if they'll give out the info (you can try)
<insert "there is no try" joke>
 
Google cache still has it.
And yes, it's the same location as @yoda's.
 
 
1 hour later…
CHM
4:36 PM
@Heike I had no clue of what to do with my phone, never having used Android before yesterday. I have a new Optimus 2x, but it came with 2.2.2, which I knew was old. I've been able to flash CM9 (ICS) on it, it looks great, but I'm going back to CM7 nightlies, since it's apparently a lot more stable and has more functionality.
The updating process is a bit retarded IMHO. I can't see why LG (or any other manufacturer) couldn't just offer the build for download on their servers.
 
CHM
5:15 PM
Surpsingly, I've had three Launcher crashes with CM7, none with CM9, and I've used the latter for a longer time. Funny.
 
 
2 hours later…
7:31 PM
Arnoud's been pretty inactive — I'm tempted to think that it's because he's busy with the QA for mma v9 before release (hopefully soon?) =)
 
 
2 hours later…
9:01 PM
The second day of the pick-up in traffic is not showing on the main site, only on the stats on Area 51. But look:
 
What are you doing to get the visits/day? Is that available through the API or are you scraping that from the se/sites page?
 
I can't get into the JSON data for some reason
I'm scraping from the Area 51 page, which disagrees with the main site.
 
maybe scrape both and you can perhaps see what the relationship is and what the lag is?
 
I think they cache differently because usually the main site visits number tracks the Area 51 one. Or maybe they are medians calculated across several days.
This week will be hard - I am getting on a plane at 6am tomorrow.
two days in Europe and then back to Oz Friday morning.
Anyway I am getting this error with the JSON, suggesting I've been throttled
FetchURL::conopen: The connection to URL api.stackexchange.com/2.0/… cannot be opened. If the URL is correct, you might need to configure your firewall program, or you might need to set a proxy in the Internet connectivity tab of the Preferences dialog (or by calling SetInternetProxy). For HTTPS connections, you might need to inspect the authenticity of the server's SSL certificate and choose to accept it.
 
Does your traffic curve look similar to that for that time range?
 
9:06 PM
barely - visits != pageviews
 
oh shoot! I didn't realize Sjoerd had shared the pageviews instead of visits/day
 
Something's definitely happened in the last few days. First all those questions, then traffic came up.
 
@Verbeia that is a possibility. I've been throttled in the past. The API supports vectorized calls (don't know how to do yet), so you might be able to reduce your calls
The page loads for me
 
Aha: {"error_id":502,"error_name":"throttle_violation","error_message":"too many requests from this IP, more requests availabe in 18309 seconds"}
Five hours :-)
 
why don't you just register for an API key? That way you can make a bazillion calls/day
 
9:12 PM
I suppose I could. I don't know what's involved. I hadn't had problems before, but of course I was testing some refinements to my code :-)
Also pagesize=100 will help.
 
@Verbeia It happened to me several times and I got locked out for a while.
@Verbeia Which part of Europe are you going to?
 
@Szabolcs Switzerland
 
I've been there only once for a very short visit to CERN with a student group (when I was an undergrad)
 
9:43 PM
I go there a lot - a lot of the meetings are held there, in Basel
ooh - dupe question on both sites?
@yoda the traffic number on the full list of sites has updated to match A51 so I bet the number on the front page of the site will update soon.
 
10:44 PM
@Verbeia On A51 I see 866 now (!). It's bedtime for me (quarter to 1), so have a nice trip tomorrow! :-)
 
11:30 PM
@yoda how did you get that graph?
 
11:56 PM
@MrWizard oops, you must've forgotten to logout from your computer =)
 

« first day (59 days earlier)      last day (4434 days later) »