HaxoGreen 2016

HaxoGreen 2016 banner

HaxoGreen is just around the corner, taking place july 28th to july 31st. This years edition is already the fifth of this small but very cozy and nice hacker camp, and unfortunately there are no tickets left.

More info can be found on the Wiki, also there's @HaxoGreen and #haxogreen on Twitter as well as #haxogreen on IRC on Freenode. If you're an attendee and want to give a talk or hold a workshop there's still time! There are some slots just waiting for you. Contact Orga at hello[_at_]haxogreen.lu and go for it :)

OpenPGP Transition Statement

For a number of reasons, I've recently set up a new OpenPGP key, and will be transitioning away from my old one. Here's the transition statement, signed by both my old and my new key:

(Or download it here)

Hash: SHA1

Fri, 19 Feb 2016 21:43

I've recently created a new OpenPGP Key and will transition away from my old one.

The old key will continue to be valid for some time, but I prefer all future correspondence to come to the new one. This message is signed by both keys to certify the transition.

the old key was:

pub   4096R/95FC3745 2013-07-05 [expires: 2016-07-04]
      Key fingerprint = A705 94BE CF58 8F1D 2E26  DF1D 8EE8 3FC9 95FC 3745

The new key is:

pub   4096R/7A9C3BD7 2016-02-10 [expires: 2018-02-09]
      Key fingerprint = 2EEC EFE3 C2FC 5E65 FF11  8B88 6835 1706 7A9C 3BD7

To fetch the key from my web site and import it:

  wget -q -O- https://muling.lu/muling_gpg.asc | gpg --import -

Or fetch it from a public key server:

  gpg --recv-key 0x7A9C3BD7

If you already know my old key, you can now verify that the new key is
signed by the old one:

  gpg --check-sigs 0x7A9C3BD7

If you don't already know my old key, or you just want to be double
extra paranoid, you can check the fingerprint against the one above:

  gpg --fingerprint 7A9C3BD7

Please let me know if there is any trouble, and sorry for the inconvenience.

Version: GnuPG v1


Hello again, world!

8 years ago I've started blogging, not regularly or frequent or anything, but still.. Back then I opted for WordPress, it was fast to set up and I didn't know yet if I even liked blogging at all. Actually I only started because I had that server & domain anyway and wanted to throw something on the web server, not because I wanted to get into blogging...

I've wanted to switch to something static as well as start writing in English for years, but never got around to. So today is the day, yay! There are quite a few static blog engines out there to choose from, I took Pelican. Important for me were:

  • Static
  • Markdown or reStructuredText support
  • Content as flat files so I can write posts in vim
  • Git repo for content, theme and stuff
  • Easy templating - I don't like web design stuff (as you probably can see), so I want to do as little of that as possible
  • Optional dynamic commenting system
  • Atom or RSS feed

I may add some commenting system later though, unfortunately this means that the site won't be totally static anymore since it needs to store and read these comments somewhere. I don't want to use any third party system such as Disqus so there's no way around that, oh well.

Kay, technical stuff done. So this blog will be about nerdy things in general, a place where I can document projects I do and stuff like that. Definitely more technical oriented than my old German blog. The old WordPress based one is still online by the way, but I'll take it down (or export to something static) eventually.

Well then, hope I can fill this place with some life!