Hmm, according to another user it still appears to work, so it doesn't seem like the issue has to do with an Instagram update (thankfully!). Did you by any chance log out of instagram? It only works when you're logged in.

If not, can you contact me through one of the contact links in the addon's description? Matrix or discord would be ideal as it might require a bit of back and forth to find out what the issue is (but if not email/github/reddit is fine too). The reason I ask is that unfortunately there's no way to have a discussion over the firefox addons review page, so I can't really help troubleshoot the issue here.

Sorry you're having this issue, and hope we can get this fixed! :)

Sorry, there's currently no way to add manual rules. This is something I'd really like to add in the future (see https://github.com/qsniyg/maxurl/issues/41), but currently there are a few technical problems with implementing this for the moment (see the linked issue for a bit more detail on why).

If you want to request a new site to be added to the script, feel free to use any of the contact links listed at the bottom of the script's description, whichever you're most comfortable with. I'm more than happy to add any new website to the script, and if I'm online, I usually add them within minutes of being notified :)

If you'd rather add it to the script yourself (note that this will require sideloading the addon), I've written a bit of a guide here: https://github.com/qsniyg/maxurl/blob/master/CONTRIBUTING.md#websiterule-contributions. In your case, a rule like this should work: if (domain === "subdomain.your-website.com") return src.replace(/(\/[0-9]+-)small(\.[^/.]+)(?:[?#].*)?$/, "$1original$2");

By the way, while the github issue hasn't seen much activity for a while, this does not mean it's been forgotten or ignored, the script is already getting restructured in many areas, which will facilitate the implementation of this. It's just that it is pretty a massive project (currently requires rewriting >70,000 lines of source code - much of which will be automatically handled, but even that requires a very significant amount of work).

Glad to know it's helpful!!
I should note however that this does not replace using a reverse image search engine, but rather complements using one. It'll find larger versions stored within the website itself (either through URL patterns or API calls), which are sometimes larger than what reverse image search engines can find (unless they crawl a page that contains the original image), but if the original image uploaded on the site is smaller than what's available on another site (e.g. an image reuploaded to a blog), it won't be able find that version.

Does it work with the example image provided in the addon's description? (https://pbs.twimg.com/media/DlOC3mOWsAEi1ld.jpg , it should redirect to https://pbs.twimg.com/media/DlOC3mOWsAEi1ld.jpg?name=orig )

To be clear (as stated in the description), it doesn't perform a reverse image search, so it's not necessarily unlikely that the sites you checked didn't have a larger version available that was stored on the site itself. Since I'm not sure which sites you tested it on, I can't really give any specific help regarding the images you tested, sorry!

If however there is a larger version (for example, the link I posted above, an album cover on iTunes, non-original images on Twitter/Instagram/Flickr, etc.) and the script fails to find it, please let me know!

Since (I believe) firefox addons don't allow multiple replies, please feel free to contact me in any of the contact links listed in the addon's description (github, reddit, or discord). I'll try my best to help! :)

Thanks for letting me know! 0.13.8 should be much faster for redirects now, as it's done on the extension side, rather than the content script :) The delay isn't entirely gone, as it still needs to perform a HEAD/GET request to ensure the larger image exists, but the userscript's overhead shouldn't be relevant for redirects now.

There's still more work to be done performance-wise, but I hope to be able to address some parts of them soon (others will require a rewrite of currently >55,000 lines of code, so, they will probably come a little less soon haha). I've tracked the issue here: https://github.com/qsniyg/maxurl/issues/294

Let me know if you have any other problems :)