![](https://aussie.zone/pictrs/image/0a4863ff-4b58-46e8-9266-dde5ef3fabc6.webp)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
And how if you share a file in Teams and then six months later you want to share a file with the same name to ANYONE else via teams, well that’s a big no-can-do. Teams just went ahead and uploaded that file to your “stuff to share” folder in OneDrive and didn’t put it in a subfolder unique to the chat, or add a unique prefix or suffix or anything because hey, you’ll only ever share a file with a particular name once in your life, right?
And nobody would ever want to share a file with the same name, but different data, right? So Teams can just give the end user the choice between replacing the current file with the new one, or sharing the same one again to these new guys, because there’s no possible use case for actually having two files named the same with different information in the file, right?
Nobody would want to share a README.TXT, or Photo001.jpg, or contact.ics, or a zip file of a folder they just downloaded from Teams’ SharePoint interface, the file that’s automatically called “OneDrive.zip” without the option to change it before saving, more than once, right? Right??
Fuck teams. And fuck Teams(New) too, just for the shitty name.
McAfee wrote a program that used the Sqlite library for database storage.
When going about its data storage business for McAfee’s program, the Sqlite library was storing files in C:\temp with prefixes like sqlite_3726371.
Users see that and get angry, and bug the Sqlite developers.
Now probably when initialising the Sqlite library McAfee could have given it the location of a directory to keep it’s temp files. Then they could have been tucked away somewhere along with the rest of the McAfee code base and be more easily recognised as belonging to them, but they didn’t.
So because of a bit of careless programming on McAfee’s part, Sqlite developers were getting the heat because the files were easily recognisable as belonging to them.
Because the Sqlite developers don’t have control of what McAfee was doing, the most expedient way to solve the problem was to obfuscate the name a bit.