June 31st
Bill de hÓra: You’re seeing this error because you have DEBUG = True in your Django settings file. Change that to False, and Django will display a standard 404 page.
Update: seems to be better now. Will leave with this somewhat odd page.
It’s just data
Bill de hÓra: You’re seeing this error because you have DEBUG = True in your Django settings file. Change that to False, and Django will display a standard 404 page.
Update: seems to be better now. Will leave with this somewhat odd page.
Tim Bray: I’m not sure whether this free-TLD idea is a good or bad thing in the big picture
Consider the fun that will occur when existing software is presented with email addresses that contain non-latin characters.
While Ryan, James, and Mark have been pursing a minimalist design from a presentation perspective, I’ve been quietly pursuing a minimalist design from a markup perspective.
My front page (under development) will be valid HTML5 and yet have absolutely no div or span elements, no inline style or class attributes, and no table or img elements used purely for layout purposes.
Views: index, post, comments, archives
This clearly is just modest beginnings. A snapshot of existing data. Read-only views at this point. No caching.
Technology is Rails 2.0.2 on SQLite3 using Phusion Passenger on Dreamhost.
Nelson Minar starts a meme. Rafe Colburn waters it down. I’ve watered it down even further.
Whatever you call your feed, Safari will call it RSS. Don’t sweat the small stuff.
Which format should you pick? I’d suggest that you pick whichever one that you can consistently produce with the fewest errors and warnings detected by the feedvalidator. Test with Iñtërnâtiônàlizætiøn and ampersands in titles. June, particularly in the UK is also a good time to test.
Tim Bray: There is quite a bit of disgruntlement about XML and Ruby right at this point in time
I’m scheduled to give a talk about this subject and more at OSCON next month. Short summary: if you are a markup geek (i.e., deal with things like HTML or XML), and expect things to “just work”, now is not a great time to be exploring Ruby 1.9. The biggest issue is that bug reports and suggestions don’t seem to attract the necessary cycles from the key developers.
Hopefully, venues like OSCON can help draw attention to this important issue.