Really just the big ones. Lemmy, Mastodon, and Misskey. In my humble opinion, judging by the software alone, Misskey > Mastodon, kbin > Lemmy. Judging by the culture is a lot harder because it depends on the instance.
Honestly I would be fine if new accounts could not post at all for a bit. There was a big issue of no one posting content when folks were coming here from reddit. I think that is because it was regular folk and many of us follow a pattern of hanging out and getting comfortable and then replying to stuff and eventually posting stuff. this is how real human beings are which is why people were sorta gung ho to bot copy pasta from reddit but I like how humans are. Granted personality will effect this. type A maybe will engage sooner or such. Anyway I would have been fine if I could read only for a week and then reply only for a month and then finally be allowed to post. If someone becomes a mod non of these limits would apply to magazines they mod. Not sure how this would work with federation though. I still would love to sign up for others block lists. I like this user so I want to auto block anyone they block. I really like things to be controllable at the user level.
Kbin already let's you apoint users as instance level moderators (without admin permissions). So, Ernest probably just needs someone that can help with the moderation, because I can't tell he actually looks at the reports, considered I've reported several spam posts before (from kbin.social) and nothing was removed.
Given that we're so small at the moment, why should a post need an upvote to be at all visible on the default sort? It can the only post of the past two weeks, but if there's no upvote, it doesn't get seen. It's very impractical.
And even if we go with this logic, why should the criterion for a post being seen be whether OP remembers to upvote their own post? It doesn't make sense. If you think that posts should only be seen if someone opts to go through new and give it an upvote (because otherwise it's not a "hot" post), OP shouldn't be able to do that.
Right now, we have a system where a major factor in post visibility is, "Did OP remember to click the upvote button?" It's just not beneficial.
The "sort by hot" algorithm was probably designed with a larger user base in mind, but I agree with you. For small communities in particular (and the vast majority of Fediverse communities are still tiny) I think even posts with no upvotes (ie no self-upvotes) should be included in the "sort by hot" view. For larger communities, where the threshold for "new" and "hot" may be set higher, so it doesn't matter so much. (I don't know what the algorithm is, but it might be something like 'hot is defined as getting a minimum of X votes, where X scales with the size or activity intensity of the community'.)
i agree, i think your argument is 'why arent my own posts automatically liked by me'
call me a pedant but it hurts me to hear a category labeled hot, that has not had literally any user related activity. those 2 things are incompatible. just swap hot for new and call it day
hot to me is an 'activity over time' metric, and zero doesnt play nice
Yeah, having posts automatically upvoted by OP would be great. I think that Lemmy automatically starts with an upvote count of 1 regardless of OP's vote, so I think Kbin should do the same. I get that Hot is meant to factor in activity and time, but it just feels super off for the only post in the past month to not appear. Surely a post that was made an hour ago is hotter than a post was made weeks back.
Threadiverse is still in its nascent stages of development, and it is even earlier stages for kbin. Anyone who have been around in the internet long enough knows that these issues are common at this stage. People who are complaining are failing to realise that this is still just a passion project of a single individual who is really not making any real profits in return, and is not a multi-billion enterprise with server farms of its own across the world. Even Reddit and Twitter had lots of such hiccups when they started out.
Thanks for all the work you are doing, Ernest! Always happy to be here!
Thank you so much ernest. I was able to go to my subscriptions, and all, and notifications today and look at them by all and all the normal stuff. For a second there I thought there was something going on!!!
It’s the new lemmy update that is the issue. It broke a lot. Lots of people are abandoning lemmy anyhow, which is why the servers are so empty now. I don’t expect many lemmy servers to continue in the next six months.
the lemmy changes are causing excessive resource use on my 'bin instance. so yeah, not using lemmy, but being directly affected by the lemmy snafu.
my failed messaging queue is filling, which has its own retry logic.. that queue buildup also takes disk space.... extra processing, extra disk space.. this leads to 'worker' slowdown and then system failures and timeouts.
Lastly RabbitMQ allows message prioritisation. So you can drop the priority of things the older/more retries they contain.
Most of this is either RabbitMQ policy or Queue rules based on Headers in the AMQP message. Depending on how KBin is generating messages you might be able to do this as a system admin
the lemmy changes are causing excessive resource use on my 'bin instance. so yeah, not using lemmy, but being directly affected by the lemmy snafu.
my failed messaging queue is filling, which has its own retry logic.. that queue buildup also takes disk space.... extra processing, extra disk space.. this leads to 'worker' slowdown and then system failures and timeouts.
Oh, interesting. My bad then, it's common for people to be unaware that kbin is a different thing from Lemmy and so I made an incorrect assumption.
I suppose this reveals some room for improvement in kbin, then. Other servers' problems shouldn't be impacting kbin as badly as this, likely indicating that kbin needs to add some robustness when it comes to dealing with stuff like this.
your thought process isnt completely off. if my server product was detecting the failures correctly, these resources wouldnt pile up.
i dont think people really understand just how brand new all this stuff is. 'the fediverse' is under active development. they call it the 'bleed edge' of technology because its painful. most fediverse servers are experiencing growing pains of some sort.
the Lemmy/kbin sides are still wet behind the ears. i just hope people dont give up!
The beginning of reddit was much the same. Things stopped working all the time. Weird bugs popped up. And there were people posting posts like this a lot trying to figure out what was going on.
But the "spam" is no longer the issue, as ever since then, mod requests system has been implemented, allowing many new moderators to takeover communities with inactive moderators, as a result allowing spam to exist within these communities.
This wasn't the issue. The issue was that moderation actions didn't federate from here. I think that this hasn't been fixed and will be once the new ActivityPub stuff is done, though @ernest can feel free to correct me on that.
EDIT: Actually, maybe it has been implemented? Looking at @RedditMigration from Lemmy instances, it seems like the spam isn't there. If that's the case, lemmy.world should definitely reopen full federation.
kbinMeta
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.