/kbin meta

1 readers

4 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 1 year ago

Do the "Ernest needs to add more maintainers to KBin!" comments remind anyone else of the xz social engineering malarkey? (kbin.social)

submitted 7 months ago by FfaerieOxide@kbin.social to c/kbinMeta@kbin.social

47 comments fedilink hide all child comments

Comments such as:

letting more people help with Kbin development.
...
Why not getting some help? I know that Ernest already said he has a problem trusting people, but

Why has Ernest insisted on being the only developer to work on this? This creates a potential “single point of failure” situation.

I understand the desire to keep kbin a solo project in order to maintain control over it, but if this is going to see any success in the long term, then there needs to be a team.

come up in almost all threads about KBin's performance. At the time I just read them as nincompoops being whiners.

In hindsight does remind one a bit of similar social pressure leveled against Lasse Collin, does it not?

Not saying people are trying to backdoor this place or anything. The similarity just seemed worth pointing out.

you are viewing a single comment's thread
view the rest of the comments

[–] FfaerieOxide@kbin.social 4 points 7 months ago (27 children)

I mean, he’s developing and administrating what’s essentially a Reddit clone all on his own.

And doing a damn fine job.

The question was if you saw similarity in the pressure to add maintainers to the project with the social engineering that lead to xz getting backdoored.

[–] eveninghere@beehaw.org 2 points 7 months ago (7 children)

And he's burning out. And more maintainers would be even better.

Yes, it's similar, but every one-man project with real-world use is similar in that regard.

[–] FfaerieOxide@kbin.social 1 points 7 months ago (6 children)

And he’s burning out.

I have seen no evidence of that. Also not the point of this thread.

[–] HeartyBeast@kbin.social 4 points 7 months ago (1 children)

I’m not going to pick through his last year’s posts and make a diagnosis, but if you’ve seen no evidence of that, I think you’re wilfully ignoring the signs.

[–] FfaerieOxide@kbin.social 1 points 7 months ago (1 children)

I’m not going to pick through his last year’s posts and make a diagnosis, but if you’ve seen no evidence of that, I think you’re wilfully ignoring the signs.

Ok, I'll continue "ignoring" evidence you can't even describe ("He talked somewhere about..."), much less cite.

For all we know his frequent absence is down to a great work-life balance on his part.

Irrespective this thread is not about who is or is not burnt out, it's about how posts like your are what enabled the xz backdoor to happen.

[–] HeartyBeast@kbin.social 5 points 7 months ago* (last edited 7 months ago) (1 children)

Irrespective this thread is not about who is or is not burnt out, it's about how posts like your are what enabled the xz backdoor to happen.

I thin you need to chill a bit. Open source has a long illustrious history of people cooperating to build software and submit patches and enhancements which are then scrutinized by project leads. Yes, occasionally bad actors use this model to try and slip through exploits, but you don't throw out one of the strengths of open source because of that. You make sure mechanisms are in palce to allow robust scrutiny.

And no, I'm absolutely not going go through someone's post history and quote bits that show someone is frazzled. I expect you to have enough empathy

[–] FfaerieOxide@kbin.social 1 points 7 months ago

I thin you need to chill a bit.

I'm not the one calling people willfully ignorant about things a thread isn't even about.

one of the strengths of open source because of that.

I don't think being a jerk is a strength

load more comments (4 replies)

load more comments (23 replies)