You do realize vpns and older connectivity exists that needs values lower than 1280 right?
Of course. Nifty thing about open source means I can configure a system to allow or disallow anything. Each server operator can monitor their legit users traffic and find what they need to allow and dump the rest. Corporate VPN's will be using known values. "Free" VPN's can vary wildly but one need not support them if they choose not to. On some systems I only allow and MSS of 1460 and I also block TCP SYN packets with a TTL greater than 64 but that matches my user-base.
Sounds like you haven't used an Android. What Windows does is the exact same as what Android currently does, showing lots of warning screens. Which is very different from banning them altogether.
If an executable isn't code-signed, Windows SmartScreen displays a big scary "This file may harm your computer" warning box, requiring multiple clicks to get past. Been like that for years.
Code-signing certs used to be very expensive and annoying to obtain. The situation has improved a lot since the launch of Azure Trusted Signing, and now it's roughly on par with the cost and annoyance level of code-signing for Mac binaries.
Big scary box might as well be outright disallowing, since someone who isn't 100% sure about your software will likely be dissuaded by the warning. But if they want to install it, then they can.
My understanding of the article is that there is nothing that a user will be able to do to install your software.
> “developers [that we approve] will have the same freedom to distribute their apps directly to users through [installation] or to use any app store they prefer.”
What tools did you use to generate this response? Please include the make and model of the devices, and what os and browser you were running, including all browser plugins and other code which had screen access at that time.
reply