-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
FrozenFox
A personal hodgepodge of css and js hacks to firefox that I personally enjoy. Strong emphasis on a blend of minimalism and functionality.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
FirefoxCSS-Store
A collection site of Firefox userchrome themes, mostly from FirefoxCSS Reddit community.
-
uc.css.js
A dark indigo CSS theme for Firefox and a large collection of privileged scripts to add new buttons, menus, and behaviors and eliminate nuisances. The theme is similar to other userChrome stylesheets, but it's intended for use with an autoconfig loader like fx-autoconfig, since it uses JavaScript to implement its more functional features.
-
FirefoxPWA
Discontinued A tool to install, manage and use Progressive Web Apps (PWAs) in Mozilla Firefox [Moved to: https://github.com/filips123/PWAsForFirefox]
...and that second option is basically a database full of CSS themes: in the repository, there's a themes directory, that, upon installation, will get copied to ~/.config/ffcss/themes, to pre-fill your themes with included ones. This directory currently has:
blurredfox
chameleons-beauty
frozenfox
fxcompact
lepton
materialfox
modoki
I think the library you are talking about would be this https://firefoxcss-store.github.io/
I'm guessing the theme you're referring to is uc.css.js.
by installing a script loader I just mean autoconfig files. the scripts on my repo require this loader, which is basically an autoconfig file that registers a component manifest and loads a javascript module, which in turn looks for scripts in a particular folder in the profile's chrome folder, and executes them with firefox's subscript loader component. the autoconfig parts need to get placed in the firefox binary folder, e.g. C:\Program Files\Mozilla Firefox\ or usr/lib/firefox/, whereas the module and manifest need to be placed in profile/chrome/utils/
Is it support upgrade process? And I think it's good to consider the profile location of https://github.com/filips123/FirefoxPWA. FirefoxPWA has its own profile location.