There is an opportunity here
If HP would add a braille bar on the bottom, this would make an excellent PC for the visual impaired.
315 publicly visible posts • joined 28 Aug 2014
The MSM companies are more and more forced by legal cases to check their user's ages, which in practice means to identify the user. In essence their is nothing wrong with that.
The problem is with where this verification is done. This is more of a lobby to have verification at OS system level, so MSM falls back to the OS for this purpose.
As might anybody else.... This is a security nightmare.
If somebody says "It almost works." I knod and sympathise and I recall the quote I once saw on a tile
"If you see light at the end of the tunnel ...... you are facing the wrong direction!"
Although I very very much love to see someone succeed in the attempt to have a workable C/C++ solution for the memory management stuff.
AI has its merits as it is quite capable in processing vast quantities of data and finding patterns inside them. Not something a human being cannot do, but AI comes up with results much faster - leaving the human to check if the outcome of the AI is plausible. I have seen very good use of processing medical scan data, AI could spot the out of the ordinary which many doctors would overlook. This is a huge benefit - saving time, money and occasionally a life.
But the fields of application are different - software engineering being no exception. These jobs will be different in the future - but senior and junior levels will be there as they are today.
It is not just Windows, it is the complete codebase - it is hundreds of products, some not even designed by themselves but acquired in a merger/takeover.
Not even considering used libraries, which may be statically linked, so different versions from the same lib are used and updates are not compatible, etc.
It should be called Project Snakepit
If your application uses external libraries, plugins, etc, this is inevitable. It is not a question if you will get hit by such threats, it is about when and how often.
Yesterday Log4j, React today, and another yet-unknown one tomorrow.
Be prepared and patch when signalled to do so. Period. No excuses. The security of your application is your responsibility alone.
They should have asked the French police to take over the request for data within the investigation, the French police could acquire such information in a legal matter. That is how this is supposed to work anyway, crime does not stop at the borders and neither does criminal investigation.
I do not think there is any legilation on either side of the Atlantic that states that the government can force anyone to break the law.
Some governments are looking to cloud solutions that do not depend on an US based provider - for good reasons.
So there may be some providers not listed here that may get (some) market share, although it will not be too significant on a world wide top 3 scale - but significant enough to be noted.
This particular individual appears to be bought to commit crimes.
But as cyber security awareness increases, security gets better, the weakest link in here is the human.
One can think of the situation where an individual of company "X" can be bribed or -worse- blackmailed to commit these crimes. It is easy enough for these criminals to look at MSM at find everything about you. Such inside jobs have the danger of going to be big.
In order to minimise the risk of this happening, companies shall appoint at least two pairs of eyes to any one job, and preferably different eyes each time - amongst other measures.
... is the only way left to "make" money out of AI.
The investment in AI is so huge that companies desperatly do whatever they can to get money out of it.
This is one example - the others will follow, or already have similar strategies.
The only way to avoid this is to find a non-AI infested alternative.