Iâ€™ve been working for quite some time now with Subversion but recently fell in love with Mercurial. Mercurial (like GIT or Bazaar) is a distributed version control system (DVCS). Coming from Subversion, itâ€™s sometimes necessary to convert an existing Subversion repository to Mercurial. And thatâ€™s what this post is about.
There’s spam on the Internet, alright. Lots of it. You receive spam when spammers get hold of your email address. How do they do this?
- A friend of yours got himself infected with a virus/worm/trojan horse. This virus reads your friend’s address book and sends all email addresses in it to a spam server.
- Spammers try to guess common email addresses, like
A lot of websites require you to give them your email address.
- These websites can (potentially) be hacked and the hackers can download your email address (among all others) from the website.
The website puts your email address in plain text somewhere where it can (easily) be found by email harvesting programs.
You can’t really do anything about point 1. You can kick your friend’s butt for not having an anti-virus program running on his computer or for surfing on suspicious websites. But then (in most cases) it may not be his fault altogether.
You can avoid the problems of point 2 by not using so commonly used email addresses (but this may not be possible for everyone).
What this article is about is point 3.
Before we get started, here’s some good advice (not really related to what’s following):
The Concept ∞
How do you cope with point 3? Easy:
You provide a different email address for each website that requires an email address.
Doing this has several advantages:
- If you receive spam over such a special email address, you immediately know which website is the culprit.
If you receive spam, you simply delete the email address. No more spam. You can’t do this if you provided the website with your main email address (obviously).
Although this concept is nice, there’s one big requirement for it:
Creating and deleting email addresses must be extremely easy/fast. Otherwise you won’t do it, trust me.
So, how do we do this? We use a so called catch-all email address.
This requires that you have the ability to create such an email address. Your best chance is if you have your own domain and your domain provider allows it.
- Create a sub domain for these email addresses. (Don’t use your TLD if you can because a sub domain is not that easy to guess.) For example, create
- Create a catch-all email address for this sub domain. This can either be a mailbox or a forwarding.
Now, when register at a website called “my-fancy-shop”, use
firstname.lastname@example.org as email address. “Creating” a new email address couldn’t be easier, could it?
If you want to delete/block an email address, simply create a forwarding to a non-existing email address (like
email@example.com). Then this email address won’t be caught by the catch-all email address but instead use its forwarding address.
P/Invoke is a way of calling C/C++ functions from a .NET program. It’s very easy to use. This article will cover the basics of using P/Invoke.
Note: This tutorial will focus on Windows and thus use Visual Studio. If you’re developing on another platform or with another IDE, adopting the things in this article should be easy enough.
With the Android NDK Google lets us write C/C++ code for Android. I don’t like writing C/C++ code because it’s error-prone but sometimes there’s no other way.
Unfortunately (this is the “I don’t like this” part), debugging Android C/C++ code is terribly difficult. If you don’t have a week to get the debugging toolchain working, and if you only need some quick and temporary solution, logging may be an alternative.
Ever wondered what Unicode is and how it relates to UTF-8, UTF-16, and so on? Or did you stumble over “code points” and didn’t know what the difference to characters is?
Then you should try out the shiny new Unicode Explorer.
For some basics, click on the “Basics” link in the Unicode Explorer.