Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport the new media endpoints to legacy OS's #28246

Closed
c33s opened this issue Oct 18, 2024 · 2 comments
Closed

Backport the new media endpoints to legacy OS's #28246

c33s opened this issue Oct 18, 2024 · 2 comments
Labels
A-Media O-Uncommon Most users are unlikely to come across this or unexpected workflow T-Enhancement

Comments

@c33s
Copy link

c33s commented Oct 18, 2024

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.

Windows 10 and Windows 11 have been criticized for privacy concerns due to several factors:

Telemetry and Data Collection: Both operating systems send a significant amount of data back to Microsoft, including device information, usage patterns, and diagnostic data. Even though users can limit some data sharing, they cannot fully opt out of telemetry.

Mandatory Microsoft Account: Windows 11 and some versions of Windows 10 push users towards using a Microsoft account to set up the system, making it harder to use a local account. This ties more personal data, like browsing history and settings, to the cloud.

Cloud Storage Integration: Windows encourages the use of OneDrive for storing files, which means that documents and other data can automatically be uploaded to Microsoft's cloud services, raising concerns about file security and data sovereignty.

Windows Defender: While Defender is a solid antivirus, it cannot be fully disabled in Windows 10 and 11. In addition, there are concerns that some files and system data are sent to Microsoft for analysis without explicit user consent.

These features contribute to concerns that Windows compromises user privacy by default.

Additional context

No response

@dosubot dosubot bot added A-Media O-Uncommon Most users are unlikely to come across this or unexpected workflow labels Oct 18, 2024
@t3chguy
Copy link
Member

t3chguy commented Oct 21, 2024

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.

@t3chguy t3chguy closed this as not planned Won't fix, can't repro, duplicate, stale Oct 21, 2024
@c33s
Copy link
Author

c33s commented Oct 21, 2024

understood. have assumed that this issue will be closed.

still sad, that you break such an essential api with no fallback for legacy clients.
you are talking about security vulnerabilities but expose users to the real privacy risks of companies who simply fetch data from us all and don't treat us in an ethical way.

if updating would be only about security, it would never be a problem to update but updates always introduce new "feature" or remove good features. firefox moving from xul to js long time ago, chrome forcing us all to manifest v2 and now manifest v3 which kills ad blocking. what is the sense of a secure communication app if the OS is taking pictures of everything entered on this machine? how can such an OS be more "secure" than an os which doesn't do that?

in general i can recommend louis rossmans videos

(i would have used invidious links if youtube wouldn't have made such a great effort of breaking/blocking it.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Media O-Uncommon Most users are unlikely to come across this or unexpected workflow T-Enhancement
Projects
None yet
Development

No branches or pull requests

2 participants