t3chguy
commented
1 week ago There are multiple security fixes which would also need backporting if we were to make a build for a legacy OS, not all of them within our control. Electron has not ported security updates to Electron 22 which is the last version which supports Windows 7. We're up to Electron 33 now. We would not like to release a secure communication product with known security vulnerabilities for a small cohort of users. You are more than welcome to fork it and build such yourself, all of the code & even our workflows to build & package are wholly open source.
c33s
Your use case
What would you like to do?
upload and download files with matrix on legacy systems like win7 and win8.
Why would you like to do it?
because win10 & win11 are spyware and there are simply too many legacy systems out there which do not care about "win7 is EOL". in reality i know customers which use still win xp and also there i also know companies where there app still runs on php 5.6 with smyony 1.x it is simply reality that there is less and less budget for IT and security. keeping at least some important apps like browser and messenger would be helpful for partly airgapped systems to still be able to get some files (download it on a secure system an send via matrix to the company internal matrix server. so the legacy system would be safe if matrix would still work.)
How would you like to achieve it?
backport the media endpoint changes or add a compatibility layer
Have you considered any alternatives?
if you don't want to the following to happen and need a windows system (for using tools which don't run on wine), you only have the option to keep a win7 or win8 system.
Additional context
No response