alternative-frontends VS web-bugs

use alternative privacy-focused frontends: https://github.com/digitalblossom/alternative-frontends

I use nitter and proxigram to query RSS feeds.

I use something similar to this, the only differences are because my use case is privacy protection and avoiding algorithmic feeds. I use the Redirector extension for Firefox so that it redirects e.g. Youtube, Twitter, and StackOverflow links to the corresponding alternative frontends Piped, Nitter, and AnonymousOverflow. You can find maintained lists [1] [2] of such projects and their instances. Mostly they are FOSS and privacy-respecting, and they have distraction-free frontends because it's a helpful coincidence of being ethical software.

[1] https://github.com/digitalblossom/alternative-frontends

for a full list, refer this: https://github.com/digitalblossom/alternative-frontends.

There are front end alternatives for major sites if you really need that btw. I use from time time to time Invidious when I want t o see a YT video for example. As for sites that require tracking cookies to work I simply stopped using them. If a given site requires the use of intrusive "necessary" cookies I just stop using it. I'm convinced is about priorities. If you quit a browser that is safe because is slow, well, you need to re-estate your priorities imho (not you, op, anyone ;) ).

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