[META] mode +r & topic? #569

Closed
opened 2026-10-05 04:30:22 +02:00 by adam · 14 comments
Owner

Currently the channel doesn't require identifying to services, but that could reduce the amount of spam. ZNC has the *sasl module so more +r shouldn't cause too big issues.

The topic currently says:

http://znc.in | ZNC 1.6.1: http://wiki.znc.in/ChangeLog/1.6.1 | http://znc.in/nightly | https://github.com/znc/znc | Debian stable: 1.4 is 1.5 year old | 1.2 is 2 years old | 1.0 is 3 years old | Debian oldstable: 0.206 is 3.5 years old | don't randomly PM people | http://blog.max-mehl.com/2014/i-love-znc-because-ilovefs/

I think that at least how old all releases are could be removed or replaced with link to git tags and if mode +r is acceptable mention SASL:

www.znc.in | ZNC 1.6.1: http://wiki.znc.in/ChangeLog/1.6.1 | http://znc.in/nightly | https://github.com/znc/znc | How old is my ZNC? https://github.com/znc/znc/tags | don't randomly PM people | http://blog.max-mehl.com/2014/i-love-znc-because-ilovefs/ | Trouble joining? http://wiki.znc.in/Sasl

Currently the channel doesn't require identifying to services, but that could reduce the amount of spam. ZNC has the *sasl module so more +r shouldn't cause too big issues. The topic currently says: > http://znc.in | ZNC 1.6.1: http://wiki.znc.in/ChangeLog/1.6.1 | http://znc.in/nightly | https://github.com/znc/znc | Debian stable: 1.4 is 1.5 year old | 1.2 is 2 years old | 1.0 is 3 years old | Debian oldstable: 0.206 is 3.5 years old | don't randomly PM people | http://blog.max-mehl.com/2014/i-love-znc-because-ilovefs/ I think that at least how old all releases are could be removed or replaced with link to git tags and if mode +r is acceptable mention SASL: > www.znc.in | ZNC 1.6.1: http://wiki.znc.in/ChangeLog/1.6.1 | http://znc.in/nightly | https://github.com/znc/znc | How old is my ZNC? https://github.com/znc/znc/tags | don't randomly PM people | http://blog.max-mehl.com/2014/i-love-znc-because-ilovefs/ | Trouble joining? http://wiki.znc.in/Sasl <!-- github-sync-id:105735735 -->
adam closed this issue 2026-10-05 04:30:22 +02:00
Author
Owner

With bad math and /who #znc %na it looks like <100 of 946 aren't identified to services and if they wish to continue being on the channel after netsplit or something removes them, they will surely take a look at identifying.

With bad math and `/who #znc %na` it looks like <100 of 946 aren't identified to services and if they wish to continue being on the channel after netsplit or something removes them, they will surely take a look at identifying. <!-- github-comment-id:139123413 -->
Author
Owner

And while I am having IRC-monologue there I would also like to point out that I haven't received any more highlight spam than before being visibly op, so I would encourage other ops to get +O flag too.

And while I am having IRC-monologue there I would also like to point out that I haven't received any more highlight spam than before being visibly op, so I would encourage other ops to get +O flag too. - https://mikaela.info/english/2015/04/01/keep-the-ops-opped.html <!-- github-comment-id:139123565 -->
Author
Owner

... but that could reduce the amount of spam ....

Clearly you have never seen the totally idle efnet channel.

.... so more +r shouldn't cause too big issues.

And the random unregistered people that just need to ask one or two questions and never return? Do we just force them to register some nick to ask questions in the channel? Could totally create a #znc-unregistered and just forward them into that channel and help them in that channel. (I don't like that idea).

I think that at least how old all releases are could be removed or replaced with link to git tags

I like people on Debian/Ubuntu LTS/etc... with old versions seeing the /topic, knowing they might be on an old version of znc, but everybody knows nobody reads the /topic. /sarcasm

And while I am having IRC-monologue there I would also like to point out that I haven't received any more highlight spam than before being visibly op, so I would encourage other ops to get +O flag too.

