One of the rules is that you are not permitted to sell third-level domains (3LD) underneath a second-level domain (2LD) in the proposed plan.

If DNS providers would provide a standardised API (or even allow standard dynamic updates with TSIG) it would make it a lot easier to use multiple providers. The two main problems I have come across are that the providers often do not let you add any NS records other than their own servers (so when a resolver caches the NS records and that provider goes down, it won't try using the other provider until the TTL expires), and updating records is painful because it involves logging into each of your providers websites to make the changes.

The book "SAP - A Map of The Minefield" by Stephen Birchall is a good read.

I don't see how they work out that it is 17938 infringements when they only set up one server, so they have only infringed once.

No longer an admin, but I have always given servers names based on their asset label, e.g. SV-0700543. The benefit of this is that the servers must be recorded in the asset register before they can be set up. When it comes to virtual machines I simply used a counter, e.g. VM-000001. The important ones (fsmo roles, database servers, app servers, etc) get friendly names with dns cname records.

Amarok dropped Shoutcast support in version 2.2 (October 2009) because of this.

Quite. It would make sense to simply use directshow or mediafoundation for decoding video so that any format for which the user has a codec installed would be supported. QtWebKit does this for example, so any web browser using Qt can take advantage of all the system codecs (as well as other pluggable backends, for example vlc).

So you think that a VPN should be used in conjunction with telnet and no passwords inside the network? Absurd! VPNs merely augment the current system. It would be no less secure with a VPN than without.

See http://www.mail-archive.com/gnupg-users@gnupg.org/msg10827.html.

The original paperkey software takes out the redundant key material for a smaller amount of data. You can restore the original key by combining the output with the public key.

To encode:

gpg --export-secret-key (thekey) | paperkey --output-type raw | dmtxwrite -e8 -f pdf > my_pdf_file.pdf

You can pass pdf, eps, svg, etc, to the -f option. Use 'dmtxwrite -l' to get a list of all supported image formats.

To decode:

dmtxread -N1 my_pdf_file.pdf | paperkey --pubring ~/.gnupg/pubring.gpg > my_new_secret_key.gpg

Untrue. Matroska is now officially supported by the DivX Plus HD profile which is used by a variety of devices.

You could also use ffdshow-tryout, which has DXVA support for AVC/H.264, allowing you to watch gpu-accelerated videos in any media player that supports directshow (such as Windows Media Player).

Nor are the resolvers capable of resolving names in zones served only by IPv6-connected dns servers (for example: mirror.ipv6.chaz6.com.). http://code.google.com/speed/public-dns/faq.html#ipv6

At my last place we assigned names to workstations of the form "WS-[badge number]". This had the advantage that the computer has to be put on the asset management system before it can be attached to the network, and for the vast majority of the time, this was the case. Our asset management system was intelligent enough that it could automatically update the location when the computer moved since every switch port was mapped to a location in the database (by room, floor, building, site).