this post was submitted on 02 Jan 2024
65 points (100.0% liked)
/kbin meta
3 readers
3 users here now
Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign
founded 2 years ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
you need to have an honest conversation with yourself before you address any further issues publicly.
from “if the update isn’t out by september consider this project dead” to “i’ll be working on it for a few hours then it should be good to go” you clearly have trouble estimating the amount and scope of work necessary to maintain a site of this caliber.
i’m not trying to be insulting to you, but you need to understand it’s starting to get tiring as a user too. take stock of what you are doing and pause for a moment before you give your users a defined timeframe.
the post where you said it would be a few hours is still up and unedited. that was 3 days ago. i wouldn’t have minded you saying “it will be a few days, maybe a week or longer” at the get-go but now we’re approaching 1000% estimated time to recovery and it feels like you are no closer than you were 3 days ago. it’s insulting and it definitely doesn’t need to be that way.
I don't quite understand what you mean. The problem is that in such a case, it's challenging to provide a specific estimate. That's why I occasionally provide updates in case the work is prolonged. It seems to me that this is how it works. Issues arose without any interference in the code or infrastructure. I addressed hardware problems, but it turned out that wasn't the only issue. Throughout this entire period, I've been attempting to ensure that the instance operates as smoothly as possible. It should be significantly better now, but I'm still actively working on it. Unfortunately, taking a holiday break here doesn't help either.
“I’ll be working on it for the next few hours” is different than “I’ll be working for a few hours today but have not identified root cause yet so I can’t say how long the fix will be”
“The update will come in September or consider the project abandoned” vs “I want to have the update out by the end of September but can’t guarantee any timeframes until I’m further along in the work”
“It should be back up in a few hours” vs “I’ll update everyone again once I’ve identified the issues and am working towards a clear resolution”
I’m not asking for more work or more communication, just honest communication.
Issues like the one that occurred are typically resolved within an hour, hence this post - mainly to quickly inform that work is underway on it. But you're right, I'll strive to improve communication in the future. Your examples gave me something to think about, thanks.
Honestly @ernest I don't think you have anything to worry about.
It is your platform. Make it at your own pace. Most of us are very happy to be invited on this journey and recognise that there are going to be ups and downs.
Good luck trying to convince this man. I'm sad to say that what I predicted, now two months ago, is happening. My advice; don't rely on kbin.social, find another instance (I recommend Mbin) or make one of your own.
Fedia.io can't even send a confirmation mail. lol
There are a lot of instances, just keep looking. Find the communities/instances you like, and subscribe to them from whatever quick, lightly-used, geographically-close to you instance you find to register on.
There's literally no location indicator for the instances servers so I'm not sure how you expect me to do that. And smaller instances are more likely to get abandoned, go down and vanish.