mike arthur dot co dot you kay

the internet is leaking

KDE - Blog from KOrganizer HOWTO

Blog from KOrganizer? What kind of madness is this? Apparently some crazy (but yet incredibly good looking) fool decided to give you the ability to post journals from KOrganizer to your blog. Let’s learn how to do it!

Firstly open KOrganizer.

Blog from KOrganizer HOWTO 1

When it has opened right-click anywhere in the “Calendars” area in the bottom-left (marked with the red ellipse) and select “Add…” from the drop-down menu that appears.

Blog from KOrganizer HOWTO 2

Select “Journal in a blog” (marked with a red ellipse) from the “Resource Configuration” dialog.

Blog from KOrganizer HOWTO 3

Fill in the “Resource Configuration” dialog.

  • Name: Choose a descriptive name for your resource, this is how KOrganizer will describe it to you in future. KOrganizer won’t reference this resource as being a blog again so you may want to choose something suffixed with “blog“.
  • XML-RPC URL: This depends on your blog but for Wordpress and Drupal this is the main URL followed by “/xmlrpc.php“, for Livejournal it is “http://www.livejournal.com/interface/blogger” and for Blogger it is “http://www.blogger.com/feeds/$YOUR_USER_ID/blogs“. For other blogs, consult their documentation or ask me for help and I’ll do my best to work it out.
  • Username: This is the username you use to login and make blog posts.
    Password: This is the password you use to login with the above username and make blog posts.
  • API: Use “(Wordpress, Drupal <5.6 workarounds)” if you use either of those blogs. Otherwise it is MovableType for Drupal, Google Blogger Data for Blogger and Blogger for LiveJournal. The LiveJournal API is unlikely to work with LiveJournal as it isn’t yet complete. If you wish to implement the LiveJournal full API rather than using legacy Blogger one then please contact me.
  • Blog: When you have chosen an API this list will be automatically populated using items from the server. If there is only one entry, it will be greyed out but the entry’s text shown and selected. If there are more than one (e.g. Drupal has one for pages and one for posts) they will be selectable. If there is nothing new displayed then one or more of your XML-RPC/username/password/API are probably incorrect.
  • Posts to download: This chooses how many posts the API will download and sync. If you, like me, have made hundreds of posts then you probably want to keep this number reasonably low.
  • Automatic Reload: This defines how often KOrganizer will download new blog posts from the server without notification.
  • Automatic Save: This defines when KOrganizer will upload new blog posts to the server without notification. You probably don’t want to have this set to “On every change” unless you want it to be uploaded as soon as you hit “Save” in the next view.

Blog from KOrganizer HOWTO 4

You should now see your new blog resource displayed in the bottom-left corner (marked with the red ellipse). Let’s try making a new blog post. Activate the journal view by clicking the journal button (marked with the green ellipse).

Blog from KOrganizer HOWTO 5

We are now in the journal view and you can see on the left-hand pane that KOrganizer has successfully downloaded some of my blog posts. If we want to create a new one then click on the add journal button (marked with the red ellipse).

Blog from KOrganizer HOWTO 6

Fill in the “Edit Journal Entry” dialog.

  • Title: You probably want to change the title of the blog post from the default.
  • Date/Time: On most blogs selecting the date/time to somewhere in the future means the blog won’t publicly appear until then.
  • Content: Write something about how I am awesome, like the pictured example.The rich-text should be displayed on your blog correctly (albeit with slightly nasty HTML).

Blog from KOrganizer HOWTO 7

  • Select Categories: This list should have been populated with the ones from your blog and from the KOrganizer defaults. Sadly, I can’t seem to remove the latter and selecting them will do nothing unless they have been created on your blog.

Blog from KOrganizer HOWTO 8

When you click “OK” you may be prompted which resource you wish to save to. Select the resource we just created (marked with the red ellipse).

Blog from KOrganizer HOWTO 9

If you chose “on every change” for “Automatic Save” in the “Resource Configuration” dialog then your post has probably whizzed its way off to your blog already. If not, you can manually save it by right-clicking on your resource (marked with the red ellipse) and selecting “Save” from the drop-down menu that appears.

Blog from KOrganizer HOWTO 10

I hope this was and is useful to some people. If you find any bugs, have any problems or want any other features then please let me know either by email, my posting on this blog or by filing a bug in the KDE bugtracker.

Posted in Software Development

12 Comments »

WP-reCAPTCHA failure…

So apparently the WP-reCAPTCHA plugin sucks is a little too good and seems to stop anyone from posting comments on my blog. I was going to link to their page but it seems it’s 404′ing which strikes me as somewhat ironic…

If anyone else has a good plugin for Wordpress for avoiding spam then please let me know as being on the Planet seems to result in me being spammed to oblivion.

Also, if you had anything interesting to say about Spore, Phorm or Chrome then please excuse me being a noob and post comments!

Posted in Software Development, Uncategorized

8 Comments »

I love my TS-109 II

QNAP TS-109
I used to run the server powering this site from my home internet connection but when I moved to getting the worst ISP of all time free with my job then this rapidly ran out of favour. The connection was slow, the router liked spontaneously rebooting and the Pentium 3 running it was using a lot of power and struggling somewhat with still being kept alive.

Eventually I got a shiny KVM virtual machine (which reboots and only takes the web server down for three seconds!) supplied by a friend which is treating me well.

The only problem now was I wanted a something that I could keep as an always-on fileserver for backups and various things I wanted an always-on system for. After a bit of hunting I found the QNAP TurboStation 109 II which has a 500Mhz ARM chip, 256MB of RAM, a speedy gigabit ethernet port, SATA and eSATA, USB ports, runs Linux and uses 14.4W on load and 6W idle.

By default it runs some crazy QNAP distribution but there is a (rock solid in my use) beta of Debian available for it, which has been done by one of the former Debian project leaders and is all-in-all a pretty nice experience. I have it now doing my regular incremental backups using rdiff-backup and running a few other miscellaneous servers, including CUPS for my printer which works amazingly.

I’ve had absolutely no problems with either the hardware or running Debian on it and I really recommend it to anyone looking for a (relatively) low-cost, low-power and low-hassle system to run as a small file-server.

Posted in Software Development

No Comments »

Bad Phorm

No Phorm
So apparently the UK government doesn’t care about a private company wiretapping its citizens and giving them to another company (for money) as long as when they roll it out to everyone they are sure to ask for permission first (i.e. most probably at the end of a huge EULA).

I can’t say I’m surprised but I am pretty disappointed. When it first emerged on The Register that Phorm had been monitoring the internet communications of BT customers I was a BT employee. When it came out that BT outright lied on to those tech-savvy customers who raised the issue my opinions of my employer had sadly dropped to an all-time low.

I’m not someone who believes in publicly criticising the company I am currently working for (partly because the company I work for currently is awesome) and didn’t want to straight after I left at the risk of seeming bitter or unprofessional but I feel it needs to be publicly stated that I did not at any time agree with the actions that were being taken by my current employer and everything negative I found out second-hand and eventually was part of the reason I left.

I’m not sure what the management of BT that thought that Phorm was a good idea were up to at the time but I feel they may need a little reminding that massively alienating a huge portion of your technical user-base is probably not the best way to run an ISP, considering how much influence we have on our non-geeky friends’ technology choices.

As for their “anonymous” technology, if I’m “anonymous” enough for you to be able to track me across multiple IPs then I’m not “anonymous”!

Posted in My Life, Politics, Software Development

1 Comment »

Next Page »
Valid XHTML 1.0 Strict Valid CSS 3