Technospeak

as you can see from the funky wide-screen image, everything starts to work . i’ve installed already the essential software and now i’ll go to bed, so i can then move all the data tomorrow…

since i’ve been mentioned in the berner zeitung two weeks ago i thought it’s time to take a look at the access-statistics of my site once again [1].

since i let google get some data about my visitors, i also have a fancy-schmanzy widget , that shows me at a quick glance if something remarkable is going on (click on the left image for bigger view). and i have to say that one could really see that quite some people came to my site in the days after the article came out [2]. one can see it much better on the following graph, when it’s not the naked numbers… on friday the 10. november the article came out and in the two following days i had around 2-3 times more people on my little website than normal (click right image for slightly bigger view). quite nice, innit?

first: dropdown-archives . they unclutter my sidebar without a single line of coding. it compacts the full archives into a nice dropdown-field. i feel like noone uses the archives, but still felt like letting them stay in the sidebar.

the second one is more for safari users (because it degrades nicely for other browsers ): the safari-search-field widget . it adds a search field to the blog that looks and behaves like the one safari-users have in their top-left corner (unless you installed inquisitor 3 ). if you use another browser it looks like a normal search field, as you can see below.

wordpress-plugins are really neat!

i probably stumbled over lightboxJS a hundred times before. today i thought it would be really nice to have that for this site here. thanks to wordpress-plugins, implementing it here only took 4 steps:

• google wordpress plugin lightboxJS
• download the plugin from here
• drop it into /wp-content/plugins
• activate the plugin in the control panel and now, if you click on an image, you get the nice lightboxJS-effect. try it for yourself, maybe in the post below! and if you read me only through my feed, this might be worth checking out the site…

for rouge , the site now has a favicon, thankts to the favicon manager for wordpress , and cocomments is now integrated thanks to the really cool plugin from david .

Technorati Tags: cocomment , favicon , plugins

in the last few weeks movable type stressed the server more and more. after reading a bit into it, i found out, that wordpress is much fancier and much less resource-hungry as a blog platform. and after trying out an install wordpress on habi.gna.ch, which really took less than five minutes , i was sold. now wordpress is powering habi.gna.ch and the blog is going to migrate to the root directory. everything else (pics , cv , my calendars and such) is still gonna stay where it is, and maybe be integrated into wordpress (which works quite well as a CMS) sometimes. i’m still tinkering with the way of redirectong the old movable type archives to the imported posts, but this still has time. if you’d like, you can change your feed addresses, but i will install a redirect-rule and leave everyting where it is. after some time, when google and co. picked up everything, i’m gonna delete or inactivate /blog…

thanks sigi for noticing (oh, and what happened to your content?)

update: the comments-script nearly took down existenz.gna.ch (again), so someone chmodded it to 000. i’m nearly ready to switch to wordpress , if this goes on, i don’t want to stress the server that much [1]. for the moment i implemented the tinyturing-test from staggernation . so all commenters must now enter a random letter into the field when they want to post a comment, as seen in the image on the right.

even renaming the relevant files did not help, so it had to take more drastic measures. [1]

i’ve installed a plugin for MT3.2 which tries adds a hidden input field and then obfuscates the code through some javascript trickery.

first, i used the direction posted here at the photoblogs-wiki and adapted them a bit:

after reading a lot of buzz about cocomment (explained a wee bit here :-) i thought it’s about time to jump the bandwagon.

and now, after adding a little bit of code to the individual entry archive this blog is now officially pimped -ehrm- cocomment enabled.

have no idea what i’m talking about? i only start to get the implication of cocomment, but let me explain it here, as far as i get it: up to now, whenever i commented on a blog/site somewhere, i had to remember to visit the site later on or add the comment feed to my feedreader to not loose that particular conversation string. cocomment should be able to overcome that, because it enables a lot of sites (even flickr !) to “send” the comments back to one central location. i’m now able to track those comments in a central location and follow conversations more, thus participating more (talk about positive feedback loop).