requestes are blocked for logged users about antispam

[ozh]

I disagree. As an admin, how am I supposed to know that a page I'm reading belongs to a site that is blacklisted? As an admin, how can I know that that site I added some time ago is now hacked and delivering malware?

[srescio]

If that's the case, the frontend could check if the page is blacklisted then prompt the user if the link match and ask if he wants to submit anyway, and by the way you were the one that asked to open this issue after I tweeted about it, closing without goign deeper into the matter is not really a constructive way to handle things, as of now there is no way to handle how the blocking works, bitly for example will give a warning page and ask the user if wants to proceed anyway to the resources, such page could be removed in the future when the source of the link is not listed as malicious anymore, but going as far with a data destructive operation that invalidate links is not a smart way to address the problem.
There are also stats attached to each link, meaning those would be lost too, but short dead link would still remain on the internet leading to dead pages
https://twitter.com/srescio/statuses/500660132200845312

[ozh]

I asked you open the issue because upon reading that tweet, it seemed like a good idea to me. After giving it some serious thinking, I changed my mind. Conclusion: as expected Twitter is an immediate medium not suited for support requests. Sorry if that upsets you.

The beauty and simplicity of the plugin API and YOURLS plugin is that you can easily expand on existing features and modify a plugin or create your own. If that helps, see wiki page Possible With A Plugin

The behaviour you describe (display a warning on redirection) will be easily doable with the next DB schema in YOURLS 2.0, see the Roadmap. No ETA, probably next year.