Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

config: chatrooms no logging by default #2523

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

slook
Copy link
Member

@slook slook commented May 29, 2023

The "rooms" setting is sufficient for remembering to log particular chat rooms if desired, otherwise superfluous plain text data (containing massive amounts of spam) is written to disk, perhaps without user knowledge.

  • Changed: config.defaults["logging"]["chatrooms"] = False

See discussion #2519 wherein @j-minster raises valid concerns about the nature of plain text data generated by other users who tend to aggressively exercise their right to freedom of speech in the default room, that is persistently written onto local disk by the application.

The "rooms" setting is sufficient for remembering to log if desired, otherwise superfluous plain text data (containing massive amounts of spam) is written to disk, perhaps without user knowledge.
@mathiascode
Copy link
Member

mathiascode commented May 28, 2024

Seeing how the room has changed in the past few years, and the increasing number of new users, I'd be in favor of simply removing the nicotine room from the list of auto-joined rooms. I don't think most people care about the room or even notice that they've joined it, and it's still at the top of the list for anyone who wants to join it.

Some concerns I have:

  • Server traffic related to joining, leaving, as well as status/stat updates
  • Increasing amount of spam and garbage in the room
  • Large list of users for spambots to target

Removing the room from auto-joins would only affect new installations. We don't want to force such a change on existing configs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants