I don't know, the more time passes the more I convince myself that the net benefits of antivirus software do not (an maybe never) exceed their downsides. In decades I've heard so many stories about AV software behaving suspiciously, using borderline shady tricks to monitor user activity, causing severe performance degradation, etc
Why sqlite3 temp files were renamed 'etilqs_*' (2006)
81–90 of 146 posts
Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)
#82Earlier quoted context omitted.
It is a web app that has exclusive ownership over its SQLite databases. Exactly one SQLiteConnection instance per for the lifetime of the application.
Does that mean you have to bring the whole app down if you need to manually insert something in sql?
Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)
#83Earlier quoted context omitted.
Daniel Stenberg has also gotten some ... interesting ... emails because people found the curl license somewhere and assumed he was responsible for $stuff. https://daniel.haxx.se/blog/2016/01/11/tales-from-my-inbox-p... https://daniel.haxx.se/blog/2016/01/19/subject-urgent-warnin... https://daniel.haxx.se/blog/2018/02/16/why-is-your-email-in-... https://daniel.haxx.se/blog/2021/02/19/i-will-slaughter-you/
The last one has to be an elaborate troll. Only a 4chan user would type "RIP Terry A. Davis" anywhere.
RIP Terry. A. Davis
Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)
#84The relevant snippet: /* ** Temporary files are named starting with this prefix followed by 16 random ** alphanumeric characters, and no file extension. They are stored in the ** OS's standard temporary file directory, and are deleted prior to exit. ** If sqlite is being embedded in another program, you may wish to change the ** prefix to reflect your program's name, so that if your program exits ** prematurely, old…
Or the direct link thither: https://github.com/mackyle/sqlite/blob/18cf47156abe94255ae14... .
Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)
#85The relevant snippet: /* ** Temporary files are named starting with this prefix followed by 16 random ** alphanumeric characters, and no file extension. They are stored in the ** OS's standard temporary file directory, and are deleted prior to exit. ** If sqlite is being embedded in another program, you may wish to change the ** prefix to reflect your program's name, so that if your program exits ** prematurely, old…
Building illuminati lairs now, are we!
Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)
#86Love it. Too bad there aren't enough Mac users to prompt a similar backlash against Macs littering every computer they visit on the network with .DS_Store and other turds.
This isn't remotely comparable. Those .DS_Store files are created in arbitrary directories by the Apple file manager or something. The SQLite temp files are created in the OS-specific temporary directory (e.g. C:/Users/username/AppData/Local/Temp or whatever on Windows) which is specifically intended for that purpose. SQLite isn't doing anything wrong; that's where it's supposed to store temporary data that doesn't f…
Apple, in its arrogance and backwardness, doesn't store those choices on the BROWSING user's computer; it stores them in the directories on the computer being browsed... where, by the way, they'll be trounced by the next Finder user who comes along.
Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)
#87Earlier quoted context omitted.
You mean like those thumbs.db files windows leaves on every computer they visit on the network?
Windows XP is the last Windows version that does this.
Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)
#88The relevant snippet: /* ** Temporary files are named starting with this prefix followed by 16 random ** alphanumeric characters, and no file extension. They are stored in the ** OS's standard temporary file directory, and are deleted prior to exit. ** If sqlite is being embedded in another program, you may wish to change the ** prefix to reflect your program's name, so that if your program exits ** prematurely, old…
>> 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. Building illuminati lairs now, are we!
Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)
#89Earlier quoted context omitted.
I never knew that. How come they end up in Git repositories then? They shouldn't be visible to Git running on a native Mac filesystem?
They're just a file, so git can see it. Good habit would be to add it to the project's gitignore, or your global gitignore (or both)
`.gitignore` is for stuff that all developers need to ignore, like compiler output, and should be kept to the bare minimum.
Re: Why sqlite3 temp files were renamed 'etilqs_*' (2006)
#90Love it. Too bad there aren't enough Mac users to prompt a similar backlash against Macs littering every computer they visit on the network with .DS_Store and other turds.