SyamilMJ said
madlep said
Bit of everything. Mostly back end work.Ruby, Erlang, Haskell, Javascript, Coffeescript, Bash.
All the misc stuff like CSS /HTML/SQL that goes with that as well.Knowing so many languages, can you give a tip or two on how you masters them all?
I’m slowly getting into Ruby + Rails. I think my biggest problem is to put my newly acquired knowledges into any practical real world example.
Best tip is to think what the goals and strengths of each language are. Find a small project to work on as a hobby that exercises those goals.
You learn the most from your second language. When you learn the first one, you rote learn lot of stuff, and not necessarily think too much about why things are done that way. When you learn another language, you think more about the differences.
You see a lot of similarities to things you’ve done before, and the syntax and details gets easier to understand, and it’s mostly about understanding the higher level concepts.
Other than that, find a good source for the standard library API docs for a language, keep it handy. The core language and syntax is easy learn, but understanding the libraries can be much harder as there is so much information to absorb.
Bit of everything. Mostly back end work.
Ruby, Erlang, Haskell, Javascript, Coffeescript, Bash.
All the misc stuff like CSS /HTML/SQL that goes with that as well.
Yup. There was a bug we introduced a couple of weeks ago that caused that.
Got fixed today (check out graphicriver.net thread for details)
revaxarts said
It’s an iframe which cause this bug:![]()
Yup. That looks familiar. There was a change deployed live today related to that. Will revert it and have it fixed up tomorrow. Some CSS fixing needs to be done I think.
That’s our bad sorry. Bug was introduced a couple of weeks back.
Is fixed now 
Details at this thread over in graphicriver.net
I just had a quick look at our server logs, and the website is responding pretty quickly for your requests – usually around 100ms, and nothing slower than 0.5s for the last week. So that looks OK at that end.
Like the other’s have suggested, I’d have a look at your DNS configuration.
It’s also possible that Javascript and/or stylesheets are not loading fast enough, even though the main site is. We host them on separate domains and using Amazon S3, and you might be getting some sort of slow down accessing them which causes the rest of the site load speed to be slower.
If you’re using Safari, turn on the “Develop” menu, and have a look at any slow requests (for more info here)
Note anything there that seems excessively slow (longer than ~1s), and post back here, that would help investigating what the problem is.
Fix is now live.
Have a look and let me know if anyone sees any problems still 
Hey guys.
Am working on a fix for this now. Should be live on the site later on today or tomorrow.
There was a bug introduced at the end of October that caused this. The problem is that the DB query to get the page count is joining items and purchases together – so it’s counting out the number required based on items X purchases, instead of just items.
Will post when it’s live.
RomacMedia said
I remember some months ago there were more members than items.
Photodune changed that. With other sites, authors tended to only upload a few items at a time as they are more complicated and specialised. Photos are different though, and Photodune authors often upload 1000+ items at a time – especially new authors with an existing large portfolio of work.
Is getting close. I’m interested in when it’s going to hit. I might pull up the data tomorrow and do some maths to get a closer estimate 
Some background about the member numbers you see at the page footer:
- the count includes ALL the members in the database table. This includes everything: all the banned accounts; all the blocked accounts; all the accounts that have signed up, but not verified; and of course, all the legit accounts
- the number is cached for 6 hours in between queries. So the count you see isn’t exactly real time sorry
. Although I might see if I can sneak in a change to bring that cache time down a bit to make it more real time for you guys 
