laserembeddings VS web-bugs

You're pretty much right on the money. For ParaCrawl[1] (which I worked on) we used fast machine translation systems that were "good enough" to translate one side of each pair to the language of the other, see whether they'd match sufficiently, and then deal with all the false positives through various filtering methods. Other datasets I know of use multilingual sentence embeddings, like LASER[2], to compute the distance between two sentences.

Both of these methods have a bootstrapping problem, but at this point in the MT for many languages we have enough data to get started. Previous iterations of ParaCrawl used things like document structure and overlap of named entities among sentences to identify matching pairs. But this is much less robust. I don't know how they solve this problem today for low-resource languages.

[1] https://paracrawl.eu

[2] https://github.com/yannvgn/laserembeddings

I've been using LASER from Facebook Research via https://github.com/yannvgn/laserembeddings to accept multi-lingual input in front of the the domain-specific models for recommendations and stuff (that are trained on English annotated examples).

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