A programmer once built a vast database containing all the literature,
facts, figures, and data in the world.
Then he built an advanced querying system that linked that knowledge together, allowing him to wander through the database at will.
Satisfied and pleased, he sat down before his computer to enjoy the fruits of his labor.
After three minutes, the programmer had a headache.
After three hours, the programmer felt ill.
After three days, the programmer destroyed his database.
When asked why, he replied:
'That system put the world at my fingertips. I could go anywhere, see anything.
Because I was no longer limited by external conditions,
I had no excuse for not knowing everything there is to know.
I could neither sleep nor eat. All I could do was wander through the database.
Now I can rest.'
-- Geoffrey James, The Zen of Programming.
Like many other people, I have more than one email account.
A lot of accounts are setup to forward mail to my main email address, but I still have seperate accounts for my private and my work email.
The email comes to my notebook using offlineimap, and is indexed with notmuch for easy searching. (I should probably create pages documenting my setup so you can all enjoy this wonderful setup)
One thing that always bothered me is that searching returns matching emails from all accounts.
Most of the time I am only interested in emails in the account I'm currently working in.
But as of yesterday Honza was so kind to accept my pull-request against his mutt-notmuch-py repository and now one can limit the search results to a specific path!
Go HERE to get the latest version with this support.
At work the whole email setup is put in gmail, like almost all startups do.
When you can get your head around the horrible webinterface, it can be ok for you to use. But if you are like me and prefer a real email client gmail can have a lot of problems.
Some things I found out the hard way yesterday while debugging why my offlineimap+mutt setup stopped working correctly:
- Gmail has some special folders like [Gmail]/Sent, [Gmail]/All Mail etc
Those folders get renamed when you switch your output language on https://www.google.com !!! basically rendering your settings of your email client non-working!
- New mail gets delivered in both INBOX and [Gmail]/All Mail.
This handling is confusing, as they are the same mails sometimes, and different mails sometimes:
- When marking a mail Read in INBOX, the mail does NOT get marked Read in [Gmail]/All Mail
- When removing a mail from INBOX, the mail does NOT get deleted from [Gmail]/All Mail
- When moving a mail from INBOX to [Gmail]/Trash the mail DOES get deleted from [Gmail]/All Mail
- When moving a mail from INBOX to [Gmail]/All Mail you end up with double items, BUT ONLY for a couple of minutes.
Gmail has some algorithm to remove double mails from the [Gmail]/All Mail folder.
This algorithm does not only work on mails that are 100% the same. Sometimes it thinks two different but very much alike mails are the same and it ends up deleting wrong mail.
- Sending mail through their SMTP services creates double mails in [Gmail]/Sent if your mailclient does the same.
Since almost all mail clients do this, using something else than the official Google mail clients will create double items in your Sent box
All the above items are hardly documented, and for me make totally no sense at all.
Unfortunately I'm stuck with gmail for my work email, and had to fiddle with my configs a couple of times simply because Gmail showed some undocumented and unexpected behaviour.
My advice: stay away from gmail as far as possible!
This site, and many more things have been hosted on a bunch of VPSes hosted by digital ocean.
We have always been very happy with their services, but it is time to move on.
All things hosted on digital ocean have now been moved to a new FreeBSD machine hosted on a 100mbit fiber connection.
Yes, our home connection.
Backups have been configured to go to the synology NAS (one thing that has always been missing on the VPSes)
If you want to script AWS cloudfront actions you will notice this is not working.
For some reason, AWS still thinks this part of their API is in preview mode.
To get it to work add the following to your ~/.aws/config file:
cloudfront = true
There are a lot of pages on the internet about how to use hipchat with bitlbee.
Because of this I'm not going to explain that. Do your google foo and find out.
There is one really annoying thing: people tend to fill up your buffers with join/part messages.
Now there are some pages out there that tell you how to fix it with irssi but did not find a weechat tip.
So see here, this is how I did it.
In my case, I added the bitlbee server with
/server add bitlbee my.bitlbee.server'
Now, to get rid of the join/part messages type:
/filter add joinquitbitlbee irc.bitlbee.* irc_join,irc_part,irc_quit *
And no more annoying join/part/quit messages that are very common with all the IM services out there.
"One cannot become a true UNIX geek without growing one at least once. Like a monolithic kernel, a UNIX geek’s beard is a commanding obelisk of knowledge, wisdom, and hubris. It is a focal point, a symbol of arcane power."