I’m sad because the fediverse wasn’t necessarily equipped to handle the influx of new people or accomodate all the outgoing mods. It should have been a moment to bring everyone over here, but sadly, even now I’m seeing the drop-off of usage of many of my fediverse hangouts. :(
There is truth to this. But, Reddit’s drama also put the spotlight on the fediverse and the need for alternatives to Reddit in general. Personally, I can say I did not even know it existed. Over the last ten-or-so years, Reddit really did develop a monopoly on forums. The progress we have seen with Kbin, lemmy, etc is because of their heavy-handed and poorly executed crackdown on third-party apps.
But still, you are correct that the fediverse was not yet a full-fledged alternative to Reddit in June. Many lemmy clients, such as Memmy or Mlem, were not ready yet. And most promising Kbin client, Artemis, is still in beta as well. Even Kbin itself is still technically a beta (not that I don’t love them both lol). Had all of these been ready in June, then I think the Reddit exodus would have been much more dramatic and impactful.
I think we need to give it a bit more time. After all, Reddit didn’t get huge overnight either. So long as we keep posting and commenting away, and create environments/communities that are welcoming, we should be able to eventually grow into something that can rival Reddit.
Since moving to kbin.social from Reddit I have been 10 times more active in posting because I want the platform to be successful and engaging. It's been a very refreshing change, but it only works if you participate.
We can't fix what happened. The June fiasco brought attention to the Fediverse and it provided a boost. A boost the fediverse wasn't fully equipped for, but a boost nonetheless.
The best thing to do is prepare for the next fiasco. And given "Reddit pays you for updoots" is still incoming, there will be a next fiasco. Make sure bugs are fixed, be able to point to some apps or alternative views that people made, and overall be a smoother transition than what was before.
Also, the Kbin dev expressly stated he isn't ready for a massive migration, and the current influx has caused him no end of stress. We want to keep him around and not drive him insane.
I appreciate the concern, and it seems to me that kbin is no longer just one person ;) Currently, kbin is a team of wonderful people who handle development work, devops, project management, and more. Additionally, Piotr helps me with administering kbin.social. There will be significant changes here soon, things are happening quickly. But to be honest, I wasn't fully prepared for such substantial growth, and it will probably take some time before everything stabilizes. But... this is just the beginning ;) What's important is that the snowball starts rolling, regardless of whether kbin, Lemmy, or Mastodon gains the most users. We all win in this situation.
Kbin is PHP/Symfony, but people are writing tools in various languages, not to mention clients. I haven't looked at the client repositories, but I assume that some, if not all, of the codebases for them are Java.
The thing that helps Kbin the most is that it is, by far, the easiest to understand. Googling "Lemmy fediverse" gives a bunch of various links to other Lemmy instances, which are presented in a way as if they are separated from one another. Kbin appears as one site, one location for content aggregation. Although that "goes against the idea" of decentralization, most users are currently looking for their "one home to replace their old one home". The more users flock to one area and learn how it works, the more things will begin to take their proper shape, so to speak.
A feature we'll definitely want to have with kbin in the future is the ability to migrate accounts to other instances. That would mean that even though we're centralizing on kbin.social right now, people could move to other instances and spread the load across the fediverse without losing their history
I'm still learning the ins and outs of this place and the others, but part of me thought that was the feature of being federated. User accounts could seamlessly transfer from one instance to another.
Looking further into it, it looks like that feature exists for content, but not so much for accounts.
Kbin doesn't have the ability to sort comments by top. To me, that is the #1 most important feature, and not having it when it's easy to do shows some real ignorance. The reason I come to these sites is to see the best comments on news of the day.
12 years ago reddit would crash all the time. To make it worse they always told me I was the one who broke reddit personally by putting a message on my screen. My bad yall.
Yeah, I always thought it was a little unfair when it popped up telling me that "Briguy24 broke reddit!". But I never held it against you, don't worry :)
To each their own but sometimes it's nice to just scroll through comments and see the varied replies instead of just fed the top/earliest on some posts. Imo it increases user engagement.
Brother, acting like a douche to people who are working and paying for you to be here shows some real arrogance. You're not a customer here. There's no ad revenue, no data collection, no money. If you want it so bad then do it yourself. Beauty of the fediverse is you can go make your own instance that does what you want it to do.
Even with the donations I doubt there's that much of a profit to being made. Servers are expensive, and there's no way that servers are the only overhead that ernest is dealing with.
His own knowledge, skills, abilities, and time are almost certainly worth more than he is receiving in donations. Dudes a skilled programmer/developer and is putting serious work into this. If he was putting his time and effort into freelance work instead he'd be building a heck of a nest egg.
They're not redundant functions. They're... Mixed up on kbin right now, because things were originally built with the up button boosting content, but that's incongruent with how Lemmy does it, so it was changed.
But boosting isn't really about sorting at all. It's about republishing content, so that it can be sent out to instances that have started following a group after the content was originally posted.
Perhaps more importantly why would one retweet a comment? Rather than a post?
The way content propagation works here is that someone using Website A follows a remote content source (either a user, or a group -- aka a "community" or a "magazine"), and the remote hosting website (let's call it Website B) sends all subsequent content from that source to Website A, where the requesting user can then view it. If someone from Website A was already following that content source, then they get to see all of the content that Website A had already received, and benefit from earlier users efforts. But if that person was the first from Website A to subscribe to that content source, then they only get future content.
It's very similar to a, well, a magazine subscription in that way. NatGeo isn't sending you their 150 years worth of back catalogue when you subscribe in 2023 (not that you should bother subscribing to NatGeo in 2023).
The 'boost' button republishes content, though. Posts, comments, whatever. Hitting 'boost' on a comment republishes it, and once republished the group actor (the little bot-like construct that functionally is the group) sees it as new content, and pushes it out to everyone following it. This means it will reach websites that started subscribing to the group after the comment was originally posted.
Boosting is how older content (where older basically means "from anytime before literally right now") spreads through the fediverse.
So this is one of those things like git, where you can't explain how it works on the surface to a normal person because it barely even makes sense if you don't know about the underlying plumbing. :\
Not awesome, but I guess that's what you get when you graft a reddit-like experience onto a fediverse that was more or less invented for microblogging.
Yea, i'm working on my own Fedi software and i'm struggling with the point of boosting in the link aggregator context. It's an odd overlap with Reddit-style reposting to appropriate subs, but based on the user.
It makes sense in the Twitter UX, but i struggle to find it's place in the Reddit UX.
I think boosts have potential to be used for crossposts, and the current implementation are just crossposts to your profile. Though they're likely here right now just because Kbin is a mix between thread and microblog software
Boosting is super important in all contexts in the Fediverse.
When am instance subscribes to a content source - be that a user actor or a group actor - on behalf of a user, it only requests future content. Back catalogues are not fetched by default. Boosting re-publishes the content, so that it is received by new followers.
With a group actor, the boost triggers the actor to reboot the content itself, sending it out to new subscribers to the group, and filling in that back catalogue.
Users who use the website that the community is hosted on have access to the full library of it. They need to boost stuff. And people who subscribe from remote sites need to boost older content that they've seen.
but relevant users cant see it, its never fetched for them to see it. Sure users on the home instance can see it, but they're on the home instance, it's already fetched for them. Ive run into this problem on here, where there is a lot of content on other instances that isnt visible from kbin. I have the option of visiting the home instance to see it, but it takes me completely off of kbin, I cant boost it from that page.
Someone just needs to follow. The community owner either needs to seed the community to big instances using accounts on them, or people who find the community via other instances need to subscribe and know that fresh content will come. Then they can boost older content from the hosting site.
Things take some conscious effort here. That isn't necessarily a bad thing.
"Then they can boost older content from the hosting site." No that's the problem. Like you yourself said back catalogues arent fetched. They can't see the older content to be able to boost it, they'll only see new content.
If my instance follows a community at time t = T, and your instance starts following it at time t = T+10, I can boost content posted between T and T+9 so that you can see it.
Meanwhile, if people on the hosting instance boost things posted from times earlier than T, we both get to see them. Then, once they're visible to us, we can continue to boost them for new instances to see.
If boosting is meant to be a solution to the back catalogue problem, then it's a horrible way to do it. You'd have to go through and boost every single post from before the hosting instance was followed, and then it'd only show up the user page of the guy who went to all of that effort? (or, realistically, bot).
If what I'm saying is accurate (and I'm still not sure because this is admittedly a bit too complicated for me) then it doesn't sound very useful since individual profiles aren't nearly as important in a forum context when compared to something like twitter, and especially when you can just upvote something and have that show on your profile. Unless I'm mistaken and anything you've upvoted doesn't propagate to another automatically instance while boosts do... but I don't think that's a big enough distinction to have two different buttons? You could just have an upvote also do that.
I see it as similar to the "save" function on Reddit, except it's public. I've started using it on things that I think I might like to read again later (and so by extension anyone who's "like me" would probably want to read it too).
i disagree, it's a great functionality that people should learn.. and here's the simple point.. you can BOOST a comment you disagree with, so that your argument AGAINST the comment will get more visibility.. reddit is dysfunctional, and this mechanism can help fix one of the problems reddit cannot get rid of.. this mechanism can help discussion, and fight against things like brigading..
think about it a minute.. someone makes a really TERRIBLE point that you can dismantle easily.. tear it down, and BOOST the hell out of it.. reddit cannot accommodate that.. keeping those two functions separate is critical..
this will help keep every thread from becoming a popularity contest that is entirely predictable, once people figure it out
edit to add: i've only been using this platform for a few days.. but i promise you, it works the way it's supposed to.. try it out..
@Friend. Do you have any tips for being able identify which instance a post is from? The “@**.” part of an instance name is usually cut off, and often the post title will say “kbin.social” next to it even if it’s not a kbin post. The only way I know for sure to tell is to click on a post and scroll past all the comments.
The post title clearly says kbin.social next to it. By he community label just says “youshouldknow.” It looks the same way from my home page: The only reason I know it’s actually on Lemmy.world is because I scrolled past all the comments, and also it’s in the url (which i am only looking at here because I copied and pasted the direct url for the post.)
Edit 2: I should probably also clarify that I am on mobile, so mouse-over’s are a no-go.
@CarlsIII try click on More at the original post and select Copy to Fediverse. That'll get you the originating url. This works for every type of post and comment.
Again, this is all way more work than it would be if the post just showed the instance in the first place. I already know I can find out what instance if I do some scrolling and clicking. I would prefer to just have the “@beehaw.org” added to the community name in the post (and to not display “kbin.social” on posts that aren’t even from kbin. I still haven’t heard an explanation for that.)
RedditMigration
Active
This magazine is not receiving updates.