e569668

I don’t know of every instance of course, but from the general purpose ones the order of up-to-date from most to least at the time of posting would be something like: kbin.run, fedia.io, kbin.cafe, artemis.camp (specific API branch), kbin.social.

But there’s also other considerations. fedia has a double post/comment issue and a low amount of 500s. Artemis has been giving me a lot of 500s, can’t upvote anymore (just reloads the page), commenting doesn’t always federate. Many instance admins seem to have disappeared since 3 months ago. I’m not sure what life is like on instances I’m not actively using so there might be issues unknown to me.

Edit: the keys that I look for are localization / ui changes. “more” dropdown now has “more from domain” on updated instances. The UI for the sidebar is different, and most recently the footer is differently styled. There’s also the federation list of instances page in the footer now.

Yeah, Mastodon has separate block and mute functions.

Ah, good to know. I’ll have to look into it a bit more, but reading https://docs.joinmastodon.org/user/moderating/#block

If you and the blocked user are on the same server, the blocked user will not be able to view your posts on your profile while logged in.

It looks like the limitation that Pamasich and I sort of expected is there. Blocks are basically only possible at your own instance. If the user is on another instance, there’s no way to stop them in the fediverse. And that includes it going out to all other instances they federate with too.

I sort of just experienced how this would work if implemented, in a way. A kbin social user posted to a beehaw org magazine. I replied to it, but my post does not seem to have made it to kbin social. However, it’s on my instance, beehaw’s, lemmy one, etc, because my instance federates with all of those instances. That’s sort of what blocking would be like if the original page refused an incoming comment due to a block, all other instances would still accept it. It’s possible there’s something I’m missing as I’m not super knowledgable on activity pub or the fediverse, so I’ll try to learn more about it

does the fediverse actually support the kind of block that’s being asked for here?

Yea, that’s where I’m thinking the hangup on this might be. A block could be implemented, but it’d come with the caveat of that all it’s doing is giving you the idea they aren’t continuing to engage with you on your instance. On their instance, and any instance that federates with them, they and others will continue to see the replies.

Personally, I would like to see block renamed to mute to be more accurate and a block from replying added with the note about the drawbacks of them being able to tell you blocked them and their posts still going out everywhere else. That at least empowers the user to make the decision themselves on what they’re most ok with. My reasoning is: changing the UI for, let’s say an aggressor, gives them a reason to retaliate. To me, either blocking method is a lose-lose; either it doesn’t stop engagement which some users clearly want it to, or it makes it obvious someone is being blocked which start aggressors down the retaliation path. That’s kind of why I’d want users to make their own risk assessment on actions.

Anyways, that’s all very unlikely to happen. Most of all I’d like the bug about notifications fixed because that is clearly not working as intended.

I posted in https://kbin.social/m/kbinMeta/t/509976 as well but just to make sure you see it, ernest was pinged so hopefully this will be fixed when he sees it

The good news is this was fixed in latest https://codeberg.org/Kbin/kbin-core/issues/1019 the bad news is it hasn’t made it to kbin.social yet so hopefully whenever this instance is updated it will be fixed

Peeps pinged ernest in matrix so hopefully he can take care of this when he gets the chance. Thanks (to squiblet as well) for bringing it up!

@CarlsIII It’s looking to work for me at least opening up kbin.social in a private window and enabling it. Make sure you’re enabling the setting under the “Threads” header and not just the “Microblog” one, assuming you mean for threads

@harmonea you may be blocking a domain, which causes a bug detailed here. tl;dr blocking any domain on kbin.social right now hides any non-link entries and comments on them. removing them all fixes it, it’s fixed in latest which hopefully the main site gets soon

@harmonea threads like this one https://kbin.social/m/Otomegames/t/480285/I-played-Butterfly-s-Poison-Blood-Chains ? Are you unable to see it, or a different one?

One thing I’m trying to keep an eye on is sup. Not much information at all besides a snippet of 1 to 1 encrypted messaging for activitypub, but the tidbit of working with any fediverse account is interesting. Potentially that could help deal with the different fediverse implementations of messaging. Of course, like I said, this is just me making up assumptions, it could not work the way I envision it at all. The creator just posted something 5d ago about it with “soon” though, so I’m hoping to read more about it

