outline-apps VS web-bugs

Outline, a free and open-source VPN service developed by Google, is renowned for its user-friendly design. It can be conveniently established on diverse platforms, and this blog will specifically guide you through the process of setting up a self-hosted Outline VPN using Amazon LightSail.

Another good way is to set up your own VPN server on Digitalocean or something. Use a VPN protocol that is good at escaping detection. I recommend Outline VPN (getoutline.org). It's an open-source project that uses the Shadowsocks protocol and aims to provide censorship-free Internet to journalists in certain countries. It's not a VPN service so you need to set it up on your own server.

Use a self-hosted Outline on GCP or any other cloud platform, it works really well in my experience for circumventing these blocks.

Yes. Use an outline service. https://getoutline.org/

See https://github.com/Jigsaw-Code/outline-client/issues/1177, technically you don't need Outline Client, compatible Shadowsocks client like https://github.com/shadowsocks/ShadowsocksX-NG/releases should work too.

The thread is very long, here is the relevant comment:

https://github.com/webcompat/web-bugs/issues/131916#issuecom...

https://github.com/webcompat/web-bugs/issues?q=is%3Aopen+is%...

Microsoft Teams (which I don't think many people use voluntarily) in particular breaks in stupid ways - and then in others if you spoof your user agent.

a link to the video would help with troubleshooting, seems like another case of "this site or this particular feature doesn't support firefox" otherwise report to https://webcompat.com/

Have any of you faced this? If the website is made to open only in chromium-based browsers, I am planning to report to Webcompat. But before that, I thought I would make sure from others. Any experience or quick fix would be appreciated.

Teams was a classic hellhole for me when I was using Linux. Nowadays it lets you in but Firefox genuinely doesn't support all of the features the Teams site uses. This means certain features are made unavailable to Firefox users. Forcing the user agent makes some of these partially work but they are also still broken so Mozilla doesn't want to enable a user agent override by default and Microsoft doesn't want to enable a feature that only half works.

This GitHub WebCompat issue serves as a good example history https://github.com/webcompat/web-bugs/issues/77892

https://github.com/webcompat/web-bugs/issues/125920#issuecom...

having recently looked at a firefox performance regression for filing a bugreport, tooling that tracks performance (quite publicly) sees attention, easy upload to share tracing profiles also helps: https://firefox-source-docs.mozilla.org/testing/perfdocs/ind...

Their dedicated blog keeps you posted if firefox perf is your interest https://blog.mozilla.org/performance/

If you have a particular website you notice chromium being significantly faster with, for an easy report, there's https://webcompat.com/ - though bugzilla is better than it seems when coming from github issues