Atom 1.0 photo feed

I fig­ured I’d go with Atom when cre­at­ing an app to extract photo feeds for the gallery here, because it’s touted as the next best thing since sliced bread. It’s not. Maybe that’s just coz I’m over­tired and have spent too long star­ing at Feed Val­ida­tor, but prob­a­bly not. What the hell is with a lim­i­ta­tion on the num­ber of times you can have the same value on an update date? Maybe I posted mul­ti­ple things at once! Or had sched­uled posts. What­ever. Either way, a limit of two on this is ridicu­lous and… seem­ingly com­pletely superfluous.

As is the require­ment to have a <con­tent> ele­ment in the feed. For this gallery feed, that really isn’t nec­ces­sary. I con­ceded that point, but am now regret­ting it: this means I am now bound to intro­duce a fea­ture I really don’t want in the future! Note to self: next time a val­ida­tor comes along, abscond. (Mmm… scones…)

On the record, right now: I know the feed is invalid, and I don’t give a crap. I haven’t even tested it in a feed reader yet: my eyes are doing all the pars­ing right now. You can check it out at http://www.joahua.com/photostack/atomiccat.php — thus named because of Atom and cat-scan. More bugs presently exist than I care to name, or even think about, but my neck feels like I’ve been sit­ting at this com­puter for about a day (it’s been a few hours…), and I really need sleep. Will resolve later, in the mean­time… add that feed (application/atom+xml) to your feed reader at your own risk. It’s highly likely to break stuff.

I’ll also setup mod_rewrite rules some­time so it looks like a real feed. Sometime…

# by Josh on October 20th, 2005 Tags:
| 8 Comments »

Databases go outside your home directory.

Some­one remind me next time I say I’m going to do some­thing stu­pid like rein­stall an oper­at­ing sys­tem too quickly, that data­bases aren’t stored in my home direc­tory. Far out. I’ve just cre­ated hours of work for myself try­ing to piece together what used to be in var­i­ous MySQL data­bases on this com­puter. Yeah, I know, I should backup, but see­ing as I never make major changes (it’s all just incre­men­tal lit­tle stuff for sites still in the devel­op­ment phase) and really don’t under­stand how things are meant to be backed up with MySQL (do you export queries, or do you copy the folder, huh? HUH!??) I don’t any­where near as often as I should.

For me, the data­bases are gen­er­ally ancil­lary things that are merely there to fill in spaces in CSS-based designs, so I always backup design aspects, but rarely the data­base itself, because there’s no orig­i­nal con­tent there. Well, yeah, but there’s vitally impor­tant struc­ture that’s just been thrown away. Doh!

Oh well, noth­ing I can (read: should) do about it now, maybe between tomor­row after­noon and Thurs­day. Think of it as post-humous ITF study. Because that’s all it’s going to get.

# by Josh on October 16th, 2005 Tags:
| 8 Comments »

18:53 remaining

Note to self, PHP’s mktime() func­tion breaks when you use lead­ing zeros. Thank­fully, that means I’ve got 18 hours left to cram, and not nine. Bizarre.

p.s. Now’s a good time for the RSS peo­ple to come out from the trees and look at the now fixed hh:mm count­down on my site.
p.p.s. The first post-script will be irrel­e­vant this time tomor­row.
p.p.p.s. Track­back spam­mers, have a heart. I haven’t got time to deal with your crap right now, and really won’t feel like it tomor­row after­noon. Just go away for a while, okay? Thanks.

# by Josh on October 16th, 2005 Tags:
| 2 Comments »

CurlyEnc 0.1

This is a sim­ple Word­Press plu­gin that allows you to copy and paste from word-processing soft­ware that automag­i­cally does smart quotes con­ver­sion (curly quotes). You can do this with­out using this plu­gin — but the char­ac­ters aren’t proper HTML enti­ties and it’s dirty. CurlyEnc con­verts curly quote char­ac­ters to their proper HTML entity codes — some­thing Word­Press does per­fectly fine with nor­mal quo­ta­tion marks, but not with these ones.

Sim­ply upload CurlyEnc into your plugins direc­tory and enable it from the Plu­g­ins sec­tion of your Word­Press admin­is­tra­tion panel, and it should* work.

* No guar­an­tees, no promises. If your weblog sprouts furry ears and starts chas­ing your mouse, so to speak, I accept no respon­si­bil­ity. Yada yada. Happy to try and help. More seri­ously, I don’t know that much about char­ac­ter encod­ing, so I wouldn’t be entirely sur­prised if my mag­i­cal char­ac­ter is some­thing of a dud on some instal­la­tions. I know it’s a good con­cept, and this is my best imple­men­ta­tion of it — if any­one else has a bet­ter idea as to how it should be done, please share!

