Schinckel.net

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.

My Life • Dido • No Angel ★★★

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.

I’ve implemented Performancing Metrics on this blog. I used the following code:

        {capture name=cats}{the_category_rss}{/capture}
        <script type="text/javascript">
            z_post_title="{single_post_title}{single_cat_title}{single_month_title}";
            z_post_category="{$smarty.capture.cats|strip_tags|strip}";
        </script>
        <script id="stats_script" type="text/javascript" src="http://metrics.performancing.com/wp.js"></script>

Instead of the code given by the system.

Got this popup while browsing today (Firefox, you are getting sloppy!): Needles to say, I didn’t click on it!

Blogsome is great. You can blog, upload up to 25Mb of images, but unfortunately, you can’t upload your own JavaScripts and use them from the Blogsome server. Or can you? It is actually possible to host a JavaScript on your Blogsome blog, you just need to be a bit tricky. If you have a script called myscript.js, and you try to Upload it using the standard Upload menu item, it will fail. Blogsome only allows files with the extensions .jpg, .gif and .png. Note well that they do not need to be that type of file, but only have that extension. I think you know what I’m going to do next, and that’s rename my file to myscript.js.jpg: leaving in the .js reminds me that this is a JavaScript file, and the .jpg allows me to upload it. Which I did. When you include the script in your template, all you need to use is: <script type="text/javascript" src="/images/myscript.js.jpg"></script> Browsers are smart enough to allow this to happen.

rentzsch.com: I don’t understand Coffee Physics

Fresh hot coffee: yum. ** Day old coffee:** yuck. Cold coffee (day-old coffee that’s been stuck in the fridge): yum.

I’ve noticed this too: but even more so, if I brew some fresh coffee, it’s great. If I brew it, pour it over ice and put fresh cold milk in there, it’s great. If I put it in a thermos flask, and drink it two hours later, it’s still nice and hot, but no longer nice.