11–17 of 17 posts
The site is broken at my 1024 pixel screen width (netbook). About a quarter of the text exits stage left. It's easier to read the content via view-source. EDIT: The problem is your 1280px width declaration in style.css's rascalcontent class. Guessing this will screw up smart phones too.
EDIT: Thanks for the 1280px info.
The site is broken at my 1024 pixel screen width (netbook). About a quarter of the text exits stage left. It's easier to read the content via view-source. EDIT: The problem is your 1280px width declaration in style.css's rascalcontent class. Guessing this will screw up smart phones too.
That's curious-- in my browser, the picture gets cropped, but the text remains visible. What browser and OS are you using? EDIT: Thanks for the 1280px info.
Earlier quoted context omitted.
That's curious-- in my browser, the picture gets cropped, but the text remains visible. What browser and OS are you using? EDIT: Thanks for the 1280px info.
Chrome 12.0.742.124. Arch Linux. Screen cap: http://i.imgur.com/4vEl3.png
EDIT: OK, fixed, I think.
"If one turned on one's anger light in a fit of frustration, it was useful as a reminder later in the day to remain angry."
I'm all for finding healthy ways to express anger, but actively holding on to anger that would have naturally dissipated seems like a great way to transform yourself into a perpetually bitter person.
http://i.imgur.com/Eme3D.png http://i.stack.imgur.com/bID6D.png http://i.stack.imgur.com/ErM6T.png
(confirmed by myself and another user in the http://electronics.stackexchange.com chat room).
Started getting some corrupted images partway through, at roughly 1:00. Possible meltdown? http://i.imgur.com/Eme3D.png http://i.stack.imgur.com/bID6D.png http://i.stack.imgur.com/ErM6T.png (confirmed by myself and another user in the http://electronics.stackexchange.com chat room).
The traffic has dropped off substantially since earlier today. The Rascal served around 200,000 hits over the course of around 2 hours on the front page. I've been logged in remotely the whole time, so there can't have been any reboots, or my SSH session would have been terminated.
Judging by the process id's of the servers, I don't think any of them have been restarted.
The error log looks pretty clean. There's huge pile of errors from a misnamed font file, but that's minor. Other than that, there are just two errors that look like this:
readv() failed (104: Unknown error) while reading upstream, client:
80.176.154.87, server: localhost, request: "POST /toggleEerik HTTP/1.1",
upstream: "uwsgi://127.0.0.1:5000", host: "209.6.42.115:82"