* [Blacklist] Increase the size of the editor window
* Don't have the dialogue overflow horizontally
* Remove one min-content, looks better, same padding top to bottom
* Shrink blacklist in settings slightly. Much closer to height of dtext input now
---------
Co-authored-by: Earlopain <14981592+Earlopain@users.noreply.github.com>
The more or less unintrusive message has been there for a few months now.
Start forcing a name change when accessing through a browser, ignore api for now
The images removed/are in the process of removing compose v1.
This also pins to an actual version instead of always using latest. Seems like a smart thing to do.
https://github.com/actions/runner-images/issues/9557
This has caused trouble on multiple occasions. Right now, a BUR resulted in about 2 million jobs being queued.
1 mil on approve, 1 mil to switch them all back.
Everything is already scoped to the approver. Switching to the creator doesn't make much sense here.
In addition, this sent the success message 5 times because the rename happened at the wrong place
I tested this since it looked weird to me and arrived at the conclusion that this always has been this way.
That conclusion was wrong, I probably looked at something cached.
This previously had whitespace that I unintentionally removed. This also has the unintentional sideeffect
of not breaking up individual prev/scale/next links which I see as an improvement.
Remove a margin override for the first entry, this wasn't properly centered for some reason.
Still not quite there but much better now.
* Address the baraag/mastodon icon situation
* Add a blogspot.com icon
* Add a yiff.life icon
* Add a nijie.info icon
* Add an f-list.net icon
* Fix the issue with the AO3 icon
* Add a couple of aliases for existing icons
* Misnamed AO3 file
* Add a wordpress.com icon
* Add a wikimedia.org icon
* Add a furbooru.org icon
* Add an alias to the Patreon CDN
* Remove the t.co - t.me alias
* Misnamed wikimedia.org file
* Add a fandom.com icon
* Add an exhentai.org alias
This doesn't have the same issue as mass updates, but
it doesn't hurt to change this away from tag_string_diff as well
Aliases/Implications still do this but considering this has been the case
for 4 years now I don't believe this to be a problem
