Topic: [Plugin] umami : e621 Browser Extension | 2025/04/06

Posted under e621 Tools and Applications

justsomeman said:
I've been having an issue since this got banned and I've installed the manual update:

On my main posts page I only have two columns and the Blacklist isn't present/functionally there and the Blacklist itself doesn't function - but only on the main posts page. If I go into a post the Blacklist functions as normal.

Any suggestions?

What do you mean by main posts page? Is it the global blacklists or is it custom blacklists?
I don't use a blacklist so I put something in there just now and when I refreshed the new posts page some posts got removed properly and the slideshow didn't view them.
only thing I can think of is if you weren't signed in on that page and refreshing would fix it...
e621 did update their UI a few days ago so maybe that broke something in some edge case?

appreciate all you've done brother, making this site much more usable. do you plan to release any updates from now on though github?
also, can anyone else not favorite through the slideshow anymore after the ui update?

something2say said:
appreciate all you've done brother, making this site much more usable. do you plan to release any updates from now on though github?
also, can anyone else not favorite through the slideshow anymore after the ui update?

So e6's UI updated twice in one month..... The one yesterday broke how the extension detected if you were logged in.
It may take a hot minute to push it to the release build.
So in the mean time if you want to fix it yourself

  • in either bundle.js or util.js in the extension find the line loggedIn: () => $("#nav-account").length > 0,
  • replace it with loggedIn: () => $(".sign-in").length == 0,

This does make it true by default if the class doesn't exist. Which isn't good. but for right now its a quick dirty fix.

Updated

reapersans2 said:
So e6's UI updated twice in one month..... The one yesterday broke how the extension detected if you were logged in.
It may take a hot minute to push it to the release build.
So in the mean time if you want to fix it yourself

  • in either bundle.js or util.js in the extension find the line loggedIn: () => $("#nav-account").length > 0,
  • replace it with loggedIn: () => $(".sign-in").length == 0,

This does make it true by default if the class doesn't exist. Which isn't good. but for right now its a quick dirty fix.

took me a bit, but changing bundle.js fixed that perfectly
you're a legend bro ty

I added a new pull request to the main branch with a fix which might take a while since wolfgang is probably doing a rewrite of the code.

Until then, I have made my own release build with a bunch of new bugfixes and a new feature in the config supporting full resolution images.
The changelog along with instructions to install is at https://github.com/Temmie-Flakes/umami/releases/latest if anyone wants it.

reapersans2 said:
since wolfgang is probably doing a rewrite of the code.

... This is very generous of you to assume xD

I have merged your PR into staging, and there is a build available on the action for people that want to test it.

If nothing obvious crops up in the next couple days I will upload it to firefox's addon site.

Updated

Welp. The day is upon us. The wretched manifest v3 deprecation. darn you google.

I merged my manifest v3 test from a while ago into my latest commit and it just kinda works? for the most part atleast.
Pool downloads are bugged. But 90% of the functionality is still there with minimal code changes.
You can find the release of this VERY beta port here
download at your own risk! It is very much unready for deployment and only here for the people who NEED it -aka:me
- It is very untested but really anything beats the way E6 handles post navigation.

- Side note, if anyone is in a situation where they can use it, I recommend trying Hydrus for downloading large amounts of media files for personal archival. With the way recent legislation and moderation is, it may help. Plus it comes with a slideshow viewer of its own which is nice.

Updated

Looks like blacklisting on infinite scrolling broke again, at least on the Firefox store version. I tried to see if the github version would fix it but FF's yelling at me about it being unsigned