Extended Scripts for Tildes Alpha
So, after a rather clunky script to open comment's link in a new tab with the left click, I got inspired by the idea of @kalebo and wrote also a script to quickly jump to new comments in a topic....
So, after a rather clunky script to open comment's link in a new tab with the left click, I got inspired by the idea of @kalebo and wrote also a script to quickly jump to new comments in a topic.
I thought about writing a dedicated script but felt like it was going to become overly complicated for a user to import different script.
- The script itself is here: https://gist.github.com/theCrius/04dc86bea0ed0f1cbec7e57f1aaff9aa
- I wrote it with tampermonkey in mind: http://tampermonkey.net/
Please read further as tampermonkey has issues with custom styles. - And here is a simple tutorial on how to load script in tampermonkey: https://imgur.com/a/pY51wn2
These script are all meant to give the community some QoL while lightening the pressure on @deimos so he can work without too much stress from all the requests. As soon as the feature are implemented you should get rid of those script that in some parts felt like bad hacks to me that I was writing it.
I know the button to scroll to new messages is in a quite bad position (top center of your browser page) but I couldn't bear to deal with tampermonkey issue and its GM_AddStyle meta not working properly so I had to use the basic CSS provided by spectre already loaded in tildes.net.
If someone knows how to figure out that goddamn meta, let me know.
========= UPDATE ============
Edit: So apparently tampermonkey has issues with styles that are not yet fixed and firefox has some issue in general with script that inject stuff in the page (understandably).
For tampermonkey the solution is simple. Use violentmonkey instead. you can just copy the script and it will work.
For Firefox it's a little more dirty unfortunately but I cannot find other solutions. You need to open the internal URL about:config
. Then search security.csp.enable
and double click to disable it. After this the script will work.
Firefox has a very strict policy and the only real solution would be to write an extension and I don't think it's worth the effort in the current state of development.
For full description of what that policy does, check the official doc from mozilla: https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP#Threats