open source software developers are getting fed up and are finally recognizing that they can just fucking leave.

[yuvalne@433.world]

@gsuberland @lianna @chirpbirb
gotta love it when the comments just prove the maintainer right...

[slyborg@vmst.io]

@gsuberland @lianna @chirpbirb ‘literally Hitler’

[sheogorath@microblog.shivering-isles.com]

@chirpbirb wow, that's almost acting like an adult.

Of course, you have this power and of course you can drop the ball like this, but it doesn't help anyone.

That "power move" is a move you get to make once, maybe twice in your life. Rage quitting a project because one guy asks for it, isn't really building confidence in you.

[drbrain@mastodon.social]

@lianna @chirpbirb as an eight year maintainer of a packaging tool for a popular programming language there is no fully acceptable way to deprecate features. Someone will loudly, annoyingly complain no matter what path is chosen. From my multiple personal experiences attempting this I will never fault a maintainer’s choice

[cybersaloperie@woof.tech]

@lunareclipse @chirpbirb yeah, as stated in the fucking license, maintainers don’t owe anything to anyone

Some months ago someone was trying to force me to accept their PR, I told multiple times that I will review it anytime soon when I have some energy again

They was still pushy, poking me every couple of weeks, sucking my energy like a vampire

So I took my distance to not suffer and now we’re 9 months later and I don’t give a fuck and will return when I’ll be ready ‍️

[lianna@micro.webgarden.click]

@Yuvalne @gsuberland @chirpbirb I guess making people's setups crash if you don't like their software is now completely acceptable in Mastodon reply-guy land. what a wonderful eternal september we're having on fedi

[cybersaloperie@woof.tech]

@lunareclipse @chirpbirb I’m so pissed out of people acting like I am at their complete disposal that my latest works are using this license where the only condition is that there is absolutely no warranty in any way

> Usage of the works is permitted provided that this instrument is retained with the works, so that any entity that uses the works is notified of this instrument.
> DISCLAIMER: THE WORKS ARE WITHOUT WARRANTY.

[lianna@micro.webgarden.click]

@drbrain @chirpbirb I mean, not going ahead actively putting effort into implementing sabotage features to crash setups is pretty easy. The ideal – if not perfect – solution would probably have been a deprecation warning and that's it.

[lianna@micro.webgarden.click]

@gsuberland @chirpbirb Malware is defined by software with unwanted, unexpected, malicious behaviour. Not every piece of malware needs to result in data breaches or something serious to be malware. Even a jumpscare screensaver is malware per definition.

Intentionally crashing your text editor if the maintainer is upset at your personal setup is pretty squarely in malware territory.

[flammableengineering@app.wafrn.net]

@chirpbirb@meow.social

This is funny as hell but I think the right move would have been to ban the shitty user

[drbrain@mastodon.social]

@lianna @chirpbirb warnings gave no fewer annoyed users and, when it was time to remove the functionality, the same types of complaints that lead to nvim-treesitter being archived

“You were warned” did not stop them, plus I had to deal with complaints about the warning for N extra months during the warning period

[tky@hachyderm.io]

@chirpbirb many moons ago I got fed up with the entitlement on the Undernet irc server I ran. I walked into the “machine room” (like I said, moons) and carried the server to my desk where I repurposed it as my workstation.

Petty? Yes. Childish? Kinda still was one. Satisfying? To this very day.

[yuvalne@433.world]

@lianna @gsuberland @chirpbirb
step 1: make an experimental plugin an indispensable part of your workflow.
step 2: ignoring the implications of step 1, use said plugin in an undocumented way.
step 3: bully the maintainer into supporting your unsupported usage.
step 4: ???
step 5: profi– oh nvm we made the maintainer quit FOSS and now the indispensable plugin is abandonware. dang. didn't see that coming.

[m@lgbtqia.space]

@lianna @chirpbirb

SOMEONE THINK OF THE CHILDREN!!!

[tml@mementomori.social]

@chirpbirb I remember back when I did the port of GIMP (and thus GTK and all that it depended on) to Windows, and had a mailing list called gimpwin-users or something like that.

Obviously, there were a lot of entitled users who were angry that I didn't fix their pet bugs very quickly. At around the same time, my own interest in GIMP and GTK was waning, and I had started doing full-time paid work on other open-source things (if I recall correctly). So finally some annoying arsehole pushed me over the limit and I just killed the mailing list. It was such a relief.

[sheogorath@microblog.shivering-isles.com]

@meena @chirpbirb I think you can scratch the rage in my statement and it remains true.

My point is that you should make your departure from a project gracefully, if possible.

Not for this guy who annoyed you, but the others who interacted with you in good faith.

[cyclopentane@rheinneckar.social]

@chirpbirb

>refuses to elaborate
>leaves

[navi@catcatnya.com]

@chirpbirb demanding support without giving the maintainer money is delusional too

[yuvalne@433.world]

@flammableengineering @chirpbirb true, but then we wouldn't be talking about this. if this going viral convinces at least some people to not become ban-worthy dicks, then it was probably for the better for that to happen.

[sam@shonk.sam.ax]

@lianna@micro.webgarden.click @chirpbirb@meow.social this sounds to me like an issue to take up with the package maintainer anyway
I can perfectly understand adding this to prevent a deluge of “help I use old version of $thing why it no work”