>> I've been through this, but I always end up muting them again.
>
> Same.

I've begun thinking there should be two kinds of mute. I keep lots of stackers on mute with whom I still correspond after viewing their comments, however keeping them muted gives me a way of controlling the order in which I read comments that is impervious to zapularity.

> I think people feel less responsible for their code now, just because an LLM wrote it for them.

Less at stake, because just blame the bot. But the avalanche of slop will influence culture the other way around ultimately: there is no longer any reason to deliver buggy code anymore. Get it right or gtfo.

> It solved my problem.

Mine too, thank you.

> I've been through this, but I always end up muting them again.

Same. This is why I'm okay with this. I don't care if other people interact with those I muted; I don't need to downzap anything but scammers (and sloppy stuff, on my territory, because I said I'd do that)

optimism

I realise one bad side-effect of LLMs is that there's increasing pressure for code to be highly polished before sharing

I would say the opposite is true: there has never been less shame in publishing bad code. See the 

 as just one example. I think people feel less responsible for their code now, just because an LLM wrote it for them. Or LLMs attract people with the wrong mindset to start contributing code.

I must admit, I do consider the simple implementation a bad idea, or at least, an excessively coarse solution to a granular problem

It solved my problem. I have muted a lot of stackers, and some of them comment a lot. It's very tempting to click and see who wrote what, similar to what 

. I don't think I've ever not regretted clicking on them.

I might have forgotten to unmute until someone mentioned him.

I've been through this. I always end up muting them again. At this point, I don't care about what I 

 be missing. It's not worth having a worse user experience overall.

mutenuke: never see 'reply from someone you muted' again

> I realise one bad side-effect of LLMs is that there's increasing pressure for code to be highly polished before sharing

I would say the opposite is true: there has never been less shame in publishing bad code. See the [PRs of this guy](https://github.com/stackernews/stacker.news/issues?q=is%3Apr+author%3Ajoelklabo) as just one example. I think people feel less responsible for their code now, just because an LLM wrote it for them. Or LLMs attract people with the wrong mindset to start contributing code.

> I must admit, I do consider the simple implementation a bad idea, or at least, an excessively coarse solution to a granular problem

It solved my problem. I have muted a lot of stackers, and some of them comment a lot. It's very tempting to click and see who wrote what, similar to what @optimism mentioned in https://stacker.news/items/1439391?commentId=1439436. I don't think I've ever not regretted clicking on them.

> I might have forgotten to unmute until someone mentioned him.

I've been through this. I always end up muting them again. At this point, I don't care about what I _might occasionally_ be missing. It's not worth having a worse user experience overall.