On a related note, it’s released under the GNU GPL — you can have that five lines of code for free! Sorry, no steak knives.

View the PHP source, or down­load a plain text ver­sion.

DashLite 1.1 — The “I-don’t-read-long-posts” edition

I announced this at the bot­tom of the post A response to Dash­Lite crit­i­cism, but fig­ured not many peo­ple would actu­ally read that far… so I’m announc­ing it separately.

Essen­tially, ver­sion 1.1 re-introduces one only very spe­cific feed, which pulls the “Releases” cat­e­gory from the Word­Press devel­op­ment blog. This cat­e­gory is only used for post­ing updates to soft­ware — there is no announce­ment of com­mu­nity events, mile­stones, etc. To view exactly what’s being syn­di­cated, visit the Releases cat­e­gory page.

Basi­cally, this syn­di­cates new release infor­ma­tion and dis­plays it in the “Do Stuff” side­bar, as shown in the screenshot.

Get it

PHP source file, rich for­mat­ting (HTML)
Plain text ver­sion of the same, save this as-is

To install the update, sim­ply over­write the wp-admin/index.php file in your Word­Press instal­la­tion — it is advis­able you backup your old index.php file first, in case prob­lems arise (none noted in the changes made, but it’s pos­si­ble you’ll dis­cover some­thing, as always).

# by Josh on April 8th, 2005 Tags: , ,
| 3 Comments »

A response to DashLite criticism

Navid Azimi posted the fol­low­ing in a com­ment on the ini­tial Dash­lite announce­ment post:

This seems like a good imple­men­ta­tion and def­i­nitely has it’s uses but for most admin­is­tra­tors this could actu­ally be more detri­men­tal in the long run than ini­tially expected. The pri­mary idea behind the Dash­board was to allow all Word­Press Admin­is­tra­tors to stay informed regard­ing devel­op­ments in the community.

Many WP users (or any com­mu­nity for that mat­ter) install and sit. Often times being obliv­i­ous to new ver­sions and (most impor­tantly) secu­rity updates. This sort of unpatched soft­ware can be detri­men­tal not only to your web­host, and your web­site, but also to the entire web com­mu­nity itself.

For exam­ple, when phpBB was exploited with a major secu­rity flaw — there was a major defi­ciency in con­tact­ing all admin­is­tra­tors regard­ing the secu­rity hole. The prob­lem is twofold. The more you pro­mote the secu­rity hole, the eas­ier it becomes for mali­cious users to exploit unpatched instal­la­tions. You see where I am going here.

Of course — right now — in the prime heat of your blog you feel that you are check­ing wordpress.org every­day and you’re prob­a­bly skim­ming the forums daily too. There is no way you’ll miss any updates. But as time goes on and you have tweaked, retweaked and redesigned your web­site five times you’ll real­ize that its time for your blog to push bet­ter con­tent and not just look pret­tier. And its then when you sim­ply stop keep­ing up with every nightly or read­ing the forums daily.

Then again, I could be com­pletely wrong.

I kind of felt that this required a response more pub­licly than the con­tin­u­a­tion of the com­ment thread would per­mit, hence this post­ing. Read the rest of this entry »

Graveyard retired

Some more atten­tive reg­u­lars (who don’t just peruse this web­site by means of syn­di­ca­tion) may have noticed the dis­ap­pear­ance of a link in the top bar in the last sev­eral hours. This is because I’ve finally got all the old con­tent into Word­Press, with no small amount of assis­tance from Michael, under a cat­e­gory called “Before Word­Press” (this post is cat­e­gorised sim­i­larly, and shall likely be the last ever entry into that category).

Prac­ti­cally, this means that that con­tent is using seman­ti­cally bet­ter markup, has bet­ter meta infor­ma­tion for search engines, and is inter­nally search­able, using the Word­Press search func­tion (it wasn’t before).

For most reg­u­lars, this prob­a­bly doesn’t mean much, but the old arti­cles attract the most search engine traf­fic, so this’ll be of ben­e­fit to peo­ple find­ing rel­e­vant con­tent, at least, because the old script could be some­what retarded in the way it was indexed, as there was no for­mal perma­link struc­ture, just a bunch of loose query strings, which search engines didn’t like.

</geek off>