Clearly we should just OP THE_ENTIRE_CHANNEL, I'm sure that will just get rid of all the spam cholby (or whoever that was) creates. When he spams the channel, he goes for all the normal people skipping the op'd/voice'd people, so they don't get highlighted to kick/ban him. (He knows the existence of the ASM bot and what it does, but oh well).

https://mikaela.info/english/2015/04/01/keep-the-ops-opped.html

... really? So you don't like freenode logic, who cares.

> ... but that could reduce the amount of spam .... Clearly you have never seen the totally idle efnet channel. > .... so more +r shouldn't cause too big issues. And the random unregistered people that just need to ask one or two questions and never return? Do we just force them to register some nick to ask questions in the channel? Could totally create a `#znc-unregistered` and just forward them into that channel and help them in that channel. (I don't like that idea). > I think that at least how old all releases are could be removed or replaced with link to git tags I like people on Debian/Ubuntu LTS/etc... with old versions seeing the /topic, knowing they might be on an old version of znc, but everybody knows nobody reads the /topic. /sarcasm > And while I am having IRC-monologue there I would also like to point out that I haven't received any more highlight spam than before being visibly op, so I would encourage other ops to get +O flag too. Clearly we should just OP _THE_ENTIRE_CHANNEL_, I'm sure that will just get rid of all the spam cholby (or whoever that was) creates. When he spams the channel, he goes for all the normal people skipping the op'd/voice'd people, so they don't get highlighted to kick/ban him. (He knows the existence of the ASM bot and what it does, but oh well). > https://mikaela.info/english/2015/04/01/keep-the-ops-opped.html ... really? So you don't like freenode logic, who cares. <!-- github-comment-id:139151682 -->
Author
Owner

And the random unregistered people that just need to ask one or two questions and never return? Do we just force them to register some nick to ask questions in the channel? Could totally create a #znc-unregistered and just forward them into that channel and help them in that channel. (I don't like that idea).

I think it's very unlikely for people on freenode to never have need for registered nick even if they asked #znc only one question. I am not suggesting any forwards as +r clearly tells you that you must be registered to join #znc.

I like people on Debian/Ubuntu LTS/etc... with old versions seeing the /topic, knowing they might be on an old version of znc, but everybody knows nobody reads the /topic. /sarcasm

If no one reads the topic it doesn't matter what it says.

Clearly we should just OP THE_ENTIRE_CHANNEL

Won't work in freenode.

... really? So you don't like freenode logic, who cares.

There are explanations on why if you ever clicked that link.

> And the random unregistered people that just need to ask one or two questions and never return? Do we just force them to register some nick to ask questions in the channel? Could totally create a #znc-unregistered and just forward them into that channel and help them in that channel. (I don't like that idea). I think it's very unlikely for people on freenode to never have need for registered nick even if they asked #znc only one question. I am not suggesting any forwards as `+r` clearly tells you that you must be registered to join #znc. > I like people on Debian/Ubuntu LTS/etc... with old versions seeing the /topic, knowing they might be on an old version of znc, but everybody knows nobody reads the /topic. /sarcasm If no one reads the topic it doesn't matter what it says. > Clearly we should just OP THE_ENTIRE_CHANNEL Won't work in freenode. > ... really? So you don't like freenode logic, who cares. There are explanations on why if you ever clicked that link. <!-- github-comment-id:139158095 -->
Author
Owner

There's a lot of spam? It honestly hasn't bothered me.

I don't think these precautions are necessary, and if anything I'd rather see +q $~a than +r.

I don't really mind the topic. People already rarely read topics, let alone click on links in topics.

There's a lot of spam? It honestly hasn't bothered me. I don't think these precautions are necessary, and if anything I'd rather see `+q $~a` than `+r`. I don't really mind the topic. People already rarely read topics, let alone click on links in topics. <!-- github-comment-id:139749504 -->
Author
Owner

I think it's very unlikely for people on freenode

Are people who saw "irc.freenode.net" on ZNC wiki and joined to ask some question considered to be "people on freenode"?

> I think it's very unlikely for people on freenode Are people who saw "irc.freenode.net" on ZNC wiki and joined to ask some question considered to be "people on freenode"? <!-- github-comment-id:141583256 -->
Author
Owner

