Is it just Kbin, or does every fediverse service have the issue of being totally swarmed with bots advertising illegal pharmaceuticals? Is this just the result of limited moderation?
Kbin seems more affected than others from what I can see in reports but it exists on other instances too.
It is a moderation issue in the sense that it is too easy for these bots to sign up. Individual instances could improve this by requiring an application for example.
With Lemmy, we have seen huge numbers of bots at times but most large Lemmy instances have registration applications turned on. As in you apply to join an instance instead of just being able to make an account.
By default this means waiting for manual approval of your account, but many instances set up automated approval behind the scenes.
This function means many spam bots are averted before the public sees them, and also spammers avoid instances with registration applications.
I mention this because Kbin, or at least Kbin.social, doesn’t appear to have registration applications which makes it a prime target for spam.
Also Lemmy has coordination between dozens of instance admins sharing details of spammers. I.e. a lot of hard work behind the scenes. I’d guess the lack of moderation at the admin level also accounts for part of the issue on kbin.
(A lot of Lemmy spam also comes via federation from Kbin.social, so much that many instances block high spam communities on Kbin and some block Kbin completely).
404's everywhere, "we're working on it" signs everywhere else.
Like sure, not being able to find my response in the pile of thread sounds like Linux problems, but how is this not loading faster and better than reddit?
Now that for-profit tech companies are beginning to implement #ActivityPub, I think it's important to establish what we want with the #fediverse and whether federation with #Threads, #Flipboard, Tumblr, and the like bring us closer to or further from those goals.
With that in mind, I've come up with a few statements (in no particular order) that describe what I think is an "ideal fediverse" — a fediverse that's not necessarily realistic but that we should aim for:
No actor controls a large portion of visible activity.
Users can move between instances without penalty.
Creating and running an instance requires minimal effort.
People on or entering the fediverse understand the variety of available options.
There is no downside to using free and open-source platforms over proprietary ones.
These definitely aren't comprehensive, and if you have anything you'd add, let's discuss that! They're currently helping me reassess my stance on Threads now that Flipboard is also entering the stage, and I hope they're helpful for others as well.
I'll elaborate on these five statements in the comments.
The whole point of the fediverse in general is that there is no single “we”. There are those ActivityPub servers that one federates with and those ActivityPub servers that one does not federate with. Lack of consensus is built into the technology by design.
but I think it’s still important that everyone at least thinks about what they want the fediverse to grow into
To have wants about the social constructs that sit atop the technology is to misunderstand the technology. The technology enables your enemies/people you don’t like/etc. to communicate and benefit in all the ways you do. By design. You cannot exclude from the fediverse, you can only exclude from your server. If you have wants about excluding then you’ve misunderstood the technology.
@rah Maybe I'm not being clear. When I say that "we" means "the fediverse in general", I don't mean that everyone should gather 'round and come to a consensus on what values they should uphold and who should be excluded. This is obviously something that should occur on an instance or individual level, as (A) there are a large variety of different people and instances on the fediverse with different priorities and (B) as you stated, anyone can implement ActivityPub and tap into the fediverse if they want to, regardless of what anyone else thinks.
What I mean is that people should be thinking about what they think instance owners should aim for and form their opinions on the current situation based on that. My goal with this post is to show what I think an "ideal fediverse" looks like and have others share their thoughts. Having thoughts about what's healthy for people on the fediverse and having wants based on that isn't misunderstanding the technology — it's simply expressing preferences.
@gmph postanowił zintegrować Mastodona jako system do skomentowania jego wpisu. Widzę, że komentarze wyświetlają się tylko chronologicznie - bez wątkowania w szeroko omawianym artykule, takim jak ten, gwarantuje to nieczytelny bałagan.
A, i testuję, czy wpis z /kbin pojawi się pod artykułem
I've been thinking a bit about this post regarding #Mastodon's responsibility to be compatible with the #threadiverse (#ActivityPub thread aggregators like #Lemmy & #Kbin). Right now, a thread from Lemmy or Kbin usually federates to Mastodon with truncated text and a link to the actual thread. However, many want Mastodon to be more compatible with threads so that the people over on Mastodon interact with the threadiverse more.
I was initially in agreement as a Kbin user. But having given it some thought, I think this is an unwise approach that'll only serve to overcomplicate platforms on the #fediverse. Yes, people on Mastodon should promote other parts of the fediverse (and vice versa), but complete interoperability shouldn't be expected of every platform.
As much as many would like it, you can't have long-form video from PeerTube, images from Pixelfed, threads from Kbin, blogs from Writefreely, etc. all neatly fit in a microblog feed. These are different formats made for different platforms, and the people making them are expecting them to be interacted with in completely different ways. When someone makes a thread in a Lemmy community, they're probably expecting that the people who are going to see and interact with the thread are people that want to see threads and are thus on a Lemmy instance (or another thread aggregator). If someone from Mastodon were to interact with it as if it were a microblog post, there'd be a big mismatch. People interact with microblogs differently than they do with threads — that's why they're separate to begin with. You don't see everyone on Twitter also wanting to use to Reddit because people who want microblogs don't necessarily want Reddit-style threads, and vice versa.
The other option, then, is to separate these different formats into different feeds or otherwise make them clearly distinct from one another. Kbin does this by separating threads and microblog posts into two tabs. While you can view both in the "All Content" tab if you'd like, they're styled differently enough that it's very clear when you're looking at a thread and when you're looking at a microblog post. This distinction lets users treat threads like threads and microblog posts like microblog posts, which is really helpful since the two formats serve different purposes and have different audiences. This option — clear distinction — is a great way to solve the conundrum I've been talking about… if your platform is meant for viewing all these different kinds of content to begin with.
And that's what it really comes down to imo. Mastodon is a platform for microblogging. Most people go to Mastodon because they want a Twitter alternative, not a Twitter alternative that's also an Instagram alternative and a Reddit alternative and a YouTube alternative. Even if you put these different content types in separate tabs, it would inevitably make things seem more confusing and thus raise the barrier of entry. Add a Videos tab to Mastodon to view stuff on PeerTube, and people are inevitably going to go, "Wait, what's this? Is this like YouTube? I thought this was just a Twitter alternative! This all seems too complicated," even if you tell them to ignore it.
It's probably best to leave Mastodon as it is: a microblogging platform that has some limited federation with other formats. The way Kbin threads currently display on Mastodon is fine. In fact, when I post a Kbin thread, I'm expecting it to be viewed via a thread aggregator. If people on Mastodon were part of the target audience, I would've made a microblog post.
Now, if you want to make something that lets you view everything on the fediverse via different tabs, feel free. As aforementioned, Kbin supports both threads and microblogs, though it comes with some challenges (e.g., trying to fit magazine-less microblog posts into Kbin's magazine system). However, this doesn't mean every platform on the fediverse needs to seamlessly incorporate everything else. I'd love people on Mastodon to promote and even try out Lemmy & Kbin more, but that doesn't mean Mastodon needs to also become a thread aggregator.
This isn't a hurdle because people typically aren't going to the fediverse with the idea of "I want a single app for all my social media." That's not how social media works outside the fediverse, so it's not really going to be a surprise that the Twitter replacement is a Twitter replacement and not one for 5 other platforms. If someone really wants to view Reddit-style threads, they're straight up better of making an account on a different platform (just like they would make a different account for Reddit) because Mastodon is a microblogging site.
Even the best attempt to incorporate all these different types of content into Mastodon is going to further complicate the platform and make more people dismiss Mastodon as too complicated of a Twitter alternative. This isn't a situation where there's no harm at best. And the potential benefit? Lemmy comments having the occasional Mastodon user?
Mastodon itself is a good enough introduction to ActivityPub without needing to make it support other things. It shows how people on different servers can share & interact with a pool of media through the same protocol. When people learn about other platforms on the fediverse, they can go check those out. Just promoting the platforms will do the job fine without complicating people's entry into the fediverse.
I've noticed that a lot of people on the #fediverse aren't particularly welcoming to those who don't initially get it or have trouble with it. You'd think that if multiple people say they have trouble picking an instance, it might be a genuine barrier to entry that we need to consider when introducing them to the fediverse. But no, instead of suggesting an instance to get rid of that barrier everyone gives unhelpful advice like "just pick one" or "it's not that hard." We'd have a much easier time getting people on the fediverse if there weren't so many people with this attitude of "the fediverse is simple, and the people who don't get it are lazy and should try harder."
The issue is that there isn’t really anything more to choosing an instance than just picking one though, and we don’t want to funnel every new user to a single instance lest this end up becoming just reddit with extra steps. Or the reccomended instance gets flooded with more traffic than it can handle.
At most, a new user may want to look at what instances have defederated from the one they want to sign up on, but that’s a concept that isn’t going to make sense to someone who is already having trouble understanding “sign up somewhere, interact with everywhere” setup.
Numerous guides to all of this have been created. Rather than tilting at windmills (you will never stop people from being rude online, best to just accept it) your effort would be better spent being the friendly guiding hand. That’s far more effective than trying to call out people who probably don’t care whether we’re attracting more users or not.
@wizardbeard I'd argue that telling people to join largest (or at least a larger) instance isn't a bad thing. If I was telling someone to join Kbin, I'd tell them to just pick kbin.social. Later on, once they get accustomed to fediverse and understand the idea better, they can go to a smaller instance if they want
(e.g., if it's focused on a topic you like, it has features or moderation policies you prefer, or you just want to take some load off the larger instance). Having people initially go to larger, more established instances — where the experience tends to be more approachable due to more active hosts, more old content being federated, a larger community within the instance, etc. — greatly reduces the barrier to entry.
And the danger of a lot of people on a single instance is really exaggerated. If things go badly on, say, a Lemmy instance that most people are on, they can just move to another one with the same features, same UI, and similar access to content. It's not like Reddit or Twitter where moving means you're missing out on a ton.
You're right that it's usually better to be the change you want to see as opposed to simply criticizing others, but I think it's still important to discuss how we introduce people to the fediverse.
XSMB - Kết quả xổ số miền Bắc - KQSXMB - XSKTMB hôm nay - SXMB
Sân chơi xổ số kiến thiết miền Bắc ngày càng thu hút sự quan tâm của nhiều tay chơi dự thưởng mỗi ngày. Số lượng người chơi dự thưởng cũng ngày càng tăng cao, nhưng bạn có bao giờ thắc mắc tại sao lối chơi này có gì mà nhiều người chơi lựa chọn đến vậy? Cùng tìm hiểu chi tiết nhất các thông tin cơ bản về lối chơi kết quả xổ số miền Bắc này với chúng tôi qua bài viết nhé.
@vkc Don't worry. In the near future, we'll be working on integrating with, among others, Peertube. For now, you can search for people from Peertube and follow their accounts, for example, "warroza@tube.pol.social." At some point, their content will start appearing in your feed ;) Enjoy.
I'm wondering if any of you need a virtual assistant. I'm Lynda from Nigeria, currently unemployed, and thought maybe someone here would be interested in employing me. I have experience working with an online institute as an admission counsellor.
I've been testing out Mbin on the kbin.run instance and it sure feels faster but it also feels empty and I'm pretty sure it's because Kbin / Mbin requires someone to have searched for a user or community/magazine before you can actually see it. Seems like this could hinder smaller instances in the long run.
