Pamasich

joined 1 year ago
[–] Pamasich@kbin.social 6 points 8 months ago
  • Sankarea
  • Gakkougurashi
  • Highschool of the Dead
  • Zom100
[–] Pamasich@kbin.social 2 points 8 months ago

I know of in Lemmy (kbin might be different), is that you can put full urls in the search field and it will pull up that post on your local instance (also works for comments).

Oh wow that actually works on kbin, at least for posts, haven't tested comments. I put your link in kbin's search and it gave me the correct thread on kbin.

[–] Pamasich@kbin.social 3 points 8 months ago (2 children)

One thing I hate about the fediverse right now is the apparent inability to link to something irrespective of instance.

Despite you giving me a link, I still need to look up the post manually myself if I want to view it on kbin instead of ani.social. I hope that changes some day in the future.

[–] Pamasich@kbin.social 2 points 8 months ago* (last edited 8 months ago) (4 children)

This ED is definitely my favorite of the season.

[–] Pamasich@kbin.social 4 points 8 months ago

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.

[–] Pamasich@kbin.social 6 points 8 months ago

Probably american-based like the other commenter says. The American left is the global center-right iirc.

[–] Pamasich@kbin.social 3 points 9 months ago

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.

[–] Pamasich@kbin.social 2 points 9 months ago

This works for me now.

[–] Pamasich@kbin.social 2 points 9 months ago (3 children)

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.

[–] Pamasich@kbin.social 3 points 9 months ago* (last edited 9 months ago) (1 children)
  • 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.
[–] Pamasich@kbin.social 2 points 9 months ago (1 children)

Great to hear the CSS works on mobile too!

I think you pressed the wrong button when you tried to upvote my comment, I can see a downvote there from you.

[–] Pamasich@kbin.social 2 points 9 months ago* (last edited 9 months ago) (7 children)

@shazbot @speck

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

view more: ‹ prev next ›