I personally have no opinion, but at least one person has expressed interest and I think it could be discussed to decide what to do.
https://botbot.me/ seems to be popular service for it with easy to remember URL.
## <bountysource-plugin>
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/27693682-meta-public-logging-of-znc?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).
</bountysource-plugin>
<!-- github-sync-id:113303887 -->
I forgot to say that I have one requirement if public logging happens: mention in ENTRYMSG "This channel is publicly logged at https://botbot.me/freenode/znc". Also in topic, but it requires making space and saying that in shorter form such as Logs: https://botbot.me/freenode/znc.
I forgot to say that I have one requirement if public logging happens: **mention in ENTRYMSG "This channel is publicly logged at https://botbot.me/freenode/znc"**. Also in topic, but it requires making space and saying that in shorter form such as `Logs: https://botbot.me/freenode/znc`.
<!-- github-comment-id:151056451 -->
it would be a great idea to log this channel, but the thing would be those who would be joining #znc would be running it like 24x7x365 thus no point in logging this channel :D
Assuming the one person you're talking about showing interest is also the person who made the above comment, they've basically pointed out the main flaw: it is redundant.
Nothing that important happens in #znc (well, the odd bit of drama can be rather entertaining... ) that would require anyone to need to see logs of the channel spanning 24/7/365.
`it would be a great idea to log this channel, but the thing would be those who would be joining #znc would be running it like 24x7x365 thus no point in logging this channel :D`
Assuming the one person you're talking about showing interest is also the person who made the above comment, they've basically pointed out the main flaw: it is redundant.
Nothing that important happens in #znc (well, the odd bit of drama can be rather entertaining... ) that would require anyone to need to see logs of the channel spanning 24/7/365.
<!-- github-comment-id:152308258 -->
Logging services generally tend to hide join/part/quit messages and being indexed by search engines it's possible that people searching issues they have could find a solution from public logs. It could also help in case someone doesn't keep logs and needs to find logs from few days ago which was the case of theh person for whom I opened this if I recall correctly.
I think that by thinking about this more I am in support of this and it might not hurt #znc-dev either as I think people with coding problems also use search engines.
Logging services generally tend to hide join/part/quit messages and being indexed by search engines it's possible that people searching issues they have could find a solution from public logs. It could also help in case someone doesn't keep logs and needs to find logs from few days ago which was the case of theh person for whom I opened this if I recall correctly.
I think that by thinking about this more I am in support of this and it might not hurt #znc-dev either as I think people with coding problems also use search engines.
<!-- github-comment-id:152423160 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I personally have no opinion, but at least one person has expressed interest and I think it could be discussed to decide what to do.
https://botbot.me/ seems to be popular service for it with easy to remember URL.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
Yes i too support this idea.
I forgot to say that I have one requirement if public logging happens: mention in ENTRYMSG "This channel is publicly logged at https://botbot.me/freenode/znc". Also in topic, but it requires making space and saying that in shorter form such as
Logs: https://botbot.me/freenode/znc.that's cool :)
it would be a great idea to log this channel, but the thing would be those who would be joining #znc would be running it like 24x7x365 thus no point in logging this channel :DAssuming the one person you're talking about showing interest is also the person who made the above comment, they've basically pointed out the main flaw: it is redundant.
Nothing that important happens in #znc (well, the odd bit of drama can be rather entertaining... ) that would require anyone to need to see logs of the channel spanning 24/7/365.
Logging services generally tend to hide join/part/quit messages and being indexed by search engines it's possible that people searching issues they have could find a solution from public logs. It could also help in case someone doesn't keep logs and needs to find logs from few days ago which was the case of theh person for whom I opened this if I recall correctly.
I think that by thinking about this more I am in support of this and it might not hurt #znc-dev either as I think people with coding problems also use search engines.
I completely disagree with this, plus it's useless, and what if someone's personal info gets there, etc, etc.