It's definitely not ideal at all currently. You've already found out how to do it currently, but I'd like to point you towards some alternatives that currently exist to make this easier until ernest adds something official.
Here's the userscripts I know of, each approaches the task a bit differently:
Improved Channel Select Menu adds your subscriptions and collections to the select channel menu. It's the one with the 3 dots and lines next to your username. This one is the only one that currently supports collections I think.
Floating Subs List adds a new (collapsible) sidebar to the left which contains your subscribed magazines.
Choose whichever sounds like more your thing, or try each and go with which works best for you.
If you're not familiar with userscripts: just get yourself either Greasemonkey, Tampermonkey, or Violentmonkey from your browser's extension/addon store, then head to the script's greasyfork page (I linked you to them above) and click the big green button. For KES it's a bit special but just as simple, just use this link, it should bring up an installation page. After installing KES, you're looking for a wrench next to the user button to access its options and turn the feature on.
I just noticed that, while kbin supports Lemmy-style spoilers, it seems like actual spoilers federated from Lemmy don't appear as spoilers on kbin yet. Are you aware of that?
The images I'm using here probably won't work as embeds, but opening them as links should work.
Depending on if you use Firefox or a Chromium-based browser (Chrome, Edge, and almost all the others), get yourself the Stylus extension (chromium) or addon (firefox).
Give the style a name to the left and hit the yellow "Save" button. The site will update in real time, you shouldn't even need to reload it for the changes to take effect after saving. In fact, after saving it once, you don't even have to keep saving it after every change in my experience.
I've changed the above code a bit to also cover the replies to posts, that's what the .comments stuff is about.
This will give you a very red background. I just chose this for the example to make the change obvious to see at a glance. You can replace the red with another color name, or an RGB or HSL value for a more granular choice.
I recommend using HSL if you want to tweak the color later without having to open up a color picker. You just choose a base color, how saturated it should be, and how light you want it. And optionally the transparency.
The HSL equivalent for red is hsl(0,100%,50%).
If you just want microblog posts to be a bit lighter or darker (depending on your theme) than threads, you can use hsla(0,0%,100%,0.15) (this makes them lighter, change the 100% to 0% for darker). Tweak the transparency (the last value) to change the intensity of the color change.
Besides the background color, you can also change other CSS properties. Just add additional lines in the pattern property: value;.
For example, you can set a border using border: 1px red solid;, which creates a red solid border of 1 pixel width.
I like to use this site as a reference myself for what properties exist and how they're used.
I think the color variation would help me better process what I’m looking at.
You can change the color yourself btw. The traditional method is to install the Stylus extension/addon, but I think kbin now lets you define your own styling in your profile settings, though I haven't tried it. (tried it now and this doesn't really seem possible there, has the same selector deletion issues as magazine css)
In the HTML code, microblog posts and threads are represented differently. Posts are blockquote, while threads are article. This makes it easy to restyle them via userstyles.
Thanks, this is the best implementation idea for this I've seen yet imo, will definitely be using this from now on.
I haven't found any bugs yet, but I'd like to request two future improvements:
Changing the order of magazines and collections
::: spoiler Details
I have like three collections and a ton of magazines, so having to scroll through all the magazines to reach the collections is a bit of a pain. It's still much easier than before this script, but it would be even better if I could move the collections above the magazines.
On the other hand, someone else might have the opposite situation and would prefer it the way it currently is, so unlike the other user I'm not asking you to just swap the order.
I think the ideal solution would be adding a setting somewhere to determine which comes first. So every user can tailor the functionality to their needs.
:::
Support for turbo mode
::: spoiler Details
Ernest added turbo as an optional mode in the past months (you can find it in the sidebar options). It turns the site into a single page experience, which means kbin.social links don't open the website anew entirely but rather replace the page content, including the changes your script makes. This cuts down on loading time, but it also causes scripts to break.
It would be great if the script were to support turbo mode eventually, especially if Ernest makes it the standard in the future (it is marked as experimental currently, so that's probably the eventual intention).
To do so, you'd have to attach a MutationListener to the body element like I did here. But that will run many times more than just on navigation, so you'd also have to ensure your code does support being run multiple times without breaking.
:::
Open source, non-corporate instances should be able to grow, and that growth will be stunted if most people who want to interact with the fediverse are deciding to go to corporate, profit-driven instances.
The issue is, how does defederating not promote leaving for Threads or instances that federate with Threads?
I think it's a good argument against Threads federating at all, but a poor one for defederating from Threads.
If Threads produces 95% of content in the fediverse, and your instance defederates from them, then your instance just doesn't have access to those 95% of content. Threads and its friends will be a lot more attractive then because it has 19x the content of what you have access to on your instance.
I think this will still lead to people leaving for the threads fediverse.
Also, I get the argument for Mastodon, but does /kbin actually have anything at all to fear here? Sure, the user numbers and content would be way higher than the rest of the fediverse. But Threads is a Twitter contender, not Reddit like /kbin and Lemmy. We will only see their content in the microblog tab.
Is the microblog tab actually that important to most people, that the instance could become dependent on Threads for dominating it? I honestly don't see it happen, I feel like this is an imported issue from microblogging platforms that's just repeated here despite being a non-issue for us.
I understood OP to be talking about mobile specifically.
And that's why I said Firefox or Kiwi. Both of those are mobile browsers (the latter is chromium) that support extensions, so you can just install your favorite monkey and stylus and add userscripts/userstyles the exact same way as on desktop.
Well, for the span tags, I haven't seen other tags being an issue. If you see a code block where the same issue occurs with other tags, tell me so I can update it.
If there is another Reddit exodus, for example, or if we get a surge due to the Threads thing, I feel like many will just turn back due to the UI alone.
I don't know if ernest's views changed since the last exodus, but iirc people joining the platform wasn't really his intention, it just happened. Kbin hasn't even had a proper full release yet, it's still beta software, so I don't think people bouncing off is that big an issue yet.
With the abandonment of Artemis (formerly kmoon), kbin is now only really usable by the mobile site.
That's the case for now, but app development is still happening with other projects:
ernest has mentioned intentions to revive his kbin app project
Hey @ernest, I noticed that the new comment markers are rather hard to see on some themes. They work perfectly on the Tokyo Night theme, but did you test them on others? This is how it looks for me using the Dark theme. I also tried the Light theme with the same issue.
edit: Forgot to mention, I did turn off all my userscripts and custom css.
Only monetized games have to pay. If they stop selling the game, they shouldn't be affected anymore.
Also
Does the Unity Runtime Fee apply to pirated copies of games?
We are happy to work with any developer who has been the victim of piracy so that they are not unfairly hurt by unwanted installs. (source)