Kbin Userstyles and Userscripts

With the work you and everyone else is doing I'm cautiously hopefull about the future of the verse. Not to mention the supportive vibes.

Yurp, I grabbed Fennec enabled tampermonkey and got the script.

Yes exactly

How do you install Tampermonkey for Android FF? Every time I tried it just told me it wasn't compatible.

There are a few alternatives, but I'm personally using an extension called Userscripts.

Essentially, you install it from the app store, launch it, and then choose a folder in the Files app where you will store the scripts. Any folder will do, but I think a good idea is to choose a folder in e.g. iCloud so that it's easier to manage from a computer if needed.

After that is set up, you need to go to the Greasy fork link and click install. You will probably just be presented a bunch of code now. After carefully reading through the ~1600 lines of code (kidding, somewhat) you can tap on the extension settings on the left in the toolbar (the puzzle piece icon) and tap on "Userscripts". Sometimes, the toolbar button defaults to opening the reader for some benign reason, whereas you need to tap it again to get to the menu.

You might be prompted to give access to reading the website, and after all that is done there should be a button saying something like "Userscript detected, tap to install". Tap it, follow the on-screen instructions and you should be good to go.

In the future, the script should update automatically by tapping on the puzzle icon again -> Userscripts -> tap on the cloud with a downwards arrow. You might need to be on kbin.socal to do that; I'm not entirely sure, to be honest.

This one is for installing an other script "Kbin Improved Collapsible Comments" (recommended!) on Firefox for Android:
YouTube Short - "Firefox for Android: user scripts"

It works the same for the Kbin Usability Pack.

Yeah, I will definitely look into making something for compact mode later. It will most likely be after the new Kbin version has been released since at the moment I'm essentially managing two different stylesheets in order to be backward compatible with the current version.

Same issue on Firefox for Android with Tampermonkey. Can't use the hamburger menu, it does nothing with this script installed.

Yeah I noticed. I didn’t get a time to deploy a fix yesterday, but I’ll have one out in a moment. Sorry!

Edit: This should be fixed in 0.3.4

Userscripts chrome extension?

Thanks for the feedback! I actually released an update 0.3.6 earlier today that addressed some issues with compact mode and the alternative mobile UI. Especially the thumbnails should look a lot better now.

Regarding the thumbnails, they didn't actually use more vertical space than in the standard UI as they merely used all the available vertical space. The issue was that since the whole element is larger because of the thicker footer, the background got stretched out to fill out the additional space, resulting in the portrait format you are talking about. That should however be fixed now, but if you prefer the smaller standard UI, that sadly won't help you in this case. I guess that's what makes it an experimental UI :P

Regarding the comment box, I agree completely and before I repacked my scripts into the KUP bundle I did actually have a fix for that. I never included it in KUP though since that feature is already included in the excellent Kbin Enhancement Script plus a number of other improvements. KUP is fully compatible with KES so I felt I should rather focus on bringing new improvements than reimplementing things that others have already solved.

If I get some time over, I might add that however, in order to make KUP more of a complete single package.

It's not in Tampermokey nor do you need to fiddle with the code. It adds a section to the settings page for the script's various toggles. If you're on mobile, click on the menu icon, then the settings (gear) icon, then scroll down to see the script settings. You may need to toggle open the settings panel.

https://i.imgur.com/wzhRJgK.png

Yeah, it seems to be a bug that slipped through when I was porting it to the current Kbin version. While most fixes will probably be done for the next Kbin version, I'm currently doing some refactoring work anyway, so I'll see if I can get a patch out later.