Skip to main content

Posts

Brussels could do a better job

Abstract Legal systems should enable good public services, not just complicate things. We (the people) don't really need governments, we need good public services. These days, too little is done to ensure a level playing field for companies on a global scale. Enabling big companies to lock buyers into their influence sphere and squeeze as much as possible money out of them. Below three examples where our public services fail. Selling hardware with preinstalled OS should be illegal If a consumer buys a smartphone or a personal computer, it is always sold with an operating system preinstalled. This fixes the consumer into the commercial influence sphere of the hardware seller. Apparently, the Brussels bureaucracy is not really interested in a plane playing field that enables European suppliers to participate in the smartphone and desktop computing market. Would Brussels really be interested in a plane playing field, it would not be allowed to sell end-user devices (smartphones and pe
Recent posts

Alphabet should rebrand their Other than search and advertising business

Alphabet Inc. should rebrand their Other than search and advertising business if they want to make serious business from it. The “Google” brand name is for a large part of the world associated with sneaky advertising practices. Not with a solid IT service supplier. Consequently, the other than search related products under the brand name “Google” are avoided. Why do I think this is the case? I started early with Google (then Suite) Workspace and supported several small businesses in the Netherlands to switch from Microsoft Exchange to Gmail. I also helped them with implementing Drive and G-Suite. After initial enthusiasm, I can see them all going back to Microsoft Office. They just trust the Microsoft brand more for the desktop. If Alphabet really wants to make a serious business out of Workspace, they need to brand it outside the Google brand as a separate division under Alphabet.

2024 Haneda Airport runway collision should not happen again

On 2 January again a runway incident happened. Known as the 2024 Haneda Airport runway collision . This kind of accidents should not happen on modern runways used in a high frequency. In this article, we sketch an architecture of a simple and cost-effective system that we think should be used to reduce the possibility of this kind of disasters happening again.  We made a draft design for a system to r educe the possibility of this kind of disasters happening again. More on this on our website

Better laptop keyboard by Google than by Apple.

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?

Crypto misconceptions due to poor semantics

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

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