Web developers: when you say, “this browser does not support our site,” what you REALLY mean is that you don’t support the browser. Don’t turn it around on the browser/user because you chose not to stick to universally-supported standards, or worse, are doing user agent sniffing.

@cassidyjames This is the same issue with distros though, you can't expect the devs to support every possible configuration out there.

@alatiera @cassidyjames with web you have polyfills that should cover most cases unless you use some fancy API that Google just added to Chrome

@bilelmoussaoui @cassidyjames You can make the same case with glib and gtk and "stable apis" but we know it doesn't hold cause the tiniest change in the system can break things.

Web engines are no different, they don't all of them behave the same way and we know their behavior can drastically very or be bugged and bitrotten.

@alatiera @cassidyjames right but that's not an excuse for deliberately blocking users from a specific browser. Especially the way chrome does it.

Follow

@bilelmoussaoui @cassidyjames I don't see anything different with asking people to use something they have/are testing and have assured to work and us doing the same with desktop apps.

@alatiera @bilelmoussaoui the web’s promise is that it is universally accessible from any device, browser, etc. That’s not at all the case you with apps designed for a specific platform. There are absolutely advantages to either approach, but I think a healthy, open web is essential.

Sign in to participate in the conversation
Mastodon

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!