Hello, We would like to bring the idea of retiring Telegram Mindshare channel for favor of using our fedora matrix home server more and being a role model of this status.
Please state your comment, and vote for (+1 Retiring , -1 Not Retiring, 0 Neutral)
Thank you.
I'm favor of +1 retiring the Telegram channel and bridge
I don't carry a vote, but for what it is worth, Telegram is the platform I used most to participate in chats and team meetings. Eventually, I will get my three Matrix accounts sorted out, but for now, I rely on Telegram to stay connected to a lot of Fedora groups.
I think that a Telegram chat used for Mindshare business should be tied to a Matrix room for the same purpose, but I see no reason why the two can't be in harmony bridged together, unless there is a backstory or problem with how this does not work now.
@jflory7 technically we have couple of problems.
I am neutral (0) on this, mostly because I am torn between +1 and -1. My stance up to this point has been, keep bridges with telegram unless specific teams agree to remove it in their channels.
On one hand, telegram is convenient. I have reason to be there to support Fedora whether or not we keep team channels bridged or not. I think the same can be said for a handful of people on Mindshare currently. It is also an organically grown community space that we don't want to alienate.
On the other hand, telegram is not ideal for the reasons @thunderbirdtr mentioned. I also think we want to encourage teams to use Element/Matrix as much as possible and make that the standard for our community.
As an overarching decision making body, I think Mindshare has the responsibility to be a standard/model for other teams as well so I think its important that we do this thoughtfully.
+1 the tg bridge on matrix has caused a lot of confusion and hassle when the bridge goes down or when people think they can pm ppl on the other side when they can't and assume they're being ignored, etc. it simply doesn't make sense. carry it on as a user community but the contributor community is on matrix bridged to irc, another protocol added to the mix just causes confusion and a poor experience for new contributors imho
+0 I use the telegram channel as my primary method to enter to the meetings (and sometimes only allowed in my corporate network)
+1 retire the bridge. I agree with @duffy 's reasoning
@bt0dotninja Can you provide a little more information about this? Your corporate network blocks element.io / matrix but not telegram? Or are you using a phone at work to access telegram (you can use a phone to access element too, it has a nice android/iphone client) ? It would likely not block port 80 so you could use it in a web browser? Can you give us more specifics on the issue so we can help resolve it?
Well the corporate network filter apps by category (Chats in this case) telegram is allowed the because network monitoring system use many telegram bots for notifications. Also IRC is blocked. I am here from 8am to 4pm. And another policy is practically not use the cell phone.
@bt0dotninja how are they filtering out the traffic and excluding telegram?
NGFW with Category/Content filtering
Hi @bt0dotninja - we discussed this at our meeting this morning. It seems the general consensus is to retire the bridge, but we absolutely don't want to exclude you from meetings. I have definitely noticed your absence in our meetings since the bridge went down :(
Since we have an early and late meeting, we thought an okay solution might be to make the late meeting later so that you can attend. If this seems like a possible solution to you, please note the time frame and days which would work best and we can adjust our late meeting to accommodate :)
+1 for retire the bridge and the channel. If we move 1 hror our the late meeting i can participate :smile:
We discussed this in the Mindshare meeting today, and we are +1 to move the late meeting one hour later. If it doesn't work out, we can readdress the time again if needed
Telegram channel and bots now retired.
Metadata Update from @thunderbirdtr: - Issue close_status updated to: Complete - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.