Skip to content
This repository has been archived by the owner on Jun 6, 2021. It is now read-only.

policy update #513

Merged
merged 1 commit into from
May 23, 2021
Merged

policy update #513

merged 1 commit into from
May 23, 2021

Conversation

realrasengan
Copy link
Contributor

No description provided.

@realrasengan realrasengan merged commit 1194a3e into main May 23, 2021
@sonOfRa
Copy link

sonOfRa commented May 23, 2021

Is this the kind of unannounced policy change Freenode users should generally expect now? You see a behaviour you dislike, announce that it is against Freenode policy, and then retroactively change Freenode policy in order to make that statement true?

@dhjw
Copy link

dhjw commented May 23, 2021

Is this the kind of unannounced policy change Freenode users should generally expect now? You see a behaviour you dislike, announce that it is against Freenode policy, and then retroactively change Freenode policy in order to make that statement true?

Pretty much every site works that way and often changes its terms & conditions. If you actually read the change you see it provides a benefit to users in one part and in the other it removes rather than imposes limits on conversations.

Unlawful activities and related support activities are considered off-topic, as are
inappropriate advertising, heavy media file trading, proprietary game software modding,
warez, porn and various forms of antisocial behaviour, including (but not limited to)
political, racial, ethnic, religious or gender-related invective.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Glad to know I can now use political, racial, ethnic, religious or gender-related invective on freenode, this is a move in the right direction!

Copy link

@dhjw dhjw May 23, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assuming you're being sarcastic, why shouldn't people be allowed to talk about those things? Free speech is important. The answer to undesirable speech is more speech, not suppression.

"If there be time to expose through discussion the falsehood and fallacies, to avert the evil by the process of education, the remedy to be applied is more speech, not enforced silence." Justice Louis Brandeis in Whitney v. California

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is indeed the view generally taken by those with a loud voice, who are not under constant threat.

@Superfreeze-automated
Copy link

If you actually read the change you see it provides a benefit to users in one part and in the other it removes rather than imposes limits on conversations.

I would disagree, but it's not obvious why from the rule itself. Esp., read:

For abandoned project channels that have moved or are no longer available to the public, you may request the ownership of the channel be transferred to you.

Nothing against such a rule in general, but the problem is the context:

  • This rule was applied before it was merged here, i.e. the channel ##hntop was taken over (source: https://www.devever.net/~hl/freenode_abuse) and then the Freenode policy was retroactively changed. Also, the rule change was announced or discussed nowhere.
  • Timing and this story suggest that the intention of the change is to keep people from leaving Freenode. If a project moves and e.g. sets the topic to "Moved to Libera.Chat", then they can take over the channel (I mean, it's abandoned) and revert the topic.

I believe that Andrew Lee (alias rasengan) is acting in good faith (also, Hanlon's razor, benefit of doubt and so on). And I understand that he doesn't want abandoned channels polluting the namespace. But, to use a service, I would like to be able trust in the operator's decisions, which I can't anymore here.

@freenode freenode locked as resolved and limited conversation to collaborators May 23, 2021
@realrasengan
Copy link
Contributor Author

realrasengan commented May 23, 2021

Please comment on issue #515 . Thank you.

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

Successfully merging this pull request may close these issues.

None yet

6 participants