On the other hand, if people really wanted to contribute, there's plenty of open issues on Codeberg that are unadressed. I agree that it would be better to announce plans in advance rather than surprise drop them, but I doubt there would be more contributions from the community.
I assume ownership requests need to be manually approved by ernest, right? I've tried applying to some (not ernest-managed ones) weeks ago because of spam on them and nothing happened yet.
The project definitely accepts contributions, the mbin devs have contributed to kbin before and a few weeks ago a minor code change was committed and merged by someone other than ernest.
As I understand it, the issue is that people with merge permissions other than ernest are only allowed to merge their own pull requests, not those of third parties, which require a review from ernest.
(At least that's what I've seen explained before, though I haven't seen any proof of it so I don't fully know if it's real.)
This means a majority of contributors can't get their pull requests merged when ernest is gone. Which is why they went and made mbin when he was gone for months last time.
Ernest hasn't abandoned kbin this time, he did post an update last week.
Today, I'm going for a minor procedure at the hospital, and I won't be available for the next 2-4 days. When I return, I'll push all the corrections and fixes I've been working on and present plans for the near future.
Him not being back yet probably means the hospital procedure didn't go as smoothly as expected, but he's not gone on purpose.
They both federate and they both look the same I think.
However, Mastodon search works by tags iirc. And kbin/lemmy users tend to not use tags. So discoverability is low.
The Microblog section is supposed to add the magazine's tags to your posts there, though I don't know if it currently does. I remember reading issues about it not being the case, but those were rather old, so not sure about the current status.
I think it would be great if we could change the default sort. Would love to sort by new by default.
If there's not already a functionality like that hidden somewhere (checked in both settings menus), I'll put it on my list of stuff I want to implement via userscripts.
Teardown isn't working for me, tried multiple devices and turned my custom styling off.
After teardown this is how the site looks like to me. Also, it seems you need to remove the mores on teardown too. The more issue is now fixed when the mod is active, but appears again after teardown.
Under the post there's a "more" button behind which you can find a "report" option. I assume this goes to the moderators of the magazine, but not entirely sure.
In the site's footer, there's a Contact link if you need to report something to the instance owner directly.
And of course you can just message or otherwise contact your instance's owner, in this case Ernest. There's a Send Message button in the sidebar when viewing profiles.
For me, the culprit is the collapsible comments mod (or the standalone script if you're using that one).
edit: The root cause seems to be lines 182 to 190. But the actual troublemaker appears to be on kbin's side, not KES. When the mod's main function finishes, the comment still only has only one .more element like when it began.
I've disabled all other mods and userscripts, so it's not one of those. Also just tried to disable KES (and even the monkey) entirely, running the script from the console instead. No change either, it's still happening.
The code fragment in question copies the comment into a new children container. I'm thinking this probably makes some part of kbin confused, leading to the issues we're seeing.
It might be best to just include the userstyle I'm using in the CSS added by the mod.
This is the code between lines 182 and 190, removing which prevents the issue:
let children = previousComment.querySelector('.children');
if (!children) {
// If not, create one
children = document.createElement('div');
children.className = 'children';
previousComment.appendChild(children);
}
// Insert comment into children container
children.prepend(comment);
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
Clicking the bar once scrolls me down a bit but otherwise does absolutely nothing.
Clicking the bar again turns the arrow upwards and spawns a new bar above the existing one.
Clicking the upper bar repeats step 1.
Clicking the upper bar again turns the arrow upwards but doesn't spawn another bar, nor does it do anything else.
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.