current status
@whitequark
Yeah! Get their asses!
@whitequark a friendly reminder that I need the link to this issue…… for research purposes 0:::3
buildah actively breaks binfmt_misc registrations from an outer namespace · Issue #6611 · containers/buildah

Issue Description If buildah detects /etc/binfmt.d, /usr/lib/binfmt.d, etc it will break certain binfmt_misc configurations. Consider the following container configuration: Bare metal system: Debia...

GitHub
@whitequark @kebokyo I might have clicked some buttons
@whitequark seems these people (the stalebot operators) don't know what "friendly" or "reminder" mean, either. Upsetting!
@whitequark Systems like these very narrowly fail to be useful. In the case at hand, the bot could ping @nalind who contributed the change called out in this issue, and let them know the issue has been waiting for their feedback for 60 days.
@whitequark i played this game for over 2 years with telegram-desktop, long enough to change my userland and my go-to IM application
github: remove stale bot by ncfavier · Pull Request #8553 · nix-community/home-manager

Stale bots achieve literally nothing except spam people's mailboxes with meaningless automated messages (and corresponding "not stale" responses from rightly irritated contributors). ...

GitHub
@whitequark my default response is “the mere passage of time does not magically fix bugs”
@jasonkarns @whitequark
I'd also add "a bug tracker is not a todo list"

@whitequark ngl I kind of wish one particular piece of software had this, there was this dead-simple to implement on paper(afaik just disabling an api endpoint, similar to how they had done for a similar endpoint) request I had submitted to Rocket.Chat's feature request repo in 2022. Bumped it every now and then for about 2 years and haven't since because I no longer have to work with that crap anymore.

Oh, and they also completely lost a vulnerability report I submitted to them, received confirmation of that receipt, reproducibility, and escalation to the appropriate team. a bit later, another email saying an engineer was "actively working on implementing a fix", then radio silence. Haven't tested it in about 6 months but I'd be willing to bet the vuln still exists. (this happened like 2 years ago)

@whitequark Would you like to also query and mention all project maintainers when you speak "stale bots are an insult to contributors?" 'cause I saw that no one else is responding