The 2009 Chevrolet Caprice SS, sold in the Middle East but made in Australia.
I came across a 2017 interview with former Holden chairman Peter Hanenberger, who was in charge when the company had its last number-one salesâ position in Australia. His words are prescient and everything he said then still applies today.
He spent over four and a half decades at GM so he knows the company better than most. Since he departed in 2003 he had seven successors at the time of the interview; and I believe there have been a couple more since.
A few interesting quotes.
âItâs [now] a very short-sighted company.â
It feels like it. The sort of retreating itâs done, the dismantling of global operations, and the failure to see how global platforms can achieve economies of scale is something only a company beholden to quarterly stock price results will do. And it doesnât help its longevity.
Even Holden, which looked like it was going to simply depart the passenger-car sector at the end of last year before a full withdrawal now, tells us that there doesnât appear to be a long-term plan in place that the US management is committed to. Not long ago they were going on about the two dozen models they planned to launch to field a competitive line-up.
âFor me General Motors was a global player. Today General Motors is shrinking to an American company with no foresight, which is in very bad shape, which has missed the market.â
Remember Hanenberger said this in 2017, when it still had presences in many Asian countries. In 2020 it very much looks like GM will be in the Americas (where it still fields reasonably complete line-ups, although God knows if they have anything in the pipeline to replace the existing models) and China. Russia, India, Australia, New Zealand and Thailand are gone or going, and western Europe went in 2017 before the interview.
âMaybe it fits into the vision of Trump; America first. But how the world is going to work also in the future is not because of America first and America only. Itâs global. I think there will be no GM in the near-future.â
Everyone else is desperate to do tie-ups while GM retreats. I think GM will still be around but itâll be a Chinese firm.
âI couldnât give a shit what they thought in America.â
I donât mean this as an anti-American quote, but I see it as a dig against bean counters (whatever their nationality) fixated on the short term and not motorheads who know their sector well.
âFor me Holden didnât have enough product, and the second one [priority] was I wanted to get these cars they had into export. For me it was very clear the products they had could be exported and they should go on to export.â
You saw the failure of this in the early 2010s when Holden failed to keep its Middle Eastern deals, and the US models returned. It could have been so different, though I realize GM was very cash-strapped when they needed the US taxpayer to bail them out.
Bruce Newton, who wrote the piece, says that the Middle East was worth up to 40,000 units per annum, with A$10,000 profit per car. It cost Holden A$20 million to develop them for left-hand drive. Iâd have held on to that sort of opportunity for dear life.
âThere was nothing going on that was creative towards the future of Holden as in Australia, New Zealand and toward the export market. They just neglected this whole thing.â
That was Hanenberger when he visited his old workplace in 2006. With product development cycles the way they are, itâs no wonder they were so ill placed when the Middle Eastern markets lost interest in the VE Commodore and WM Caprice (as the Chevrolet Lumina and Caprice), and China in the Buick Park Avenue.
Itâs an interesting interview and perhaps one of the best post mortems for Holden, even if it wasnât intended to be so three years ago.
Nadia has done it for ages, but I noticed Glamour did it for a while in 2018, and Wheels has stuck with it for its “new look”. What’s the deal with bordered covers?
I still prefer them bled, especially as I remember the difficulties of doing them back in the old days, and print agencies discouraged me from bleeds on cheaper jobs.
Unless there’s a clever reason, I can’t really see these covers as having a greater impact. Having bought Wheelsâ design issue recently, I was pretty disappointed in the overall look. Nothing really beats the feeling of the UVed, upmarket Phil Scott issues back in the late â80s, even if the price hike put it slightly outside my teenage budget, and I stopped getting the mag monthly.
Based on a cursory examination, CondĂŠ Nast’s Glamour went back to bled covers by the end of 2018, the gamble probably having done nothing for circulation.
Avira informs me that Ccleaner 5.51 is infected with a virus, called TR/Swrort.ofrgv.
I havenât come across anything online about this threat, except for reports in 2017 when Ccleaner was distributed with malware, eventually found to be the work of hackers who compromised the servers of the company behind Ccleaner. The Hacker News said that hackers got in there five months before replacing the legitimate Ccleaner with their own.
Iâve no idea where the blame should go this time, or even if my own computer has been compromised somewhere, but I’ve now downgraded to v. 5.50 and there have been no further alerts.
Anyone else had trouble with their Ccleaners?
Thatâs it for ânet neutrality in the US. The FCC has changed the rules, so their ISPs can throttle certain sitesâ traffic. They can conceivably charge more for Americans visiting certain websites, too. Itâs not a most pessimistic scenario: ISPs have attempted this behaviour before.
Itâs another step in the corporations controlling the internet there. We already have Google biasing itself toward corporate players when it comes to news: never mind that youâre a plucky independent who broke the story, Google News will send that traffic to corporate media.
The changes in the US will allow ISPs to act like cable providers. I reckon it could give them licence to monitor Americansâ traffic as well, including websites that they mightnât want others to know theyâre watching. As Sir Tim Berners-Lee, the inventor of the web, puts it: ‘We’re talking about it being just a human right that my ability to communicate with people on the web, to go to websites I want without being spied on is really, really crucial.’
Of course I have a vested interest in a fair and open internet. But everyone should. Without ânet neutrality, innovators will find it harder to get their creations into the public eye. Small businesses, in particular, will be hurt, because we canât pay to be in the âfast laneâ that ISPs will inevitably create for their favoured corporate partners. In the States, minority and rural communities will likely be hurt.
And while some might delight that certain websites pushing political viewpoints at odds with their own could be throttled, they also have to remember that this can happen to websites that share their own views. If it’s an independent site, it’s likely that it will face limits.
The companies that can afford to be in that âfast laneâ have benefited from ânet neutrality themselves, but are now pulling the ladder up so others canât climb it.
Itâs worth remembering that 80 per cent of Americans support ânet neutralityâthey are, like us, a largely fair-minded people. However, the FCC is comprised of unelected officials. Their ârepresentativesâ in the House and Senate are unlikely, according to articles Iâve read, to support their citizensâ will. Hereâs more on the subject, at Vox.
Since China censors its internet, we now have two of the biggest countries online giving their residents a limited form of access to online resources.
However, China might censor based on politics but its âGreat Wallâ wonât be as quick to block new websites that do some good in the world. Who knew? China might be better for small businesses trying to get a leg up than the United States.
This means that real innovation, creations that can gain some prominence online, could take place outside the US where, hopefully, we wonât be subjected to similar corporate agenda. (Nevertheless, our own history, where left and right backed the controversial s. 92A of the Copyright Act, suggests our lawmakers can be malleable when money talks.)
These innovations mightnât catch the publicâs imagination in quite the same wayâthe US has historically been important for getting them out there. Today, it got harder for those wonderful start-ups that I got to know over the years. Mix that with the USâs determination to put up trade barriers based on false beliefs about trade balances, weâre in for a less progressive (and I mean that in the vernacular, and not the political sense) ride. âThe rest of the worldâ needs to pull together in this new reality and ensure their subjects still have a fair crack at doing well, breaking through certain partiesâ desire to stunt human progress. Let Sir Tim have the last word, as he makes the case far more succinctly than I did above: ‘When I invented the web, I didnât have to ask anyone for permission, and neither did Americaâs successful internet entrepreneurs when they started their businesses. To reach its full potential, the internet must remain a permissionless space for creativity, innovation and free expression. In todayâs world, companies canât operate without internet, and access to it is controlled by just a few providers. The FCCâs announcements today [in April 2017] suggest they want to step back and allow concentrated market players to pick winners and losers online. Their talk is all about getting more people connected, but what is the point if your ISP only lets you watch the movies they choose, just like the old days of cable?’
Boris Johnson: usually a talented delivery, but with conflicting substance.
I spotted The Death of Expertise at Unity Books, but I wonder if the subject is as simple as the review of the book suggests.
Thereâs a lot out there about anti-intellectualism, and we know itâs not an exclusively American phenomenon. Tom Nichols, the bookâs author, writes, as quoted in The New York Times, âAmericans have reached a point where ignorance, especially of anything related to public policy, is an actual virtue. To reject the advice of experts is to assert autonomy, a way for Americans to insulate their increasingly fragile egos from ever being told theyâre wrong about anything. It is a new Declaration of Independence: No longer do we hold these truths to be self-evident, we hold all truths to be self-evident, even the ones that arenât true. All things are knowable and every opinion on any subject is as good as any other.â
I venture to say that the “death of expertise” is an Anglophone phenomenon. Head into Wikipedia, for instance, and youâll find proof that the masses are not a good way to ensure accuracy, at least not in the English version. Head into the German or Japanese editions and you find fewer errors, and begin to trust the pages more.
Given that many of âthe peopleâ cannot discern what is âfake newsâ and what is not, or who is a bot and who is not, then itâs absolutely foolhardy to propose that they also be the ones who determine the trustworthiness of a news source, as Facebook is wont to do.
I canât comment as much on countries I have spent less time in, but certainly in the Anglosphere, Iâve seen people advance, with confidence and self-authority, completely wrong positions, ones not backed up by real knowledge. You only need to visit some software support forums to see online examples of this phenomenon.
When I visit Sweden, for instance, thereâs a real care from individuals not to advance wrongful positions, although I admit I am limited by my own circles and the brief time I have spent there.
Itâs not so much that we donât value expertise, itâs that the bar for what constitutes an expert is set exceptionally low. Weâre often too trusting of sources or authorities who donât deserve our reverence. And I wonder if it comes with our language.
Iâll go so far as to say that the standing of certain individuals I had in my own mind was shattered when we were all going for the mayoralty in my two campaigns in 2010 and 2013. There certainly was, among some of my opponents, no correlation between knowledge and the position they already held in society. It didnât mean I disliked them. It just meant I wondered how they got as far as they did without getting found out.
Fortunately, the victor, whether you agreed with her policies or not, possessed real intelligence. The fact she may have political views at odds with yours is nothing to do with intelligence, but her own observations and beliefs. I can respect that (which is why I follow people on social media whose political views I disagree with).
In turn Iâm sure many of them disliked what I stood for, even if they liked me personally. Certainly it is tempting to conclude that some quarters in the media, appealing to the same anti-intellectualism that some of my rivals represented, didnât like a candidate asserting that we should increase our intellectual capital and pursue a knowledge economy. No hard feelings, mind. As an exercise, it served to confirm that, in my opinion, certain powers donât have peopleâs best interests at heart, and there is a distinct lack of professionalism (and, for that matter, diversity) in some industries. In other words, a mismatch between what one says one does, and what one actually does. Language as doublespeak.
So is it speaking English that makes us more careless? Maybe it is: as a lingua franca in some areas, merely speaking it might put a person up a few notches in othersâ estimation. Sandeep Deva Misra, in his blog post in 2013, believes thatâs the case, and that we shouldnât prejudge Anglophones so favourably if the quality of their thought isnât up to snuff.
Maybe thatâs what we need to do more of: look at the quality of thought, not the expression or make a judgement based on which language itâs come in. As English speakers, we enjoy a privilege. We can demand that others meet us on our terms and think poorly when someone speaks with an accent or confuses your and youâre. It gives us an immediate advantage because we have a command of the lingua franca of business and science. It gives us the impunity to write fictions in Wikipedia or make an argument sound appealing through sound bites, hoping to have made a quick getaway before weâre found out. Political debate has descended into style over substance for many, although this is nothing new. I was saying, although not blogging, things like this 20 years ago, and my students from 1999â2000 might remember my thoughts on Tony Blair’s 1997 campaign as being high on rhetoric and light on substance. Our willingness to accept things on face value without deeper analysis, lands us into trouble. We’re fooled by delivery and the authority that is attached with the English language.
Youâll next see this in action in a high-profile way when Facebook comes forth with more comment about Cambridge Analytica. I can almost promise you now that it wonât hold water.
I worry about the control that big corporations have over information. The danger is we get into the situation that existed in the Soviet Union with their papers, Pravda, which means “truth” and Izvestia, which means “news”. The joke was, there was no truth in Pravda and no news in Izvestia. Corporations will always promote stories that reflect well on them and suppress those that don’t.
That last bit definitely applies to a lot of the media today, especially those owned outside our country.
The rest makes for a great read as Prof Hawking talks about AI, the anti-science movement, Donald Trump, and what humanity needs to do urgently in science. Here’s that link again.
Now that I’ve gone four days without a BSOD, it does appear Microsoft realized it had rolled out another lemon, and, nearly two months later, patched things. Goodness knows how many hours it has cost people worldwideâthe forums have a lot of people reporting BSODs (maybe it’s confirmation bias, but I really don’t remember this many, ever). I posted this in a discussion entitled âWindows 10 is a nightmare!’, and the comments there make for sobering reading. A small number have had to purchase new computers; others report that the OS has made their computers unusable or that countless hours were spent trying to fix things. I can believe it. My addition:
I have to concur with the original poster: Windows 10 has been, hands-down, the most shockingly unreliable OS ever made, by anyone, anywhere.
I have spent more time here for this OS than at any other time with Microsoft productsâand Windows 10 has been terrible from day one.
Most recently, I have had multiple BSODs per day since the fall Creators update was installed, and until Microsoft rolled out a patch at the end of January that finally fixed problems of its own making. If your computer is BSODing multiple times a day, with 800-plus events in the reliability monitor per week, then you can imagine how little work gets done. Things finally calmed down on February 2, when I received the cumulative update. You can see the thread for yourself here: I actually feel sorry for the MS tech who stepped in, because heâs solving problems a crap product with faults not of his own making. They wonât be bugs that are in his handbook. Looking at this part of the forum alone, BSOD comes up a lot in the subject lines, more than I ever remember. So it isnât us, Microsoft, itâs you.
Going right back to day one, I canât believe how many threads Iâm involved in. Windows 10 started up differently each day, as it would forget its own settings each day. Some days Cortana worked, other days it didnât. Sometimes I had the UK keyboard (which I had never once installed), other days the US. In November 2015 I had to post a queryto ask how many hours it would take for a Windows 10 machine to shut down. Thatâs right, hours. At least thatâs better than some of you who commented earlier who canât get yours to start up.
Initially, Cortana required fiddling with each day to get it to work. Notifications once went back in timeâon a Saturday I began getting notifications from the previous Thursday. None from Friday though, they all vanished. Windows began forgetting my default browser and default PDF application, and no, you couldnât fix either from the standard settings. The Anniversary update took 11 attempts to install on this PCâand one of them screwed things up so badly my PC was bricked and wound up at the shop, where I had to spend money to get it fixed urgently. (I joked at the time it was called Windows 10 because you needed more than 10 attempts to do anything.) It never installed on my laptop at all: by the time Creators spring came round, the one update that was compatible with my laptop, it had been through 40 unsuccessful update cycles.
Thereâs still more that I can share, and you can probably find it via my profile. I would add more but on the original reply I actually hit a limit on these boxes. I guess Microsoft has a limit to how much bad news it can take from one user.
Microsoft has actually changed its QC procedures for the worseâthat is a matter of recordâand youâd think after three years of abject failure they would switch back. We see the same hackneyed official responses here day in, day out. They need to spend more time getting things right before they ship their OSs, and spare their community people a lot of wasted hours with solutions that generally do not work. In my latest thread, I fixed itâyes, the tech helped a bit, but ultimately I had to listen to my gut and believe that MS had messed up. I was right, but wow, at a massive cost to my real job with days lost to being Microsoftâs unpaid technician.
It is good, however, to come out the other side (knock on wood)âand despite the countless hours spent, I was once again right, and conventional wisdom was wrong. I’m not sure if that’s something to be that proud of. A healthy mistrust of big firms stands one in good stead nevertheless, and remember, every industry has thick people making stuff.
Two very helpful peopleâbwv848 at Bleeping Computer and Sumit Dhiman at Microsoftâhave taken me through the steps to figure out what was going on with my Windows 10 desktop computer, on which I’ve had between 100 and 200 BSODs since the Windows 10 Creators fall update arrived.
Windows claimed that the error was a DRIVER_IRQL_NOT_LESS_OR_EQUAL in tcpip.sys, but we know that that wasn’t the cause of the crash.
They had both got to the point where the Driver Verifier had to be run again. On the first attempt, the process had identified an Avira driver, although after removing and reinstalling the anti-virus program, the crashes continued. I had found other dodgy things in the Event Viewer, but solving them didn’t get rid of the BSODs.
Now that I’m back from holidayâand with Windows 10 crashing one more time and costing me more work that hadn’t been backed upâI gave Driver Verifier one more go.
I had been averse to it because of the crashes that resulted from it, and had a sense it would tell me the same thing it had in December.
True to form, Windows wouldn’t even load and it BSODed during the boot. But this time, running Windbg on the dump file revealed something called mobk.sys (Mozy Change Monitor Filter Driver), part of a program called Mozy.
I’ve never heard of Mozy, but it appears to be a back-up program. Checking my driver, it dates from April 2010 and was installed in 2012âaround the time I bought the computer.
It could well have been installed by me as part of a bundle, or by PB (the retailer).
Mozy wasn’t helpful. They have a forum, but when you sign up to use it, you get to a page where they want to charge you US$109 for one of their plans. Personally, if I was making software, I’d want reports from people like me. It’s not as though the question was complex: I wanted to know if it made sense to delete the offending driver in safe mode, or maybe download a trial version of their program, then remove it, in the hope that the driver would be overwritten and deleted. It’s only been a couple of hours since I Tweeted them, so I don’t expect any replies till tomorrow.
Rather than wait, I popped into safe mode and deleted mobk.sys from the system32\drivers folder.
These errors are deeply frustrating and in direct contrast to the stability that my Imacs have exhibited. Even though I’ve tired of OS X, at least I wasn’t losing work because of three to six BSODs per day.
The advice I can give to others is to create a system restore point, then run the Driver Verifier, and repeat the two processes until a culprit has been identified.
There are a few silver linings to this: I got rid of certain software which might have been insecure, and the random resets were quite handy in “clearing” the PC sometimes when I was doing work on it remotely.
I wonder what had changed in Windows between the spring and fall Creators updates that generated this very serious problem. I haven’t seen Windows crash this often since a dying laptop, on Vista, needed a fresh OS installation (it now runs Ubuntu). I’m still of the mind that Microsoft shipped a lemon, given that I’ve had no end of problems with this OS since it launched, from inconsistent behaviour (Windows 10 would originally be different each time it booted up, from Cortana settings to which keyboard it believed I was using), to very difficult updates (Anniversary took 11 attempts on this PC and never made it on to my laptop even after 40 attempts; it only updated to Creators because all other updates would fail).
While I can understand that there was no way either Mozy or Microsoft could have checked on a 2010 driver for compatibility, and there are so many configurations of Windows out there, there’s still no escaping that Windows 10 could have shipped with fewer bugs. Happily, as it turned out, the troubleshooting procedures may have worked, even if things wound up taking a month.
I’ll blog again if I’m wrong about Mozy.
PS. (January 18): After 24-plus hours with no crashes, I got another one, with the same message. Following my own advice, I ran the driver verifier again. Windbg pointed this time to Oracle Virtualbox. I intentionally ran an older version of this because since 2015, no newer version would work due to its hardening feature. Faced with no choice but to update, it had the same error which, finally, I traced to Mactype. This was the error, for those searching:
The virtual machine ‘Windows XP’ has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in ‘C:\Users\User\VirtualBox VMs\Windows XP\Logs\VBoxHardening.log’.
Result Code:
E_FAIL (0x80004005)
Component:
MachineWrap
Interface:
IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}
The key is to insert these three lines into Mactype.ini:
[UnloadDll]
VirtualBox.exe
VBoxSvc.exe
The error also picked up that there were McAfee drivers left behind from what should have been a full removal. I ran mcpr.exe, found in a thread with the ever-helpful Peter (Exbrit on the McAfee forums). Mcpr.exe did not remove the three drivers, so I took them out manually (despite this going against expert advice): mfeclnrk.sys, mfencbdc.sys and mfencrk.sys. There was also a driver from Malwarebytes, which I downloaded after expert advice in the wake of the damage done by Facebook and its forced download in 2016. Malwarebytes had to be removed with a program called mb-clean as it didn’t show up in the Windows 10 programs’ list.
One important point: when the system restored itself after the latest crash, it appeared the old mobk.sys reinstalled itself into system32\drivers. I removed it again in safe mode. I’ve since created multiple restore points so hopefully none of the now-removed drivers resurface to cause problems again.
I am very happy that I’m running the latest Virtualbox, too, since posting in 2015 resulted in no solid leads. It’s why I’m posting all of this stuff, in the hope others find it useful.âJY
P.PS. (January 22): No crashes for three days, I update both the Microsoft and Bleeping Computer threads with the good news, and within nine minutes, bam! Oracle VM Virtualbox is to blame again, if the driver verifier is accurate. That was yesterday. Today, I attempted to remove the program from the Windows Control Panel. Merely removing it caused three BSODs for three attempts, literally within minutes of each other. I booted into safe mode once, tried to remove it (I couldn’t), then back to the regular mode. I was then able to remove Virtualbox. I have since reinstalled itâlet’s see what happens next.âJY
P.P.PS. (January 23): Two BSODs this afternoon, still so very disappointed software is this unreliable today. Removing a networking driver from Virtualbox has made no difference. Same error as before. I haven’t re-run driver verifier, but I have now updated MacType to the latest version and double-checked the ini file changes are still there.âJY
P.P.P.PS. (January 24): MacType update did nothing. Bwv848 recommends removing Oracle Virtualbox altogether. I may have to do that, and reinstall it only when I need it, and see what happens. Sumit at Microsoft has given up for the time being.âJY
P.P.P.P.PS. (January 25): After one more crash despite some tweaking of the power options last night, I removed Oracle Virtualbox this morning. There were five remaining drivers that removal did not address, two from the latest version (VBoxNetAdp6.sys and VBoxNetLwf.sys) and three from the old one (VBoxNetAdp.sys, VBoxNetFlt.sys and VBoxUSB.sys). I manually removed them. No crashes since, though I will be interested to know if reinstalling, without any of the old drivers present, will make a difference.âJY
P.P.P.P.P.PS. (January 26): Got to its first crash by 11.45 a.m. Driver verifier now blames CLVirtualDrive.sys. Found one user on Virtualbox’s forum who had the DRIVER_IRQL_NOT_LESS_OR_EQUAL crash but the mod doesn’t like me helping out (very protective people, who don’t like their favourite software criticized). A system restore saw Oracle Virtualbox return, even though I made a restore point long after I deleted it. Let’s see what CLVirtualDrive.sys is. Four BSODs before noon. Man from Mozy got back to meâthe first contact other than on Twitterâbecause they wound up spamming me and never responded to my original support question. Amazing how a few eventsâincluding Facebook’s forced download in 2016âhave directly led to this time-wasting point in 2018.âJY
Many years ago, I was locked out of Facebook for 69 hours. It was completely a Facebook database problem, but in those days, they just locked you out without any explanation. It happened on a Friday. I believed I would not get back in till Facebook staff got back to work on Mondayâand I was right. This is a company that seems to close down for the weekend, and the important techs don’t get back till afterwards. It also doesn’t understand the concept of time zones, as six years ago, Facebook walls stopped working on the 1st of each month in every time zone ahead of Pacific Standard Time.
As it’s the weekend before the Gregorian New Year, Facebook’s probably closed again, so if their databases mess up, you could be stuck till Monday. Maybe later.
Except these days, I believe they run another con altogether, as I explained in 2016.
The theory: they now shift the blame to their users, by saying their computers are infected with malware, and forcing a malware scanner download on us. No one knows what this scanner actually does, but I know first-hand that it wrecks your real anti-virus program. I know first-hand that when Facebook and its scanner providers (which once included Kaspersky) are questioned on it, they clam up or they delete comments. I also know for a fact that others can log in to their Facebook accounts on the same “infected” PCs. All this is in earlier posts.
Some affected users over the last few years have said that they could wait this out, and three days seem to be the standard period (though some were out for a month). That sounds awfully close to 69 hours, which I was out for in 2014.
If word got out that their databases were this fragile, their share price would tumble.
In a year when Apple has had to apologize for short battery life on their Iphones, and sexual predators in Hollywood got outed, maybe we could finish off 2017 with Facebook having to apologize for lying to its users about just what this scanner does. Because we also know that people who have legitimate malware scannersâincluding ones supplied by Facebook’s “partners”âhave usually reported their PCs were clean.
Today is the day of the perfect storm: if there is a big database outage at Facebook, it’s the weekend, and no one is around to fix it. For whatever reason, thousands of people have been receiving Facebook’s malware-scan message, telling them their computers are infected: today has seen the biggest spike ever in users getting this, beginning 14 hours ago.
In my two years following this bug, I haven’t noticed any real common thread between affected users.
With Facebook’s old bug, where walls stopped working on the 1st of each month, there was a particularly noticeable rise in reports on Getsatisfaction when 2011 ticked over to 2012âprobably because no one was at work at Facebook to switch 2011 over to 2012. (I wonder if it had to be done manually. It honestly wouldn’t surprise me.)
While some of this is admittedly guesswork, because none of the companies involved are saying a thing, there are just too many coincidences.
Let’s sum up again.
⢠When certain Facebook accounts died three to four years ago, you were locked out, and this took roughly three days to fix (in my case, I got hit at a weekend, so nothing happened till Monday after a Friday bug). These bugs were account-specific.
⢠On January 1, 2012, Facebook walls around the world stopped working and would not show any entries from the new dayâtill it became January 1, 2012 in California, 21 hours behind the first group of people affected. It seems there is some manual tinkering that needs to go on with Facebook.
⢠Today, Facebook accuses people of having malware on their systems and demands they download a scanner. Yet we also know that others can log in to their Facebook accounts on the same “infected” machines. Conclusion: those computers are probably not infected as the lock-outs are account-specific. If it’s account-specific, then that leads me to believe it’s a database relating to that person.
⢠When people refuse to download Facebook’s scanner, many of their accounts come back online afterâyou guessed itâthree days. Ergo, they were probably never infected: Facebook lied to them.
⢠Those that do download the scanner cannot find it in their installed programs’ lists. Neither Facebook nor their scanner partners have ever come clean about what this program actually does or why it needs to reside in a hidden directory on Windows.
⢠It is December 30, 2017, and it’s a weekend, and there’s a spike in users getting this warning. It began, noticeably, 14 hours ago. It’s very hard to believe so many got infected at the same time by the same bug: even a regular virus, or the real malware that gets spread through Facebook, doesn’t have this pattern. It all points back to something happening on Facebook. My reckoning is that this won’t be fixed till January 1, 2018 or afterwards.
⢠Facebook is the home of fake accountsâit’s very easy to find bots and spammers. Logically, if resources are used to host the bots, then that means fewer resources for the rest of us, and potential database problems.
If you are stuck, I recommend you read the postscripts and relevant comments to my earlier posts: here and here.
