I keep random accounts throughout the fediverse so downtime is not an issue for me. I'm grateful for this alternative that you've created and I understand that this project is still in it's infancy. Thank you for creating it, but please take time for yourself. This site is truly a gift.
Thank you so much for the update ernest! I can only imagine how much work this website takes, and I hope you have a swift recovery - skin problems are no joke!
Ernest! So sorry to hear about the struggles. Happy you responded, I'll stick around :)
Do consider adding more devs to the team! Not good that you are feeling pressure from dorks like us just because you need some time for yourself (or are working on things less visibly)
I'd volunteer, but I'm already burdened with personal projects and the horribly underpaid work in Hungary's own "public work program" (pays half of minimum wage for an 8 hour job), so currently I cannot. That being said, if there ever were some paid opportunity (even part-time at minimum wage), I could finally say goodbye to my current job.
Good luck to you!
But i think instead of waiting to announce planned things you should just show them, even in early stages.
Then we can give feedback, check your code and contribute ourselves.
You dont have to do everything, we really want to help.
On the other hand, if people really wanted to contribute, there's plenty of open issues on Codeberg that are unadressed. I agree that it would be better to announce plans in advance rather than surprise drop them, but I doubt there would be more contributions from the community.
I know. I'm just saying that the idea people would magically help out on kbin if he was more open about his plans doesn't work out, because the people willing to do so would either already be contributing to cleaning up the backlog or have moved on to mbin.
Btw, do mbin devs look at kbin issues too or do common problems have to be posted to both repositories to be seen?
Currently I wouldn't count on it as for as long as there is no activity on codeberg, looking at it in general is a waste of time. If you find an issue on both Kbin and Mbin and are convinced it is the same issue, it's definitely worth reporting on both.
Sometimes showing that things are being done is more work and way more stressful than the act of doing them, so I can relate to that.
But it would probably be a good idea to get more admins on board - sometimes one needs to take a break, and a one-person moderation team for a page with this many users cannot be sustainable in the long run. But I guess getting to a point where that is feasible, not to mention finding qualified people, might in itself be a fair share of work. :)
And of course - get well soon, Ernest! It's great to hear from you.
It doesn't have to be a show-and-tell. Just pushing your changes to a branch is enough. That way people can at least see that something is being worked on.
As a software dev I find it strange that you can go a month or more without pushing. At work I push at least daily, even if it's just a WIP commit that I reset the next day.
Exactly this is what i mean.
Name your branch something useful and push reguarly.
Ernest feels like doing so much secrecy for code that is ultimately going to be public anyways.. We wont scold you for having fucked up code. We will fix it ourselves if we have to.
Man if you look at this thread on Kbin and then again via another instance like Fedia, there are number of comments not federating across both instances. Kbin counts 24 comments and Fedia just 19. The missing comments on Fedia seem to be Kbin users. There's some comments in here that are upwards of 8 hours old that have not made it to both instances. This is really problematic.
kbinMeta
Najnowsze
Magazyn ze zdalnego serwera może być niekompletny. Zobacz więcej na oryginalnej instancji.