I despise how security updates are bundled with feature updates.
-
@x41h @Em0nM4stodon grapheneOS is still android. Pixel is made by Google.
There's a difference between "barely any" and "no". I said barely any. There are Linux phones but there are very few of them and they all suck. Most are "currently out of stock".
If there was a conspiracy it's unlikely you or I would know it for sure.
@licho @Em0nM4stodon the only conspiracy is that Google tried to block sideloading APKs. I wonder why... GOS team are to release news of an OEM deal at some point.
-
@Em0nM4stodon I think it is really difficult to maintain and sustain more than just the latest version of a piece of software, which then in turn leads to fixes shipping together with features. Having had to back port security fixes to an old version of Android I really feel for picking the lowest cost way out.
@Em0nM4stodon @Aurimas Really irritating thing about the current Apple situation is that they are still providing security updates for older versions of the operating systems, but only on devices which cannot install 26. -
@Em0nM4stodon @Aurimas Really irritating thing about the current Apple situation is that they are still providing security updates for older versions of the operating systems, but only on devices which cannot install 26.
@pacavegano @Em0nM4stodon what do you think they should do instead?
-
I despise how security updates are
bundled with feature updates.Now we have to choose between risking getting malware from random criminal gangs when refusing to update, or getting embedded malware from the tech company itself that comes with their update.
And honestly at this point, I'm not sure which is worse.
@Em0nM4stodon ok, but look on technical side, most of updates is in binary format, and assumes one state, and leads to other. Now if you would like to have 2 updates, one for security, one for features.... it is difficult (I would like to say impossible) in diff approach.
You don't have 1 "start" version but multiple... maybe user has prev security, but not features....
Even for single app it seems that you would need to produce multiple versions of the same update.... lets say, you would always keep only 10 back... so 10 back, user can go with full, or only security... so there are 2 10 back, 9 back... user may start from each of those and choose going with features, or with security.... what will be even more wired...
Even if it would be distributed on source level... nope... it would be backporting security changes, or sometimes writing several versions of those....Or you have some idea how to do it? Maybe there is some doable way I simply don't see, hope you will share 🙂
-
@pacavegano @Em0nM4stodon what do you think they should do instead?
@Em0nM4stodon @Aurimas I think that they should allow users of any device to choose to continue to run the older operating system, with security updates, for as long as they continue to provide those updates on any device. -
@Em0nM4stodon @Aurimas I think that they should allow users of any device to choose to continue to run the older operating system, with security updates, for as long as they continue to provide those updates on any device.
@pacavegano @Em0nM4stodon so every OS version for every device for as long as they sell a device?
-
I despise how security updates are
bundled with feature updates.Now we have to choose between risking getting malware from random criminal gangs when refusing to update, or getting embedded malware from the tech company itself that comes with their update.
And honestly at this point, I'm not sure which is worse.
@Em0nM4stodon
Dear Debian,
Thank you for being Debian.
Love, Your users. -
I despise how security updates are
bundled with feature updates.Now we have to choose between risking getting malware from random criminal gangs when refusing to update, or getting embedded malware from the tech company itself that comes with their update.
And honestly at this point, I'm not sure which is worse.
@Em0nM4stodon
Try Ubuntu or similar -
@Em0nM4stodon ok, but look on technical side, most of updates is in binary format, and assumes one state, and leads to other. Now if you would like to have 2 updates, one for security, one for features.... it is difficult (I would like to say impossible) in diff approach.
You don't have 1 "start" version but multiple... maybe user has prev security, but not features....
Even for single app it seems that you would need to produce multiple versions of the same update.... lets say, you would always keep only 10 back... so 10 back, user can go with full, or only security... so there are 2 10 back, 9 back... user may start from each of those and choose going with features, or with security.... what will be even more wired...
Even if it would be distributed on source level... nope... it would be backporting security changes, or sometimes writing several versions of those....Or you have some idea how to do it? Maybe there is some doable way I simply don't see, hope you will share 🙂
@przemelek @Em0nM4stodon Honestly... that just sounde like everything is bundled way too closely
-
undefined oblomov@sociale.network shared this topic