4 ms·
I have zero trust on how they handle this, judging by your post it is justified. This is why I decided to bite the bullet and go flatpak for the likes of teams
by Nux 5y ago
I have zero trust on how they handle this, judging by your post it is justified.
This is why I decided to bite the bullet and go flatpak for the likes of teams, slack and other proprietary software.
- mcny 5y ago> This is why I decided to bite the bullet and go flatpak for the likes of teams, slack and other proprietary software. I always recommend this now if it is an option. Even if Microsoft does nothing wrong, it is way too easy for me to make an error and somehow enable Microsoft antivirus stuff on my Fedora machine which I still don't know how I managed to do.
- yrro 5y agoFlatpak is best iff the vendor is producing the packages. I have found all too often than I'm stuck on an outdated version of a orphaned, unofficial pacakge...
- stinos 5y agoStill I wonder if you'd author all non-proprietary packages how many of these violations you'd find. Especially in smaller projects. Don't have any examples ready since I also try to avoid anything but established software, but I'm certain in the past I've had issues like mentioned above, even persisting after removal of the package.