Introducing temporary interaction limits | Hacker News Reader

Introducing temporary interaction limits

github.com

72 pointspetercooper16 comments

Is this to limit the HN effect whenever an issue is linked here and people just go "yeah +1" even if they don't actually read the discussion?

yeah +1

That and "brigading" where someone directs a bunch of people to an issue from Twitter, Reddit, etc.

Also for projects that regularly receive a good dose of Twitter hate (e.g. systemd).

You mention systemd getting a lot of hate, but I've never had any problems myself with it or know anyone who has. What sort of things do people dislike about it?

They're fixing things that aren't obviously broken and have served us well for many, many years. That alone is enough to make me sit up and take notice. But in several cases they've then created issues this way.

It's purportedly a replacement for Sysvinit/upstart. There's massive scope creep going on. Among a zillion other things, it now includes its own DHCP server.

It's generally looked down upon to scrap an entire codebase because "eh, it's old legacy code, we can do better". And systemd is running into a lot of issues that demonstrate why that's a rule of thumb.

I haven't seen that much since the emoji reaction +1 feature was introduced. I use the latter a lot though.

The +1 reaction has helped a lot but I still useless +1 / -1 notification spam pretty regularly from people who haven't gotten the message.

Github could add an option for "pre-receive webhooks" for comments. Push them to a moderator HTTP bot that returns accept/reject.

I've also thought it'd be nice to have a way for repo members to quickly send a warning to someone without spamming the thread. In this case, it'd be nice to have a way to put a specific person into a cool down period.

Not sure if you're referring to it but they announced (roughly) the feature you described yesterday.

Introducing temporary interaction limits - https://github.com/blog/2370-introducing-temporary-interacti...

That was what started this conversation but the feature announced doesn't appear to have the specific user cool-down I was hoping for.

"people who haven't gotten the message"

You cannot add emoji reaction from mobile version of Github website.

That sounds like a good issue to open with GitHub.

I've been using request desktop site to vote in Mobile Safari, but it is one extra thing to do.

This is the only purpose I see and with reactions on every post now I don't really see it much anymore. Though, in a similar thought, it would prevent brigades from HN / reddit / etc if it's, say, an unpopular feature or change and it's at the top of their front page for a while.

If it's a legit heated discussion and you limit it then you're just to come back in 24 hours to very long, impossible to follow responses. At least this has been my experience when people have left things to cool down them come back and need to respond to everything.

This seems like a good idea to me.

Nitpick: the captions under the checkboxes are very confusing because they're written with double negatives. "Users that have NOT X will be UNable to Y" could be "Only users that have X will be able to Y".

Reply on news.ycombinator.com