Amit Chaudhary

@alfydavy I also got the same error when using **127.0.0.1:9966** or **0.0.0.0:9966**. But it worked for **localhost:9966.** Workaround for now.

This makes sense, but there is a performance overhead since the extension is run on all sites, even those where there is no code. ``` "matches": [""] ``` I prefer...

I did some research. We could do something like this: http://stackoverflow.com/questions/16759345/getelementsbytagname-for-two-tags-at-once Specifically **document.getElementsByTagName('pre').concat(document.getElementsByTagName('code'))** or **querySelector**

@willbiddy I closed your PR since there are merge conflicts now as I merged the PR for the history table. Can you update your fork with new changes from source...

+2

@lukefernandez Thank you. Can you test this in your fork for a few days and let me if this works correctly? I reviewed old commits and saw that I had...

@troncosojr Hi, that sounds weird. You don't need a premium account for this to work. Can you elaborate why you think this has something to do with IFTTT?

* [x] ACL: https://aclanthology.org/2021.emnlp-main.3/

@vict0rsch Thanks a lot for implementing this so quickly. It works perfectly.

@vict0rsch Btw, the chrome-webstore link to the extension on the GitHub repo has an issue.  It redirects to this auth error right now.  You will have to remove...