Sorry I rushed it out after the first poll locked out. I had bisexual before so I'll add it as soon as I can. I wanted gay and lesbian so people who wish to see the divide can do so I was hoping it wouldn't clutter too much and that's also another issue. I knew making this people would question the western and English speaking biases and whatnot but understand I struggle to reconciliate all the considerations while maintaining the data interesting and useful to look at/ digest
@Spaghetti_Hitchens This is a good idea. Right now, I am using Google Keep or Skiff Notes. I tried to send a message to myself here on Kbin and ... well I broke it. 😁 So a save or bookmark feature would be handy.
I would like more information, please. if I am running software on a public server which breaches any license or law I would like to at least be made aware of that
TLDR: It’s broken, but It’s still a fun and enjoyable platform!
Very true. It's a lot more stable than it was even a couple months back - I used to upgrade my instance and run into constant problems, and now I can happily git pull without destroying everything.
From a user perspective, a lot of the issues you encountered early on were due to a couple factors - kbin.social was dealing with more traffic than it could handle, and the developers of lemmy added a sneaky thing that would specifically block kbin user agents from being able to federate out to lemmy instances, leading to constant error logs and issues.
I would say that, aside from platform stability, the biggest looming threat on the horizon is spam. Think about email (the original federated message system) - nobody even thought about the possibility of spam when developing email, spam exploded in the 90s, and currently spam control is managed by whichever email platform you're on rather than by the protocol itself, as well as a sort of trust system where newly registered domains are more likely to be seen as spammers. The Fediverse needs to take lessons from email and start implementing the same sort of controls before the issue becomes unmanageable.
and the developers of lemmy added a sneaky thing that would specifically block kbin user agents from being able to federate out to lemmy instances, leading to constant error logs and issues.
Do you happen to know why they did it? Was it that kbin was causing them technical problems somehow and they chose to block it until they are resolved or was it just pettiness?
Unfortunately I don't know. It could very well have been that their own instances were being flooded by traffic from kbin.social and this was their solution. However, to my understanding this was added to the source code itself so all lemmy instances upgrading suddenly become an issue for kbin instances. I had to change the user agent in my own kbin instance to stop the flood of errors as it was absolutely messing up the.coolest.zone and I basically couldn't troubleshoot any legitimate failed messages.
Whatever the case is, I'm very glad it's resolved now.
IIRC the official reason was that some automated anti-spam code accidentally caught the kbin user agent and mistakenly added it to a block list, and the lemmy.ml admins were busy and didn't see it for over a week - but once one of them noticed it was promptly fixed.
Also, I recall this being specific to lemmy.ml - other instances run by other admins like lemmy.world and lemmy.ca weren't affected.
Thanks for sharing your experience. Good post. I really like your conclusion and your determination not to give up. And I hope that the annoying bugs will get ironed out soon.
Great post! We need more people to share their experiences. In the end, I'd rather support a decentralized open platform run by the community that a centralized commercial platform run by greedy capitalists.
The same thing seems to be happening with [email protected] and [email protected]. The former hasn't had a post show up on kbin since July 13th, while the later doesn't appear to have any posts at all. Initially I was thinking maybe it was due to the lemmy bug that mistakenly marks some connected instances as inactive and stops sending them updates. It may be specifically because these are bot accounts, though.
I believe this is specifically a bot account issue, because non-bot posts are still showing up as expected. On Lemmy, there's an option that toggles the visibility of bot generated content, but it doesn't seem to be a setting here.
I noticed I submitted this question 4 times. Once from another instance. My apologies. I have removed all duplicates. The reason for this is that after placing the thread, I got an error message and was under the assumption that posting the thread had failed.
/kbin
Oldest