tabliss VS ao3-enhancements

You can use this page to report issues with Tabliss.

lf you want to report the issue you can do so at https://github.com/joelshepherd/tabliss/issues

Licence: https://github.com/joelshepherd/tabliss/blob/main/LICENSE.txt - I am not affiliated with tabliss.io

The problem has been reported to "Issues" on the GitHub repo of the plugin. As the say, the recent update version 2.4.0 is to blame and there is already a fix that has been released. But...

LibreWolf sets your timezone to UTC to prevent fingerprinting. Take a look at Tabliss, you can change the default timezone in it's settings

AO3 Enhancements adds this (among other things).

I'm shit at coding so everything is relatively entry level. Most give you a user interface added directly to AO3 and for the ones that do require modifying the code the creator left baked in directions on how to modify it. It's easiest to use on desktop, but I got things to work on Android by following the directions here. I created my own list of extensions rather than using the one linked in the site so I could use AO3 Enhancements for the word count features/read time estimates. If you use apple you can probably do some general googling for "install tampermonkey iOS". Keep in mind that settings aren't saved across multiple devices, so if you switch between multiple you have to individually update each device every time you block a tag or flag something as read.

AO3 Enhancements. Firefox version. Chrome version.

You could try using a script (ao3 crossover savior) or the browser add-on AO3 enhancements. So far I don't know of anything on the site itself that would help you, but maybe someone else knows more.

use https://addons.mozilla.org/en-US/firefox/addon/ao3-enhancements/ to filter out tags and not having to worry about them ever again.

This is to fix AO3 https://github.com/jsmnbom/ao3-enhancements/

That's almost certainly the culprit then. See the issue here on github. The problem is that TrackWorks feature adds every fic you see to your History. So if you disable TrackWorks, you can probably continue using AO3 Enhancements without running into that bug.

AO3 Enhancements extension for Chrome (or here for Firefox) does this. I use it to filter out multi-fandom crossovers. You can set the limit to any number you want. Be sure to turn off all options under "track works" because that one is buggy and will flood your history with fanfics you've never even read.

I use AO3 Enhancements. It's a browser extension for Google Chrome and Firefox and has a bunch of cool features besides the blocking.

The beta version 0.4.0-beta.6 (let's not talk about beta 1-5 :P) can be found over on the AO3 Enhancements GitHub releases page. Guides on how to install them are similarly found on the AO3 Enhancements wiki. (note: very simple on Firefox, less simple but still very quick on Chrome)