|Holly c4a4d5d01b||1 week ago|
|LICENSE||1 year ago|
|README.md||1 week ago|
|index.html||2 weeks ago|
|remote_instance_actions.user.js||2 weeks ago|
|ria.png||1 week ago|
|scripts.js||1 year ago|
|style.css||1 year ago|
Quickly suspend or silence remote instances from the Mastodon frontend
A userscript to make blocking remote instances on Mastodon a less tedious and time-consuming task.
First, install Tampermonkey. Then, visit the installation website.
It fills in the
@match directives for whatever instances are relevant to the user, using GET parameters so Tampermonkey's update functionality will continue to work.
For the same reason as the last question. That's how the
@match directives are filled in with the GET parameters. The file has to have the .user.js extension so that Tampermonkey will prompt the user to install it, which means I had to go into the PHP configuration files and allow it to execute .js files as PHP. It's a little cursed but it does work.
@run-at context-menuheader only works in Chrome based browsers. The context menu item appears in Firefox but doesn't do anything. Find a workaraound
@run-at context-menuactually does exist in Firefox now, but there's a bizarre CSP enforcement bug that causes Firefox issues. Details on the installation page