Bug #6054
The #hts freenode channel
0%
Description
Morning everyone, hope you're all well.
In light of recent events with Freenode (which I won't go into here) I took the liberty of opening a sister/brother #hts channel over on libera.chat. Sadly the mere mention of libera in the topic was enough to get the channel mangled. Not once did I mention #hts had moved.
Topic for #hts is: Discussion about Tvheadend: https://tvheadend.org | Logs at http://colabti.org | Latest stable is: 4.2.8 | This channel is also on libera.chat! * ChanServ (ChanServ@services.) has left * freenodecom (~com@freenode/staff) has joined * freenodecom gives channel operator status to freenodecom * freenodecom has changed the topic to: This channel has moved to ##hts. The topic is in violation of freenode policy: https://freenode.net/policies <freenodecom> This channel has been reopened with respect to the communities and new users. The topic is in violation of freenode policy: https://freenode.net/policies * freenodecom removes channel operator status from mpmc * freenodecom removes voice from mpmc * OperServ gives channel operator status to freenodecom
Why is this a bug? I opened this as a bug rather than in the forum because it affects the tvheadend '#hts' user community and as a community we need to make a decision as to where the main channels should be. Nothing is set in stone at this point.
So folks, what are your thoughts please?
PS: You're more than welcome to join #hts on libera if you like, however depending on the consensus in this issue that may change.
History
Updated by saen acro over 3 years ago
This is a freenode censor
11:20 <mort> Wait, just yesterday this channel had the libera channel in its topic 11:21 <mort> what happened? 11:21 <@danderson> freenode staff nuked all channels that had the word "libera" in their topic. 11:21 <@danderson> which includes 700+ OSS projects. 11:21 <@danderson> including #go-nuts :)
Updated by Flole Systems over 3 years ago
Well if they decided that they no longer want us by nuking the channel and think that a TV Server project is in violation of their guidelines then we will choose another provider which allows discussions about an open source TV software, can't be that hard to find one.
I personally don't use IRC anyways and would prefer something like a Telegram group (but that's probably just me ). As you already created a new channel I would say that we wait 7 days now in case someone has any concerns or sees issues, and if by then nobody commented those here it will be set in stone.
Updated by Mark Clarkstone over 3 years ago
Flole Systems wrote:
Well if they decided that they no longer want us by nuking the channel and think that a TV Server project is in violation of their guidelines then we will choose another provider which allows discussions about an open source TV software, can't be that hard to find one.
I personally don't use IRC anyways and would prefer something like a Telegram group (but that's probably just me ). As you already created a new channel I would say that we wait 7 days now in case someone has any concerns or sees issues, and if by then nobody commented those here it will be set in stone.
I'd love to see you on IRC though, and I'm also on Telegram.
My intention wasn't even to move the #hts channel at all but to have one on libera too. I suppose I could ask the freenode staff if people want it back but given how heavy-handed they've been I don't hold out any hope. Any takers willing to deal with them instead?
Updated by saen acro over 3 years ago
+1 for Telegram group.
https://www.redmine.org/plugins/redmine_chat_telegram
Updated by Mark Clarkstone over 3 years ago
- Due date set to 2021-07-01
just an FYI I updated the contact bit on the main page to include all three networks. trying to be neutral, even if personally I find it hard :).
I think it's wise we leave this issue open a bit longer so people not so active here can still have their say
Updated by Flole Systems over 3 years ago
Even if it's marked as resolved/fixed/whatever there can still be further comments, it's just "for us" to keep track of what needs attention and what doesn't afaik.
If we don't have control over #hts on Freenode then we should not list it. It can still be an unofficial channel and if someone wants to use it that's perfectly fine, but I think the whole point of having an official channel is that the team behind the software has control over it. So I think it should be de-listed.
Updated by Mark Clarkstone over 3 years ago
- Status changed from Need feedback to Resolved
Flole Systems wrote:
Even if it's marked as resolved/fixed/whatever there can still be further comments, it's just "for us" to keep track of what needs attention and what doesn't afaik.
If we don't have control over #hts on Freenode then we should not list it. It can still be an unofficial channel and if someone wants to use it that's perfectly fine, but I think the whole point of having an official channel is that the team behind the software has control over it. So I think it should be de-listed.
Flole Systems wrote:
Even if it's marked as resolved/fixed/whatever there can still be further comments, it's just "for us" to keep track of what needs attention and what doesn't afaik.
If we don't have control over #hts on Freenode then we should not list it. It can still be an unofficial channel and if someone wants to use it that's perfectly fine, but I think the whole point of having an official channel is that the team behind the software has control over it. So I think it should be de-listed.
Given the events yesterday it has now been removed with links pointing to this issue and another explaining what went on. I guess we can mark this as resolved now.
Updated by Mark Clarkstone over 3 years ago
- Status changed from Resolved to Fixed
Fixed may be a better status :p