Remember that the button at the top of the sidebar expands the options to disable federation.
Remember that the button at the top of the sidebar expands the options to disable federation.
Remember that the button at the top of the sidebar expands the options to disable federation.
when you say "disable federation" do you mean preventing our content (threads/comments/posts/etc by us as an individual) from being shared/seen on other instances? or do you mean that it prevents us from seeing federated content? or both?
At least from my quick test right now, it limits your home page to posts within kbin.social. Not sure if it works the other way around, too, preventing your posts from going out into the fediverse.
You only see local only. Unless the instance de-federates your content can be seen on other instances.
Nice. That's exactly how it should work honestly. Though I'll just leave it on because I like accessing the fediverse :)
@ernest can you clarify this?
2 questions for whomever has the answers
Gracias fellow kbinians ✨
Hi, I'm figuring this out too. Veterans, please feel free to correct me!
(kbin calls them /m/agazines, lemmy calls 'em /c/ommunities, if you're wondering about the 'm' vs 'c' in the URLs lol.)
You may notice this @[object]@[place] pattern a fair bit.
For example, our own 'music' community is @music@kbin.social. The lemmy.world 'music' community is @music@lemmy.world. Your account is @Spider-Man@kbin.social. See if you can spot users or threads that are from other sites! They're probably already in front of you!
As a second experiment, see if you can visit the music community from beehaw.org, without leaving kbin.social. They have one too, but you don't need a beehaw.org account to participate there!
Yes, this is correct.
As opposed to the thinking of a lot of people, being able to have duplicate communities on each instance is a feature, not a bug. It is a very good way to give people freedom of choice if, for instance, a mod for a community on one instance is taking the community in a bad direction.
Oh so that's what that does!
So... I take it that the sleep thing didn't happen? Been there - should be sleeping, too "in the zone" to sleep.
Sleep? What is this nonsense?
It's that thing that you eventually have to give in to, lest you turn into a gibbering wreck, unable to do something as simple as make a cup of coffee, without doing something stupid like putting the kettle in the fridge and wondering why the bottle of milk doesn't have a switch on it to boil it.....
Not related but I love that @ernest is on 196 and okbuddybaka
@ernest Is this something on kbin's side for why Mastodon isn't showing any posts from kbin.social? I'm able to view Lemmy communities fine on Mastodon, but unable to view anything from kbin.
I had to play around with it a bit to figure out how this is working. Basically, if you post to a Magazine's "microblog" it uses the Magazine name as a hashtag. See: https://kbin.social/m/kbinMeta/p/433361. Paste that link in your Mastodon client and you'll see the #kbinMeta hashtag. So, if you want to follow the Kbin Tech magazine you'd have to follow the #tech hashtag in Mastodon. If you look at that Magazine you'll see posts there from Mastodon servers. Those are posts with the #tech hashtag. Posts that don't have a hashtag end up in the Random magazine.
If you dive into the technology behind it all you start to see that all of these different platforms are designed to show the same content in different ways. They're all based on the ActivityStreams protocol: https://www.w3.org/TR/activitystreams-core/.
Take the image object. If you post an image to Mastodon you see the text that was posted with that picture then the picture. If you look at the same picture in Pixelfed (similar to Instagram), you'll see the image first and displayed prominently, since it's the focus, followed by the text. In Lemmy or Kbin you'll see a small thumbnail that you can then expand to see the full image. Same image object type, different ways of displaying it.
I guess the point is, depending on what your interests are (microblogging, sharing links, sharing photos, etc) you pick the platform that most suites your need. Or, have multiple accounts for posting different content.
Exactly what I was looking for. Otherwise there was no /all filter without being submerged by federated content.
Why am I still seeing posts from other instances on my front page when I have federation disabled? Is this a bug, or is it supposed to work that way?
I've turned off federation in my settings. Why am I still seeing posts like https://kbin.social/m/StarTrek/p/438502/Looks-like-r-startrek-and-affiliates-just-packed-up-and-setup , which was posted by someone at hachiderm.io? How can I limit to only seeing posts and content posted directly on kbin.social?
Lol I would have never in a million years figured out how to do that, and it's something I have kinda wanted to do -- the fact that the home page is a mix of posts from various Lemmies and Kbins and whatever meant that I have very little idea what actually was on kbin. Thank you!
so we can defederate individually with any magazine or all of an instance such as lemmy.ml
I believe turning federation "off" would just limit your feed to content from kbin.social.
If you want to block an entire instance of Lemmy you can use the /d/ (for domain) function. For instance, if you didn't want to see anything from lemmy.ml you could go to https://kbin.social/d/lemmy.ml and click the block icon on the right side. You can manage your blocked domains from your settings. You can also block individual Magazines/Communities by going to the community and clicking on the block icon.
You can also use the domain feature to block non-Lemmy/Kbin sites: https://kbin.social/d/newrepublic.com
Also, I'm not suggesting that people should be blocking either of those domains. They were just some of the first options on my feed that I could copy for examples.
this is super useful!
I posted this as a thread in the /m/kbinmeta to bring attention, linking back to your post
Wow, that's a superb feature I didn't know existed! So I could subscribe to https://kbin.social/d/newrepublic.com (not going to just using the same example) and get every thread that links there - nice!
It looks like that is a planned feature judging by the unpopulated "Instances:" heading beneath the main toggle. For now you can block specific communities/magazines from appearing in your feeds. So you could just block any lemmy.ml community that appears.
Thanks for the heads up. I definitely want to opt out. I hope this place has some staying power, but I don't want an interconnectedness to flood the home feed with too much ragebait and garbage content anywhere near what reddit turned into.
Your home feed can default to "All," which shows content from all communities across all federated instances (not just Kbin and Lemmy) or it can default to Subscribed, which shows content only from communities you're subscribed to. Lemmy has a third option called "Local" which shows content from all local communities. Turning off federation for yourself in Kbin is similar to the local option in Lemmy, but allows you to still switch between All and Subscribed (ie, all local or subscribed local). Lemmy doesn't currently offer a "local subscribed" view.
The hamburger menu next to your name allows you to toggle between Subscribed and All. In the dropdown menu when you hover over your name, under Settings, you can select your default view (Subscribed vs All).
My personal preference is to default to subscribed and see content from across the Fediverse that I choose to see. This way I'm not missing out on any communities or magazines on federated instances that interest me. I sometimes switch to All with the Commented sort to see what the current zeitgeist is (where are the biggest conversations happening). I don't see much need to de-federate my view entirely since I can block communities/magazines, or entire domains, which means even under All I'm not bothered by content that I find annoying, offensive, etc.
Does that work for you? Mine is set to Subscribed but my home screen still defaults to All. From another thread, it sounds like at least one other person is having the same issue.
For what it's worth - on the microblogging (twitter-like) part of the fediverse, we've had pretty great results federating with lots of instances, but defederating from the ones that have problems with hate speech, spam, etc. It's led to a much more positive vibe than Twitter etc because people aren't so afraid of some random person misconstruing something they said and jumping down their throat about it, and there's no algorithm pushing rage "engagement" to the top.
One of the problems we do have in microblogging land, is the main mastodon developer has tried to direct new users to his own instance, making it by far the biggest mastodon instance, and then did a bad job controlling spam - so the other instances were left having to chose between cutting off a huge number of real users, or being inundated with spam. Having all the kbin and lemmy instances federate with each other, except where there are issues, can make the network overall more resilient against any one instance being mismanaged or invaded by spammers and trolls. The users on that instance will have to move, but there will be plenty of similar-sized instances ready to welcome them, and if the magazines are also spread out, they can keep posting to the same ones.
(I admit I also have a selfish interest here - I'm posting this from fedia,io, a different kbin instance. I joined through a different instance than the main one to help nudge things toward decentralization.)