Posts by Pascal Monett 19065 publicly visible posts • joined 10 Apr 2007
Agreed, this is no bug. This is a functionality that was implemented in a time when password security was not even thought about in any serious way.
The fact that the new version no longer uses this functionality means the developers have wisened up.
The fact that said new version is brand new means nobody worried about it before 2018 - which is way too late in my opinion.
As usual, all this is down to the failure of management to actually manage. There is no excuse for postponing an update at the last minute ; if management had taken the need into account, it would have planned the workload accordingly and made the time available.
Unfortunately, management today has nothing to do with such mundane things as planning and everything to do with Cover Your Ass. Since nobody has the balls to actually impose a deadline, we're all stuck with waiting until we're back to the wall and then we can only pray that nothing will go wrong - which, given Murphy's Law, has a coin toss' chance of happening.
Isn't that usually the case ?
Because, if authority was defined by competence, 1) our entire economy would come crashing down and 2) most IT admins would suddenly find themselves with board-level revenue, while board members would find themselves manning the Helldesk - and failing all Target Performance Indicators miserably.
If you follow them scrupulously and something goes wrong, you've got your iron-clad excuse right there in your hand.
And the blame gets shifted to the guy/team who wrote the instructions, and to the manager(s) who approved the instructions.
Don't you find that there's suddenly a lot less yelling in those situations ?
No, they can't. If you take vast amounts of data stored in entire rooms, and a processing unit measured in cubic meters, then yes, a machine can beat a human at Go, which is nothing to sneeze at.
But if you constrain the machine to the size of the human brain, the only thing machines are beating us at is precise mathematical computation and, until positronic brains become a reality, it's going to stay like that for a long time.
"If you wash the basmati four or five times in cold water (I use one of these) making sure pretty much each grain gets a rub between your fingers, then leave it to stand for half an hour before draining, it will then cook in 2-3 minutes when you need it in a hurry."
My dear sir, if I have to fondle each and every grain of rice I wish to cook, I'm pretty sure it'll take a hell of a lot longer than the 15 minutes of simmering the whole lot will normally require.
When cooked, strain and then rince with hot water to have non-sticky rice. Yes, it's as easy as that. I usually use an earthen pitcher in the microwave. When the water is boiling, the rice goes in and gets a twirl so as not to stick on the bottom. The flame goes to minimum and the microwave is set to nuke for 6 minutes. When it dings, I give the rice another twirl and set the microwave to minimum for another 6 minutes. At the next ding the rice gets another twirl in the water and I check its cooked state. Generally, for Basmati you'll need another minute or three. Then strain and rince with the microwaved water and voilà : perfectly cooked non-stick rice.
You can't fail, even if you're reasonably sloshed.
Yeah, he thought he was more intelligent than the rest of them.
Well, now he's going to have the time to take a full course in Defrauding Investors 1 0 1, courtesy of the California Justice System.
In ten years, he will claim that he is the brainchild of Icahn, and he'll make a fortune.
Funny how that sounds like Logitech had no idea how such a thing could possibly happen. It's almost as if Logitech was begging us to believe that there was some rogue engineer that put an API in place and Logitech wasn't aware of it.
Because rogue engineers are totally a thing these days, right ?
Slack shut down the accounts of people who had been to a blacklisted country, but no longer were there ?
That is not how you do it. You use geolocation to forbid blacklisted countries from using your app from the forbidden country.
Otherwise, you are saying that it is the people from those countries who cannot use your app wherever they are, and that's called racism.
And, if they're in the US, you're getting sued. As you should be.
Apparently, they're not doing their job very well. They might want to start using some intrusion detection software, I hear that that is a thing these days.
Either that or they need to pay their personnel better and train them more often.
That is a shame. It means that no actual decision is going to be taken, arguments are not going to be heard and Justice has no say.
All that in the name of protecting the revenue of a corporation that has more money than it can spend.
Google obviously knew what it was doing ; it evaluated the man (a crook with a strong penchant for money) and found the right amount to shut him up before a judge could lay in with a decision that might hurt Google long term more than losing the case would.
Hey, two crooks would obviously find common ground, right ?
No, no, you're not with the program.
After Serverless Computing, we'll be ushered into a new era that will be called Power-Assisted Computing. In order to properly adapt this paradigm, you should build a Computer Assistant permeated with AI and 7G connections.
Oh, and a holographic screen. It has to be holographic.
It certainly looks like the way to go. Logitech is just one example of companies that don't actually care about providing you with a reliable service, they're all just faffing about, changing products and functionalities as soon as a new PHB takes office.
There is no long-term plan and no care of not disrupting the user experience.
It's all about getting the dough now, then screw you.
That is why I am convinced that true home automation is going to actually be open source - by the people, for the people. That will be the only thing that actually has a chance of working for more than 18 months.
This whole project stinks from the other side of the screen.
The customer doesn't give the data to allow the project to go forward, then doesn't want to look like it's paying for software (wtf ??), then gets all huffy and claims that 25% sales loss is IBM's fault.
I'm not defending IBM, but if what IBM says is true, that is one shitty customer.
On the other hand, IBM, please : talking to the Agile team is what you're supposed to do.
Unless IBM manages Agile with a Waterfall approach ? Hmm, that might explain a few things.
Pray tell, does it have anything to ensure that car control commands cannot be overridden by the effing media player ?
Or by the Internet, due to the frakkin' "continuous connectivity" we're all going to bask in ?
Because if not, well, there won't be much improvement, right ?
Well apparently not fantastic enough to refuse selling out to the Master Borgifier.
Shame on those people who decided to cash out and let a "fantastic resource" get emasculated by Microsoft.
And don't tell me they didn't have a clue. The CxOs who took the decision knew Microsoft acquisition history just like the rest of us - except they got truckloads of cash.
I hope they enjoy watching their life's work become a husk of its former self.
Well here's some news : even if the USA is royally screwing itself over, the rest of the world is getting along fine and many, many countries have full fiber FTTP projects going on.
I myself, after having left a year ago a village where I had an acceptable 12MBps connection and arriving in a village where there was nothing but a communal WiFi that worked when it wanted, I have now signed up for and will be getting a 1GBps connection as of next January 3rd. For €50/month. Oh, and there's no throttling or limit in the amount of data, like some operators actually dare to do. If I download 1GBps for thirty days straight (supposing I manage to find enough data for that), then that's my business.
So carry on, USA. You will soon be in the backwaters of the internet, and I'll be reading about how you barely manage a national average of 25MBps whilst surfing at 40 times that speed.
I've got a different problem with that : who on Earth decided that is it a good idea to use the gram to express exoplanetary loss of mass ?
We're talking about a planet that is light-years away, losing copious amounts of mass, and you deliberately choose the smallest unit of mass we have to express it ?
Saying ten thousand tons of mass per second wasn't impressive enough ?
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2025
