Due to a minor injury less doing sports and more watching sports. The olympics, german football league starting…and what not. Along the way I worked off my last freelance jobs…so the coming weeks should be a lot less crowded…at least when it comes to working, unless I get the new job I’m applying for, then the “workless” times could be over quite quickly ;)
Football preparation for the new season has started two weeks ago and so far I didn’t miss a single training session – so far. Today I missed the first one, a friendly match, as my foot is shining in different colours ranging from green to blue. It wasn’t the best idea to train on friday after suffering the injury on thursday, but oh well. Nontheless a lot of sport going on.
First of all, the Beijing Olympics…so far nothing much going for the german athletes when it comes to winnnig medals, but at least some of the national teams seem to be in good shape (e.g. handball, basketball)…it’ll be fun to watch them compete for the next few days/weeks.
Secondly, the german professional football season is about to start next weekend, so in good old tradition the competition for the german football cup ( “DFB Pokal” ) started this week…so far quite a few good matches and no major upsets…
Alrighty…enough about sports, I’m going to do a little sport myself now…called “couch-surfing” ;)
After a weekend from hell, we’re finally back. On friday evening I received a disturbing text message from my hoster, my server has been disabled due to outgoing DoS attacks. After that one I decided it was time to move on and do a server reinstall as the server has been exploited before, so it was a good time to switch to a new Operating System. So I did that all of saturday and all seemed well, although some stuff was lost (backup-scripts not fetching subdomains, etc)…but the main problem remained a dns issue that kept my sites from being accessible. Today I finally got a hold of a server guru at my hoster and he found out what was wrong quickly. D’oh. The install of plesk had a wrong standard setting, it blocked ingoing DNS-request, nice firewall config…NOT…D’oh. So now everything is back up and running again…minus a few sites which databases needs to be recovered…I’m doing just that now…wheeeeeeee….le’s hope all goes well…I certainly hope so….
Well, the opportunity was just too good not to order it…how does 70% rebate sound…good, right. Once it arrives I’ll have another update and maybe even a review…wheeeeeeeee…..
…I get no support at all for an original product, genuine baby, that I bought from this company. What do I get instead? “Support” from a russian call-center basically telling me “click here, click there, oops doesn’t work, good day sir”. Wtf is going on here? Is there no qualified staff anymore where cases like mine could be escalated to? Wtf is going on…I’m so mad right now, you wouldn’t even believe it.
Note to self and anyone else out there pondering a Vista install for one reason or another: If you’ve got the “old version” (without SP1), make sure you use this version in the install process and install SP1 after the install. Why? Because Vista+SP1 is not Vista and then SP1…sorry…can’t activate your install…thank you very much M$…that’s what you get for buying your software instead of stealing it…thank you very much….
Edit #1: It seems that even the gurus at Technet can’t help…so I guess I’m in for a reinstall, yet again…
Edit #2: Still waiting for my new external hard-disc to show up…grrr….I hate delays….
Edit #3: Almost there, system up and running again…with official activation and the whole she-bang…still need to install some updates and then I’m good to go again…wheeeeeeeeee.
From now on tweets coming via my WordPress Plugin will show it…nice :-)
Twitter forgot to put the final “e” on it (for updater), but hey…I’ll take it for now and get in touch with support later….
Today was one of these days. Sit down at computer, do some small stuff…get the feeling that it’s totally sluggish. Hmmm, it’s windows after all and has been running for two weeks straight now…oh well, let’s reboot. Poof. Bad idea. System doesn’t come up again and throws the black screen of death. This or that driver is missing or damage.
Okay, let’s do a repair. Repair done – same problem.
Okay let’s do a restore to system restore point “yesterday” – not working.
Okay let’s do a restore to system restore point “two days ago” – not working.
…
Okay…all system restore points aren’t working. Groovy. Why did the system do them again? Sigh.
Okay, let’s do a repair install. Errm yeah, (upgrade aka repair) only possible when started from within the “old” install. Errm yeah, genius…I need the repair out of pure desperation…not because my system isn’t coming up you dumb***…sigh.
Oh well…burned up the whole afternoon and evening and now I’ve gotta do a clean install anyway…bad beat right there…
So it’s time to upgrade again…the upgrade was quick and painless like we’re used to…nice job WordPress. So, if you’re running wordpress, get it…
—
UPDATE: Please head on over to the new home of my plugin: TWITTERUPDATER.COM this post here will not be updated any longer!!!
—
So, I found this cool plugin posting updates to twitter once you wrote a new blog post (or edited an old one). It’s pretty nice and can be found on the authors, Victoria Chan, site here (v1.1).
Jonathan Dingman then released an update adding tinyurl support (v2.0) which can be found here.
I just edited this v2.0 and replaced the tinyurl-support with support for the new url-shortening service ZZ.GD which results in even shorter short-urls saving more space in the tweet in case a post title is longer…
My new version (v2.07.1) can be found here (please read edits below for more information!!!): Twitter Updater v2.07.1
Known Issues:
Feature requests:
Installation:
1. Download the plugin (see above link.)
2. Unzip the compressed file to your hard drive.
3. Upload the “twitter_updater†folder to your wp-content/plugins folder.
4. Browse to the Plugins page under wp-admin and activate the plugin.
5. Setting the options: Browse to Manage->Twitter Updater.
6. On this page, you can set any options you would like to.
7. IMPORTANT: Make sure you enter your Twitter username and password, then click on “save login”Â
8. That’s it! Now your Twitter.com status will be updated every time you publish a new post.
Edit (July 15th 2008): Just a quick note…the recent release of WP 2.6 has messed something up. While the plugin continues to work fine in WP version 2.5.1 and older, it keeps firing two updates (one with an invalid zz.gd-short-url) in WP 2.6. I’m going to investigate…stand by for news…and hopefully a quick fix.
Edit #2 (July 15th 2008): I’ve identified the culprit…WP2.6 uses post-revisions (saving multiple instances of the post using autosave)…hence the multi-tweet…working on a fix now…
Edit #3 (July 15th 2008): It’s indeed the post-revisions thing, but the quick workaround I tried (disabling post revisions after all) has had some major side-effects (namely edits of posts were not saved anymore)…so I really need to address this issue by checking the post status and ignoring revisions…fix probably coming tomorrow…for the time being please just manually delete the first auto-tweet.
Edit #4 (July 17th 2008): Sorry about the delay, but my computer fried itself today, so I had no time to fix it yet…exciting news forthcoming…as hopefully the fix…stay tuned.
Edit #5 (July 17th 2008): This little plugin has it’s own twitter source parameter now…so it’ll say “from Ingoal’s Twitter Update” instead of “from web” from now on…you can grab the latest version, version 2.02 above…version 2.03 with the bugfix (double-tweet) is still forthcoming…
Edit #6 (July 22nd 2008): Sorry about the delay…but I had something else going on, so it took me a while to write the fix. I deleted some of the options, from now on out you’ll have the update choice to auto-twitter when posting a new post (with or without link using zz.gd) and auto-twittering when editing old posts…that’s it. Compatible to WordPress version 2.6! So if you’re running WP 2.6, please update to version 2.03!!! …and if you’re running WP 2.5.1 or older, please continue to use version 2.02!!! Hat tip to microkid for his hint about identifying WordPress post revisions and auto-saves!!!
Edit #7 (July 27th 2008): Fixed the post-title issue. In the prior version post titles were truncated if they included an ampersand ( & )…this is fixed now…please update.
Edit #8 (July 29th 2008): Introduced alternative method to retrieve the shorturl from zz.gd (using curl)…please update if you had problems (error message, empty shorturl) and make sure you have a look at the twitter updater page (manage) -> check the new checkbox! If you didn’t have problems you don’t need to do anything…
Edit #9 (August 04th 2008): Introduced a cascading in the shorturl generation. After zz.gd was down the last two days due to server issues, ppl using the plugin were stuck with empty shorturls. To rectify that situation and keep it from happening in the future the cascade of zz.gd — tinyurl.com was introduced. If zz.gd is down, the shorturl will be generated using tinyurl.com. Other cascades might be added in the future, but for now, this one seems to be more than enough.
Edit #10 (October 18th 2008): So…Marco “Saphod” Luthe put up a modded version of the 2.06 version that fixes the future post (and save post) issues. I took the liberty to rename his modded version 2.06 to version 2.07 and I’m officially releasing it here. Thanks again Marco! All you users and readers out there feel free to drop by his site to thank him for the fix…and happy tweeting/twittering….
Edit #11 (November 1st 2008):Corrected tinyurl api url, so that if you’re using tinyurl instead of zz.gd you’re getting the correct short-url…
Oh what joy it brings to see script-kiddy after script-kiddy try their luck. Oh the pain when one of those kiddies is actually successful. Grrrr….time to do some upgrades, again, let’s see how it goes….see you on the other side….
Today was the day that Firefox 3 was finally released.
My first impressions are:
1. Compared to the old version Firefox seems to have an improved memory handling (or bluntly put: less memory leaks)…with the same tabs open and everything 85MB looks much better than 214MB….
2. The “Awesome Bar” is a nice feature….
3. Speed-wise I can’t see much different…
More impression after a longer time running it on a day to day basis…
…not that I had an old-one, lol, but as I got myself a new digital camera today, I thought I’d start a photoblog as part of ingoal.info. It can be found here. Let’s see how long I can keep it uptodate with photos…my plan is to post a photo every day, let’s see how that works out. If you would like to follow my photoblog, check in regularly or subscribe using your favourite feedreader…
Wow, the new 3G iPhone will be 199$ (8GB) and 299$ (16GB)…although I whole-heartedly love my (first generation) iPhone…I’ll get a new one soon :-)
Too good a price to pass up this opportunity…
I just wanted to give a big shoutout to the makers of SuperAntiSpyware as their software did a really great job on cleaning my system. It all started a few days back when some nasty spyware infected my system. No big deal I thought, so I fired up all the usual tools (e.g. Adaware, Spybot S&D, HijackThis)…to no avail…not even a safe-mode reboot and cleaning-procedure could get rid of it.
Bring in SuperAntiSpyware – Free Edition. Installed it, auto-downloaded the newest updates and definition files, ran it once, rebooted once and my system is clean. Awesome.
So once again, this is not a paid review, it’s just a message from me saying: Great software and if you’ve got problems with a spyware-infected system, give it a try!
…well, kind of, I would say I know how it feels like being scalped on local anaesthesia. Got a lipoma removed from my forehead this morning. I’m usually a pretty tough person and the local anaesthesia really helped a lot, once it wore off though, it started to hurt pretty good. The funny thing is that you normally don’t even realize how much your forehead is used in expressing stuff, as it’s really automatic. So it automatically hurt a lot during the day…thank god for (light) painkillers…
The compression bandage will come off tomorrow during the usual after-OP checkup…let’s see how it looks with a normal bandage on tomorrow…