Firefox 社群討論區

I am the developer of FastF1, an open source Python package for downloading and analyzing Formula 1 race results, timing data and telemetry. The package is widely used in the fan community for independent analysis of results. For some advanced features, the addon requires users to authenticate with their Formula1/F1TV account. Since their services don't have an open login API, a companion addon is required to allow users to sign in using their browser and the official website.

I have just noticed that my developer account has been banned and the addon was blocked in Firefox. I have not received any email about this and don't know why exactly this decision was made. I'd like appeal this and reinstate my account and the addon, but I don't know how to proceed from here.

FastF1 and the companion addon are fully open source and intend no harm to users. https://github.com/theOehrly/Fast-F1 https://github.com/theOehrly/fastf1-companion

I hope this problem can be resolved.

I've been using alt+a to open new tabs in a multi account container for a long time. Recently that shortcut stopped working possibly with the update to v148 as indicated in this reddit thread.

alt+a is not listed as a shortcut in about:keyboard or in about:addons > manage extension shortcuts or in my ubuntu shortcuts nor in any software I can think of thats running. I've disabled all add-ons except multi account containers and it still does not work. Changing the shortcut to another works fine.

Why would just that shortcut stop working? What else can I do to diagnose the problem?

I don't plan to use any provided AI chatbot. I want to use models that I have downloaded and tested myself and which run on my PC. So please add the possibility to connect through major LLM APIs, the same way other tools way simpler than Firefox already allow to do.

I have recently installed the containers extension and have been having a bit of trouble with one site (the others are fine), which seems to originate from the manner in which the site is structured. As it references new pages, they are often in a different URL. For example, you start in login.site.com, which then tries to load dashboard.site.com, but it fails authentication on dashboard.site.com because it opens in a different container. Which then tries to open the login.site.com page again, which displays the login page, but showing it tying to complete the original authentication. I have tried to add each step along the way, but without success. Is there a way to overcome this?