Provide 'exclude' list to avoid 404's
planned
m
manicmoose
Hi,
I've noticed that on non-Mastodon sites, this plugin creates calls to 2 API links that don't exist on every page refresh and thus generates 404's (which can result in being blocked on some sites).
eg.
GET /api/v1/instance HTTP/1.1"
GET /api/v1/timelines/public?local=true HTTP/1.1"
These get called everywhere.
If they could either be turned off completely (which I presume breaks Graze?) or allow a list of domains where Graze is either inactive/active then this could solve the problem.
Thanks.
Jared Zimmerman
planned
Jared Zimmerman
under review
Jared Zimmerman
Yeah, unfortunately due to the distributed nature of Mastodon and new instance opening all the time a static list of instances is not a viable way to fix this...
What site are you having issue with? possibly can investigate a fix. in the mean time, you can go into your browser Extension settings (not Graze's settings) and choose "active on click" for Graze, you lose the main value of "1-click actions" because you'll have to click the extension then refresh the page, but this would be a way to pick and choose what pages its active on.
m
manicmoose
Jared Zimmerman
No specific sites as yet. I have my own webservices and noticed they were logging 404's when I accessed them and that's how I found Graze doing this.
For my own website - that's available to anyone on the net - if I log 2 404's within 2 seconds from the same IP then the origin site goes on the naughty list and is blocked temporarily. Beats off a lot of Wordpress script kiddies, etc.
I can imagine that others probably do similar, so I'd rather not get blocked from them due to a browser extension.
m
manicmoose
Jared Zimmerman
hmmm....unfortunately 'active on click' is not an option for Firefox. :-(
Yes, the reason I thought an 'exclude' list would be best in the first place is for reasons you described - many new Mastodon instances popping up everywhere and disappearing almost as fast.
Jared Zimmerman
manicmoose I understand the goal, this just isn’t feasible with how extensions are required to be written by browser makers at this time.