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!

@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

Appreciate the level-headed reply in this thread. There’s a lot of fingerpointing and hostility going on and I’d appreciate it if people would make less assumptions / jumps to attack people. I’m not sure if you or anyone else can confirm, but I agree with ernest that federation of mod actions was working once before. Without knowing exactly why it stopped, it’s hard to say what is going on.

For instance, I just coordinated with the admins of startrek.website as their latest maintenance started blocking user agents with curl in it, which is what kbin sends, meaning all kbin instances stopped being able to get images from their instance. It seems like this is true for multiple other lemmy instances. I didn’t follow up with any other admins at the moment, but I think from that, and the fact that back when I originally signed up people would constantly complain kbin federation was broken when it was lemmy.ml that was blocking kbin, it’s not a good idea to jump to assumptions on why something isn’t working.

Not just on the roadmap, already in :) (fingers crossed no bugs, no promises ><) example

This is anecdotal, but I don’t experience these log outs on fedia (I have to relog like once every few days but that doesn’t bother me, I assumed it was cookie expiry but maybe it has to do with server restarts or something). So I can understand if it happens more often to kbin social users it might be some other way it’s set up like caching or something that others might not be running. Then again, without version info, it makes it a bit tough to debug so this might not be helpful, fedia could be running some random sha atm which might be the reason.

You might’ve already seen this, but just in case other people missed it since not everyone may follow ernest or check the microblog tab, he listed his current priorities here https://kbin.social/m/kbinMeta/p/1002621/Hi-in-this-and-probably-the-next-week-I-will so hopefully people won’t have to deal with this too much longer 🤞

He did say it would be “federated this week” but in the next comment in that issue he made he said that changed “but it turns out it’s not easy, and I wouldn’t want to make such a big change hastily”. I don’t think anything has happened since. I definitely almost never see any reduces over here on a different kbin, so I think it’s still the same. There is still some discussion in that issue, someone just posted they have a PoC of doing it in a fork for instance.

There’s some relevant discussion here and in the thread linked by ernest in that post here. I don’t want to give any wrong information, but I don’t think activitypub has a spec for downvotes/reduces/dislikes, just likes and shares (boosting). So on mastodon dislikes definitely aren’t federated. I believe for lemmy, they federate between lemmy instances that have them enabled, but for kbin they are local to your instance.

I attended a talk in 2019 by Sir Tim Berners-Lee on Solid, which sort of seems related to what you are getting at. The idea being that you own your data/identity, and can decide to share it with third parties. It goes over things like files, but I believe login identities were also meant to be part of it, I see when I scroll down:

authenticated by a decentralized extension of OpenID Connect

I’ve been wondering recently, especially with Pixelfed adding login with Mastodon recently, if anyone has heard or experienced anything with that project. But considering I haven’t seen it spoken about or implemented since then, I’m not sure I should be hopeful

Just a note that the original team moved to PrivacyGuides. I didn’t do much reading into the entire ordeal as it seems like a sort of each side has a story ( here’s privacyguides ), but you can see on the site you linked it seems to be a bunch of ads and crypto now.