this post was submitted on 12 Jul 2023
188 points (100.0% liked)

/kbin meta

6 readers
1 users here now

Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign

founded 2 years ago
 

A couple of weeks ago, @shazbot made this post about a project that they were working on. Since then, @shazbot, @ori, @minnieo and I have been hard at work, and we are excited to finally announce the official release of kbin Enhancement Suite (KES)!

kbin has seen an explosion of user-made add-ons, but keeping track of them in one place, letting them share settings with one another, and toggling them on and off can be a challenge. KES is an expandable add-on manager that aims to rectify this by providing a unified interface and framework for script makers to collaborate, and letting you use them all in one place.

KES brings together userscripts from the community, with a built-in settings menu that lets you tailor your experience to your liking. It also offers a flexible framework that empowers script authors to effortlessly integrate scripts into KES and set up custom input fields with no additional code.

KES gives you a single window onto a collection of enhancements that is growing by the day. And those features can be added to by you!

The KES settings menu

What the feed looks like with everything enabled

The comments with everything turned on

Features

We’ve focused on making customizing your kbin experience as easy as possible, whether you are on mobile or desktop. After we sort out the bug reports from this release, we plan on adding many more features! Here’s what we have so far:

  • Collapsible comments with nesting (by @artillect)
  • Use slash commands to add emoticons in text areas (by @minnieo)
  • Add syntax highlighting (with customizable themes) to code blocks (by @ori)
  • Show instance names next to non-local users and communities (by @artillect)
  • Add a link to message users on your instance next to their usernames (by @shazbot)
  • Hide upvote/downvote buttons and reputation (by @artillect)
  • Show more detailed timestamps on threads and comments (by @shazbot)
  • Hide thumbnails on threads (by @shazbot)
  • Add link to subscribed magazines to the navbar (by @shazbot)
  • Replace or hide the kbin logo in the navbar (by @shazbot)
  • Add “OP” label next to thread author’s username in comments (by @shazbot)
  • Convert navigation links on profile pages into a dropdown (by @shazbot)

Each of these can be toggled in the settings menu, and some of them have additional configuration options, such as setting custom labels, colors, etc.

New features are added on a rolling basis and the menu pages will update on the fly to reflect this new content.

Installation

Click here to install KES, and follow your userscript manager’s prompt to complete the installation.

If you don’t have a userscript management extension, you can install one of these, and then install KES using the link above:

Once KES is successfully installed, access the settings menu by clicking on the wrench icon located at the top-right corner next to your username. From there, you can enable the features you like, and customize your browsing experience.

More information

For bug reports and feature requests, visit our GitHub repository’s issues page. If you have any questions or need assistance, don’t hesitate to ask here or make a post on /m/enhancement!

Developers

If you are a userscript author, we’d love it if you could try porting your userscripts into KES, or try writing completely new ones for it! @shazbot has made it easy to integrate your scripts: you just need to add your script’s information to manifest.json, make a few small modifications to your script, add it all to the GitHub repository, and you’re good to go!

KES benefits:

  • Turnkey integration: a simple, declarative framework for dynamically adding features to the UI without touching the underlying code
  • Sharing of user-defined settings through script namespaces: access your script settings, and those from other scripts, through a well-defined object
  • Automatically responds to infinite scroll and page reload events
  • Attribution of script authors
  • Easily toggle scripts on/off

Explore KES’s documentation here to get started. If you have any questions, feel free to reach out here, on /m/enhancement, or at our GitHub repository.

you are viewing a single comment's thread
view the rest of the comments
[–] Noki@kbin.social 1 points 1 year ago (1 children)

I did the update but still have no wrench, but it’s late for me and I will try tomorrow from scratch.
I appreciate your work!

[–] shazbot@kbin.social 2 points 1 year ago (1 children)

Alright, if you have additional debug output from the dev tools console, that would be helpful. Unfortunately, we don't have easy access to an iOS test bench at the moment, but I'll try to read through the Userscripts documentation to see why it might behave differently.

[–] Noki@kbin.social 1 points 1 year ago (1 children)

Good news, it seems to work in Safari! But not when I add kbin as a PWA/add to Home Screen. But I think that is by design of Apple?

[–] shazbot@kbin.social 1 points 1 year ago (1 children)

Yes, I think there are additional sandboxing/security considerations when using a PWA, which may block pulling in additional script dependencies needed. If I understood you correctly, it works on Safari on a desktop, but when you add it as a mobile home screen app, it doesn't? Can you still use it on mobile some other way?

[–] Noki@kbin.social 1 points 1 year ago (1 children)

Correction: I’m using safari on iPad iOS on 16.5.1 and don’t have any Mac.

My desktops uses Windows 10 and Firefox and that works with out any problem.

[–] shazbot@kbin.social 1 points 1 year ago (1 children)

Ah, okay, so it works on mobile Safari, but with the caveat that you can't save it as a pseudo app to your home screen. This seems pretty good overall, we can mention that in the documentation. A few other users reported trying to create PWAs with some special apps (not Userscripts) and reported the same outcome. It's because they essentially blacklist extra dependencies.

Overall, I'd say this is a positive indication that it's working, yes? This is the outcome we were hoping for, as Userscripts closely resembles GreaseMonkey's API, so once we added support for the latter, it was all but guaranteed to work on the former.

[–] Noki@kbin.social 1 points 1 year ago

Yes your correct!

It will work for me, it would be nice if there is a workaround in the future but it is not immediately needed.