Are people who saw "irc.freenode.net" on ZNC wiki and joined to ask some question considered to be "people on freenode"?

How many people you know that never do anything at freenode?

I can see that this issue doesn't seem to be getting so much support and since we have Sigyn (freenode utility bot that /kills nick spammers) since sometime after opening this issue I think this can be closed.

> Are people who saw "irc.freenode.net" on ZNC wiki and joined to ask some question considered to be "people on freenode"? How many people you know that never do anything at freenode? I can see that this issue doesn't seem to be getting so much support and since we have Sigyn (freenode utility bot that /kills nick spammers) since sometime after opening this issue I think this can be closed. <!-- github-comment-id:141619046 -->
Author
Owner

How many people you know that never do anything at freenode?

Every new user of IRC who has some question about ZNC. We shouldn't discriminate them.

> How many people you know that never do anything at freenode? Every new user of IRC who has some question about ZNC. We shouldn't discriminate them. <!-- github-comment-id:141634469 -->
Author
Owner

What about a separate +r #znc-dev channel?

What about a separate +r #znc-dev channel? <!-- github-comment-id:141644848 -->
Author
Owner

What would it be used for? From experience it looks like separate dev/support channels don't work and another not working thing is separating offtopic from main channel when it doesn't go too offtopic.

What would it be used for? From experience it looks like separate dev/support channels don't work and another not working thing is separating offtopic from main channel when it doesn't go too offtopic. <!-- github-comment-id:141645494 -->
Author
Owner

I'd forward all GitHub notices there instead. Discussion limited to ZNC
development. I'm here to develop this thing, not to babysit some wannabe
trolls.

Where does it not work? It works great for a much larger project that I'm
affiliated with. It's imho a very sensible thing to do when the community
channel gets crowded.

On Sat, Sep 19, 2015, 12:54 Mikaela Suomalainen notifications@github.com
wrote:

What would it be used for? From experience it looks like separate
dev/support channels don't work and another not working thing is separating
offtopic from main channel when it doesn't go too offtopic.

—
Reply to this email directly or view it on GitHub
https://github.com/znc/znc/issues/1076#issuecomment-141645494.

J-P Nurmi

I'd forward all GitHub notices there instead. Discussion limited to ZNC development. I'm here to develop this thing, not to babysit some wannabe trolls. Where does it not work? It works great for a much larger project that I'm affiliated with. It's imho a very sensible thing to do when the community channel gets crowded. On Sat, Sep 19, 2015, 12:54 Mikaela Suomalainen notifications@github.com wrote: > What would it be used for? From experience it looks like separate > dev/support channels don't work and another not working thing is separating > offtopic from main channel when it doesn't go too offtopic. > > — > Reply to this email directly or view it on GitHub > https://github.com/znc/znc/issues/1076#issuecomment-141645494. > > ## > > J-P Nurmi <!-- github-comment-id:141648088 -->
Author
Owner

That makes sense.

For example #ircv3 (but the dev channel is not used and the whole thing is dev) or Chromium (which made the mistake of calling dev channel #chromium and support channel of #chromium support (which is probably why it doesn't work and guess where do people go looking for support...))

That makes sense. For example #ircv3 (but the dev channel is not used and the whole thing is dev) or Chromium (which made the mistake of calling dev channel #chromium and support channel of #chromium support (which is probably why it doesn't work and guess where do people go looking for support...)) <!-- github-comment-id:141649381 -->
Author
Owner

I assume +q $a isn't any more welcome than mode +r, but it's the best way to manage botnet joining to the channel and starting spamming temporarily until staffers do their killing/lining.

I assume `+q $a` isn't any more welcome than mode +r, but it's the best way to manage botnet joining to the channel and starting spamming temporarily until staffers do their killing/lining. <!-- github-comment-id:142204185 -->
Author
Owner

botnets are only temporary, setting +r at the time of the event hasn't harmed anyone.

botnets are only temporary, setting +r at the time of the event hasn't harmed anyone. <!-- github-comment-id:142225645 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/znc#569