Thu 16th Mar 2006
I’ve made some changes on my blog template so Trackbacks are handled a little bit nicer: specifically, Trackbacks/Pingbacks now also get the “owner” class. I’ve also turned off Gravatars for Trackbacks/Pingbacks, since they don’t make that much sense. I’d like to use a favicon or something in their place, but I’m not yet sure how to do this.
At this stage, I’ve left in code so that the Gravatar for the Author Email will appear for owner trackbacks/pingbacks.
(more…)
Thu 16th Mar 2006
I had a couple of interesting comments today, and when I viewed them in the list view, I noticed there was a comment awaiting moderation with the same format:
But obviously a whole lot more links.
If you look at the times, the one with heaps of links was posted first, and then it looks like the poster realised it wasn’t working, and posted comments without heaps of links, which made it into the comments stream.
Needless to say, 1insurancereview has made it into my blacklist. And the word insurance is very close to making my moderate list.
These are real comments, not trackbacks. I am finding a few Comment Spams now, I wonder if my JavaScript isn’t working?
How true:
Actually, the main reason I’m posting this is to comment on the Washington Post’s method of preventing you stealing the images displayed in comments. It’s actually quite clever. It checks the refererring page (where the <img src=“”> code is), and allows or rejects the request according to this.
Of course, the easy way to get around it: take a screenshot.
The harder way: find the image file in your cache. Search your computer for all files modified in the last 5 minutes just after loading the web page for the first time. You’ll need some kind of tool to examine the data in files, and be able to rename files to add the right extension.
Wouldn’t It Be Nice • Jeffrey Osborne • Wouldn’t It Be Nice ★★
Change icon color with CSS - CSS Insider
This is actually a very cool idea: it allows for very simple replacement of image background colours. The images are actually transparent background, with white detail, and you just place them over a div-tag with the right background/shape, and away you go.
You can then very easily change the colour/shape, all with CSS, allowing for site-wide design changes very simply.
Plus, they are smaller than using images with colours, and you only need to have one version but can have different colours, without a server hit for changes in colour.
For some reason, the character I use as a spacer, ☆, doesn’t seem to want to display in Safari. It works fine in FireFox, Opera, and possibly IE, but not in Safari:
This surprises me, since this is one browser I would have thought it would work in.
As it turns out, Safari may actually be doing the right thing here. To include Unicode characters in the CSS :before pseudoselector, you must escape them.
Instead of using:
#topnav li:before {content:"☆ ";}
I’ve used:
#topnav li:before {content:"\2729 ";}
Thanks to a great post over on mezzoblue.
