localslackirc VS repo-lockdown

> Really? Just a git command, a button press on GitHub? So why don't they just do it? Why don't they apply the patches when people send the code in then?

Because the patch was bad.

> Something like a month later the guy just rewrote the patch without even engaging with me.

Do you think he'd have done that if the patch was good? Was his version completely identical to yours?

> Yeah, that made me feel like shit

At least it didn't introduce a new bug to every user… I'm sure collective feelings of the userbase were less harmed in this case.

> Sorry but maintainers don't have the moral superiority to demand free labor

But you have the moral superiority to demand free labour from maintainers, to review, improve, test your patch?

Look at this pull request for example: https://github.com/ltworf/localslackirc/pull/387

How could a thing like that be merged?

When asked to split it, he just proceeded to open tens of pull requests that were all based on the previous one, in a chain. And every commit contains thousands of lines of unrelated changes with what the description is.

Then he got upset.

plugging my IRC gateway https://github.com/ltworf/localslackirc

I find that using slack from IRC, and having the option to deprive some people/channels to notify me is very helpful to reduce the amount of distractions.

I could never understand why people insist on using requests rather than the stdlib (which works just fine).

When async became a thing, I remember hitting some bug in aiohttp so I wrote myself a tiny (just doing the bit I needed) HTTP async client, which I figured was easier than wrestling aiohttp into compliance.

These days aiohttp is quite nice for async, and for sync I just use the stdlib.

My async client, if it can be of interest https://github.com/ltworf/localslackirc/blob/master/slackcli...

I normally use [localslackirc](https://github.com/ltworf/localslackirc) to use slack.

I can grep through the logs if I need to find something. That's really really fast compared to their search on the website.

I also get other advantages such as not automatically being forced to see all the reaction GIFs and being able to silence notifications from certain users that abuse them.

https://github.com/ltworf/localslackirc/ if you are interested.

GitHub makes this unnecessarily worse by refusing to let you disable Pull Requests like one can disable the other social features (Wiki etc) of a repository: https://github.com/dear-github/dear-github/issues/84

The workaround is to use GH Actions to auto-close PRs: https://github.com/marketplace/actions/repo-lockdown

And thank you for the link. I agree, automation is needed here. :) I'm using a different GitHub action: https://github.com/dessant/repo-lockdown

Something that really helps me uncouple programming from burnout is having a strictly-non-collaborative personal project in a language/ecosystem I intentionally avoid in the professional world. It's still open source Free Software but I don't ever want a pull request or even a bug report because then it becomes work and means the codebase is no longer a 1:1 representation of my own brain-space/goals/style.

Not that I have received any of those things, but I have steeled myself to be ready to turn it down if it ever does. The social pressure is real, and Github doesn't even let you disable pull requests so I had to configure a bot to automatically be an asshole for me: https://github.com/dessant/repo-lockdown

Here's the message I configured in my `.github/lockdown.yaml`:

```comment: Please accept my apologies for your wasted effort in closing this pull request, but I am not prepared to accept changes on this project at this time, if ever. This is a personal project for my personal website that I'm happy to share, but I want the code to be all mine. I would not be able to mentally connect with my codebase as well if it were a reflection of anyone but myself, and accepting others' code complicates the copyright situation regardless of the software license used. Please e-mail me with any bug reports :)```