The short answer is no but the longer answer for what happens in each situation was detailed here: https://codeberg.org/Kbin/kbin-core/issues/1051

lemmy -> kbin = pretends to send but doesn’t

I’m able to see that post, do you see it in private browsing / when logged out? If so, you might be blocking domains on kbin.social and removing them would make it appear again. That’s been fixed in latest which hopefully kbin.social users should get soon, but wasn’t affecting other instances I had checked so you should be fine to do so on artemis

I don’t want to give false information, but on fedia the majority of 500 pages seemed to stem from the image media cache causing issues (our instance admin detailed the issue here). People were able to mitigate it by disabling images everywhere they could, but one place they can’t be disabled is the user avatars on the notification page. I could be wrong, but it’s my belief it’s those images causing the 500s, and that pushed me to add https://codeberg.org/Kbin/kbin-core/issues/1039 in hopes that if it was possible to disable them the 500s would stop. All this could be wrong though, maybe it’s something else like deleted messages or anything else, or maybe there’s a better way to solve issues with cached images

he’s eventually going to make sure abandoned instances have admins

I think he meant magazines on kbin.social in this context. I don’t think he has any way to control another instance and change who runs it, besides a kindly worded letter.

I do try to keep track of kbin instances and how up to date they are and their admins, but I can’t really advertise in their place. One thing I’ve kind of been thinking about is it’d be nice if nodeinfo had information next to current user count of like: desired user count, max user count. Otherwise you have no idea what an instance admin is hoping for, whether it’s just their personal instance or they’re willing to support tens of thousands of users. Without that I don’t want to send people to x instance and suddenly the admin being in for a surprise. But I just looked up nodeinfo and it looks like there’s plenty of worms in that can about it being too complex already, so maybe I’ll avoid opening my mouth about it… for now.

It looks like all the spam I’ve seen are from newly registered accounts. Perhaps this is something you’ve already considered, but would shutting off registration on kbin.social and pointing people to other instances until things are more manageable help?

In hindsight I remember why I filter newest to a timespan, so wanted to make note of it. Right now:
https://fedia.io/m/[email protected]/microblog/newest 500s for me but
https://fedia.io/m/[email protected]/microblog/newest/1w is able to load. so cutting off some of the older posts helps me run into less 500 issues, and I generally don’t care too much about old posts unless I’m searching for something. that might be a fedia specific thing though, not sure how 500s are on other instances

You filed the issue on it! xD

I remember this happening before so it might be the same thing, auto media preview basically: https://kbin.social/m/kbinMeta/t/77143

https://codeberg.org/Kbin/kbin-core/issues/446

I’m not sure if this is a good suggestion, are you able to delete it via moderation as you’re the magazine owner? Someone mentioned having issues deleting their own posts but still could via moderation recently, but I’m not actually sure what that difference means as I haven’t moderated any magazines myself.

Definitely, you’re right that new timeframe doesn’t matter, I meant to type hot all time xD I would expect that to potentially grab like whatever was boosted most in the past but then again the algorithm does tend to show newer things even under hot.

Yea the tag system might need a bit of work. It works great for some magazines, but for others not so much. For example m/help is supposed to be a magazine for kbin help but it pulls in everything under #help which can be anything in the fediverse. I did see someone suggest a way for a magazine to remove it defaulting to using the tag of its name, which doesn’t seem like a bad idea to me

Interesting, I’ve heard people say the same before. I do always sort by newest myself, but I sub to a bunch of magazines and also, say, three mastodon accounts, and that page is basically just solely the mastodon posts, very rarely do I see microblog posts in lemmy/kbin. I guess a filter of magazines vs users would be useful

Edit: Also, is the default view all time for you? I could see that causing a problem as well if it’s hot / all time. I mainly have three bookmarks: /hot/12h, /sub/newest/24h, /sub/microblog/newest/1d. Getting all results for all of time by default seemed a bit weird to me, especially for microblog posts