I don't know what this xz thing is about, first time hearing it. But people saying he should get more help are trying to help him, not having malicious plans like installing backdoors or whatever.
I do think people should ask less for more maintainers — the project is already opensource, so it's up to maintainers to join, not him to seek them out. But he should still get some help with managing the instance. Pauses in development are fine imo, but the instance shouldn't be swarmed with spam and account deletion requests lost in limbo just because ernest got sick or something, which can happen with the best work life balances.
I don't know what this xz thing is about, first time hearing it.
Someone pressured the maintainer of a compression tool used in a bunch of open source software to hand over the keys by citing burnout and offering to "help" then spent ~3 years slowly adding tiny changes that combined to form a backdoor in SSH that nearly compromised the entire internet or something.
It was only barely caught by accident because it made some thing some guy was doing that wasn't even related a fraction of a second slower.
Been all over the FOSSiverse for days, and the social engineering that was used on the xz maintainer reminded me personally of similar pressure certain people have applied to Ernest in most threads about kbin performance I have seen.
The reason it worked is because sometimes burnout is a real problem, and getting extra help is a real solution. The fact that this was exploited in one situation doesn't mean that all of a sudden there isn't any real burnout or genuine offers to help any more.
A project can sometimes benefit from help even if there is no burnout. People have limits.
I realize that a magazine I made isn't available through lemmy.world and lemmy.ml and some communities from there aren't available here. Does someone know why?
Normally if nobody from an instance has subscribed it doesn't show up in searches from that instance. You have to manually type the exact url and subscribe that way. Once one person has done it, it will show up.
To newly federate a magazine with Lemmy, search for it using the syntax !Polytopia@kbin.social in Lemmy's built-in search. This worked for me instantly when I just tested it on lemm.ee, after confirming that it 404s before doing it.
for a magazine to show up on lemmy, a logged-in user needs to visit it first. afterwards, to ensure that new content is published to lemmy instances, someone from that instance needs to subscribe to the magazine. this needs to happen on every instance as far as i know. this is one of the reasons services like lemmy-federate.com or browse.feddit.de exist.
@ernest thank you for the update and everything. Its great to hear your personal matter is kinda sorted.
I already have the moderation of several magazines so I won't be able to contribute to that more, I think.
I am a little bit familiar with bug reporting, not in github tho. So I just created a github account and a codeberg to try and contribute. Of course I will have to spend time checking out the existing ones and familiarizing myself with the platforms. I say all this because if you or any of the active devs, have test cases or a specific area that you would like to check first or anything relevant, I would gladly do my best to help on demand.
The time away almost seems like a benefit now. It gave people a chance to grumble and you have responded to many of the complaints from that time in this one post. Great on you for listening and responding to the community.
On Lemmy, users can send each others direct messages. It seems like Kbin/Mbin has no way of displaying those direct messages. Is that correct or is there a way to show direct messages?
Direct messages exist on kbin/mbin, but users are currently unable to send or receive them from other instances than their own. Sending is implemented but intentionally disabled by ernest, for unknown reason, but it might have to do with receiving not working.
Mbin has an open issue on this and yesterday someone said it's planned but low priority. It also links to the related kbin issue.
I have to say that I agree with others there are significant structural issues with the benevolent dictatorship type governance model. A team of people with diverse skills, strengths, weaknesses, commitments and all that is needed to bring a project like this to its potential.
Establishing a committee of some sort to share the work is really going to allow your efforts to shine to a greater degree and highlight your contributions, not diminish them. Perhaps getting in touch with some organization like Software Freedom Conservancy for advice? They exist to help with this sort of thing:
Conservancy assists FLOSS project leaders by handling all matters other than software development and documentation, so the developers can focus on what they do best: improving the software for the public good.
kbinMeta
Ważne
Magazyn ze zdalnego serwera może być niekompletny. Zobacz więcej na oryginalnej instancji.