Clocked (en)

Apple was on the forefront of human interfacing. Not only technical but also emotional. The better feel of Apple products! In one area, however, they missed the boat. The keyboard! Google with their Chromebooks are catching up on the feel and user experience. Their keyboard experience is even better than the MacBook experience. Just take a look at the keys left of the space bar on a MacBook and the ChromeBook.    MacBook ChromeBook Apple needs 4 keys! Google only 2! Industry standard knows the Control and Alt key. But Apple has the strange legacy from the early days of Apple computing called the Command key. Apple wake up! Linux has become the industry standard (not knowing the Command key concept). Much more user would switch from Windows to macOS if they were not hindered by the stupid Apple keyboard legacy. Google makes the switch experience smooth. Apple makes it hard. Guess who will win?

How do you contact a person with your mobile phone? FaceTime? Signal? WhatsApp? Call? Is it not about time to rephrase Phone Number into Contact Number?

Let's start by explaining a use case and the confusion it gives due to poor nomenclature in the crypto-world. The case of me giving a so-called private-key to someone, so I can send the person an encrypted message with the pared public-key, so only the receiver can open it. In this use case, in fact, I make a private-key public and assume the public-key to be private. This use case makes clear that the naming of private-key and public-key are a poor semantic choice. It is a poor choice because depending on the use case, the private-key can be public and the other way around. We better call the private-key just the encryption-key, and the public-key an encryption-vault. Let's then revisit the example use case now with the new naming. The case of me giving a so-called encryption-key to someone, so I can send the person an encrypted message in an encryption-vault, so only the receiver can open it. We have 4 clearly define objects now: public-encryption-key private-encryption-key...

The need for home servers, and what functions it needs to perform. A way to look at a home is as it being a thing on the mobile internet. Just like a mobile phone. What if you have an off grid (for electricity) home and the internet is down? And how to shield the home from unwanted data outflow from the home? I can see the need for a new kind of Network Attached Storage (NAS) what covers these scenarios. To cover these scenarios, you need a NAS with additional functionalities: In-home SSL Cloud mirroring Intrusion detection In-home SSL In house network security should be no different from the field data security. The current Root Certificate system (RCS) was never designed to cover this scenario. Another (outside the scope of this item) weakness of the current RCS, is that it is DNS dependent. Cloud mirroring Most users are using (also business users) their mobile phone as their primary data communication device and User Interface (UI). And to be global portable they use a Cloud serv...