Mcafee accidentally made users call the devs of SQLite and complain.
Mcafee accidentally made users call the devs of SQLite and complain.
via: @memes@wetdry.world
https://wetdry.world/@memes/112717700557038278
the sqlite codebase is a gem.
tldr; mcaffee made a shit ton of sqlite files in the temp folder causing people to call the sqlite devs phone angrily. now they name all files etilqs to prevent this.
Text from the screenshot:
2006-10-31: The default prefix used to be "sqlite_". But then Mcafee started using SQLite in their anti-virus product and it started putting files with the "sqlite" name in the c:/temp folder. This annoyed many windows users. Those users would then do a Google search for "sqlite", find the telephone numbers of the developers and call to wake them up at night and complain. For this reason, the default name prefix is changed to be "sqlite" spelled backwards. So the temp files are still identified, but anybody smart enough to figure out the code is also likely smart enough to know that calling the developer will not help get rid of the file.
Code found at: https://github.com/sqlite/sqlite/blob/master/src/os.h#L65 (The line numbers in the screenshot and the code don't match up)
Wasn’t there a story about people calling curl devs because of car issues?
For what it’s worth, I’m sure the SQLite devs could help somebody clean up their temp files. They just really shouldn’t have to.
Are you talking about this: I have toyota corola?
Well
Forgive my ignorance. SQLite is a database software. Why would McAffee create lots of database files?
[Edit:] I’m not asking why a program needs to store data. I’m asking why that necessitates many files. One database file (or one per table) should be enough, right?
Many programs use SQLite internally and McAfee decided to store the database files in C:/Temp
No, these are sqlite temp files, not the database files. McAfee had no control over the temp files.
Sqlite is a great embedded database.
If you are storing lots and lots of information in a JSON file, CSV file, or coming up with your own serialisation... Chances are, sqlite is going to do it better.
I know loads of android apps use sqlite for storage. I've also managed to open quite a few programmes "proprietary" file format in sqlite.The program needs to store multiple temporary files (one per virus definition update, or scan results or whatever purpose).
It looks like they simply picked sqlite as a format because the data has a structured format and that way they leverage databases robustness, easiness to read and query the data.
The comment appears to be from 2006. Sqlite mightve had some limitations then that necessitated creating a new (temporary) database file as a subset of larger database for performance reasons or to allow multiple processes to read/write them and then consolidate data back into the single database.
Al sorts of applications would enjoy a database to log all sorts of stuff, store results, capture events, etc.
SQLite is great because it doesn't necessitate another infra dependency as it is stored to file
John McAfee would be spinning like a rotisserie chicken in his grave. Or at least he would be if McAfee Software hadn't already turned to shit long before his death.
So the temp files are still identified, but anybody smart enough to figure out the code is also likely smart enough to know that calling the developer will not help get rid of the file.
Don't underestimate the stupidity of your average person.
Was gonna say, this wouldn't happen on John's watch. /S
I love how the solution didn't involve changing the prefix to "mcaffee_". Now users don't know who to blame. Great. That's so nice of them.
Then
mcaffee_would be appearing in unrelated sqlite-using applicationsOh, I thought that the temp files were named by the user. If that's not the case, that these are not databases created specifically by McAfee in the temp directory, then I'm not sure what the appropriate solution should be. Obscuring the file type and how the file is used from users is still a bad practice.
the solution is not on the mcafee side but on sqlite
I used to tell people that John McAfee always exited a room by jumping through a window while yelling, "MCAFEE RULES!" Which he didn't, but maybe he did? Anyway, I miss that crazy motherfucker. Sometimes nuts make the world more fun.
He was an interesting one but not a good one.
Hm. The first hit on DuckDuckGo is a single entry for a guy and all it says is Contact the Business Inquiries.
You would think a better solution to this problem would be to put a message on that page stating that if you’re a McAfee user looking for information about SQLite files in your temp folder, to call the McAfee support line.
But hey what do I know, right?
Yup, you found the developer. That's his phone number.
It's not exactly a new change either. In 2006 people weren't going to the specific page from duckduckgo, they were probably finding the sqlite homepage, and then tracking down the contact info.
20 years later it's probably better to maintain consistency with the prefix than to change it even if it's weird.
The way I understand the users didn't necessarily realize McAfee is responsible, just that a bunch of sqlite files appeared in temp so they might not connect the dots here anyway. Or even know McAfee is installed considering their shady practices.
Fair point about not knowing McAfee if involved. But at the same time, it beats having your dev getting phone calls at all hours because McAfee’s devs were to lazy to ready the source file and learn how to change the freaking prefix of the file.
There's a solution for this McAfee problem:
What a time it must've been, being able to publish your phone number online without fear. Now you give it to any website and it's sold straight away to advertisers. Making it public would be a nightmare.
Making it public is required by law at least in Germany, Impressumspflicht
I have my phone number on my personal website—never had any adverse consequences. In fact, the only two calls I've gotten have both been at my work number which isn't on there somehow. One to ask a genuine question and one to give me 30 bucks in appreciation.
You don’t even need to make public yourself. City governments do it automatically, mostly if you’re a home owner. Other companies do it because they keep getting hacked.
Try it.
Go to your favorite search engine and type in your phone number (format it to look like a phone number). If you haven’t already gone through and had yourself removed from these types of sites, you’ll be appalled at what you find.
The developer still has their phone number up. But SQLite was written in the early days when not everyone had a dedicated internet line, so if there was an urgent need for them to be reached, they could be called and then connect to the internet.
Although depending on where you are, phone numbers are already public information, and can be trivially looked up. There's a non-zero amount of movies where a character goes and calls the phone number of a friend from a phone book, and that was before you had such fanciness as computers to do the looking for you.