Obligatory "ignore this space" : https://sacoronavirus.co.za

Domains give us evidence of a marketing machine out of control. We might say, totally out of control, but we think that a rally driver will just laugh at us. A rally driver must snigger when people think they're making fine distinctions about control and the lack thereof. If a rally driver doesn't have a guiding angel he must be God himself.

A personal God doesn't need us to identify ourselves. Centralized authentication is what we come to look at when we talk of domains that are authentication domains. Decentralized authentication is why we have so much hassle with passwords. Some people think that the best means of solving a problem is to cozy up to someone who might have the right potential; if this person offers objections on the grounds of his personal feelings towards the task, those who gave it to him must leave the country for a while or for good. It's only because of doubts about the integrity of those who spend their lives checking the integrity of things, that the idea of centralized authentication can be said to be a bad one. On this one I really do insist that my personal feelings aught to be trusted; which comes with the side effect that those who do all their work in the cloud will have a reason to back up exactly one file.

And the side effect of having to look at versions again. Isn't that such a great website? Go with your intuition!

An authentication domain is a headache: we need a replicable database, for one thing. Unix uids (user id) are not suitable for replication, because then we need to make arbitrary assignments of numeric ranges, which doesn't feel like technology. If you don't believe me, try NIS out for yourself. But, of course, that got called obsolete before it was perfected. After countless years of treachery, we are now back on track to roll out GNU fileservers and authentication servers that can be managed just as easily as EZ itself.

But let me not harp on the past, and recall the manner in which people are managing files that they think they might own if someone is being nice. We dispense with the protocol, for the only reason anyone would need this description laid out is if they're the kind of person who will only use https.

Networking is about numbers, but this is also where we talk of a bit that isn't a boolean. This matters to networking specialists; generally speaking, however, we nonetheless deal with numbers and leave the encoding of them as a curiosity. A network address works just like pigeon-holes. For those who are confused by that term, the use of pigeons to carry messages is a dark history. A story is told of a bird that was made extinct in the same manner the Buffalo became a rare creature. But it wasn't one or two men who brought this state of affairs about. That was brought about in part by people who believed the bible where it says that the earth is ours to do what we will with it. I've always greatly respected those who concern themselves about creatures that are endangered. But naturalists end up finding enormous numbers of extremely rare animals, don't they?

The Buffalo, we know by intuition, is yet revered by those who call themselves Native Americans; I haven't heard of any such folk talking about pigeons. And I haven't heard of any message that is so unimportant that it may be entrusted to a bird.

Domain Name System (DNS) is a particularly efficient mechanism for the conversion of arbitrary names to network addresses, and it is an example of replication that doesn't require monkeys on call every minute of every day. Sadly, it is true, many people must just do a job, and the technicalities are all so many mill wheels. My researches, including that of verifying for myself the truth of GPL, showed me plainly that soon after the introduction of DNS, people stopped wanting to build on past success: the new protocols were made by people who got excited about big numbers but couldn't say, stop bit.

The use of DNS for authentication was an idea that rolls around yet. The introduction of new top level domains is an idea that seems to pop up once a generation. Top level domains is an example of a root list; DNS is a tree, therefore.

"In any hierarchical namespace, one aught to make sure that the number of children is manageable, and that their identifiers aren't deliberately misleading," said the boy with unnecessary heartache, after taking a sip of cider.

The boy, with whom I have unnecessary sympathy, might have gotten tired of saying things like this naturally. But in a flash he saw that the people telling him that one day someone will solve these hassling problems who is being paid to solve them, were so many passenger pigeons.

Migratory birds who give yapping dogs a reason to look at their limbs and not give thanks to their maker do lead us to think it possible that boys with rifles and no other pasttime could bring about the extinction of creatures that are not rare by any means; which explains certain imagery to those who are following me.

But leaders must lead by following people in other countries; for this is how they obtained their leadership position. And no speech is complete without referring to money spent on the things that boys can tell their mothers--and possibly girls, too.

"Look at our new top level domain. This will unite the people who belong here. Those who think that we've just spent money on things which are just going to gather dust, are obviously racist."