Pamasich

I know what they mean, because I have the same issue on my work pc (but not at home). I forgot it happens because the personal userstyle I'm using includes CSS to fix this issue entirely.

@speck get yourself Stylus if you don't have it already and try this CSS which works perfectly for me:

div.more:not(:nth-child(1 of .more)) {
    display: none;
}

Can't guarantee it works with kbin's built in custom CSS functionality, as that one seems to filter out some selectors (no logic behind which).

@shazbot
Basically, what happens without that CSS is that

1. Clicking the bar once scrolls me down a bit but otherwise does absolutely nothing.
2. Clicking the bar again turns the arrow upwards and spawns a new bar above the existing one.
3. Clicking the upper bar repeats step 1.
4. Clicking the upper bar again turns the arrow upwards but doesn't spawn another bar, nor does it do anything else.
5. Clicking the lower bar removes the upper one again and turns the arrow back downwards.

At no point is the comment ever expanded. When OP says it obscures text, that's just the default state where only x lines of the comment are shown and the bar covers the last line(s). The issue is the comment can't be expanded, so it keeps obscuring the text even when clicked as nothing actually moves.

Looking at the HTML source, I can see five instances of the bar existing at once on the same comment.

I tested just now to turn off my scripts one by one and KES was the culprit. Disabling it fixed the issue. I'll try checking which feature is causing it.

I think you're referring to the black bar below comments that are too long which can be clicked to expand the comment?

That has nothing to do with KES's collapsible comments feature as someone else brought up. It's a native kbin feature.

KES actually has a feature that addresses this by automatically clicking that bar, but it seems to only apply to thread bodies, not comments, currently. If you're interested in having it apply to comments too, try filing a new issue on Github requesting the feature. The mod in question is "Always expand post bodies" in the Threads category. This should be fairly easy to add.

I'm not sure what KES

Kbin Enhancement Suite. Inspired by the Reddit extension of the same name (RES).

It's a userscript that provides many opt-in atomic features with a shared api and settings interface.

Current features include:

• hiding various sidebar elements
• bringing up a list of subscribed magazines via hotkey
• displaying the instance next to usernames and magazines
• a mail icon next to usernames which starts a new message when clicked
• notifications easily accessible in the navbar
• softblocking magazines
• syntax highlighting
• fixing broken lemmy code blocks
• and various others

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:

• KES (Kbin Enhancement Suite) has a feature that brings up your subscriptions with a hotkey.
• 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.

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).

Once installed in your browser, open the extension by clicking on the icon next to your address bar. If it's not there, there's a puzzle piece button to open a list of all your extensions where you can click on it. I'm writing this from an Edge perspective, so for other browsers, especially Firefox, this might not be entirely accurate.

This opens up a menu where your current styles are listed and can be turned on/off (well, the list is empty for now of course), and there's buttons to "Manage" and "Find styles".
Above those buttons, there's a link to the current page. Click on the kbin.social part of that link.

This should open up the editor in a new window.
Just copy and paste the following code into that window.

div#content {
    > article {
        /* thread styling */
    }
    > blockquote, > blockquote + .comments > blockquote {
        /* microblog post styling */
        background-color: red;
    }
}

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.

So you should be able to just

div#content {
    > article {
        /* thread styling */
    }
    > blockquote {
        /* microblog post styling */
       background-color: red;
    }
}

You can also define the color in rgb rgb(255,0,0) or hsl (hsl(0,100%,50%)).

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

• Support for turbo mode

As I understand it, the message here is that any decently savvy user of Firefox turns off telemetry, so mozilla doesn't know of them using extensions. hence why they say 80% don't use them, people who do use them don't give them their usage data.

Kbin.social has just had some big issues recently and still hasn't fully recovered (which is why development is currently stalled), so it's absolutely possible you'll run into more issues currently than usual. Not sure if what you're experiencing there is part of that though.

I don't know which anime those are, but it's not only about advertising the manga,

Anime are made by a production committee, which consists of various companies that put money into it and expect something in return. The source material's publisher is just one of them, and they're the only ones interested in boosting the source material. But even they might be doing it for some other purpose, like the author's next work or a spinoff.