[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-community
Subject: Re: [kde-community] Telegram Relay Service
From: Laszlo Papp <lpapp () kde ! org>
Date: 2016-05-10 8:54:45
Message-ID: CAOMwXhNY08AV7Otw2BJ2hBpYJRvenTbHjkYw5=4_jN55AJibuw () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Tue, May 10, 2016 at 9:50 AM, Ben Cooksley <bcooksley@kde.org> wrote:
> On Tue, May 10, 2016 at 8:42 PM, Laszlo Papp <lpapp@kde.org> wrote:
> >
> >
> > On Tue, May 10, 2016 at 9:37 AM, Riccardo Iaconelli <riccardo@kde.org>
> > wrote:
> >>
> >> On sabato 7 maggio 2016 18:23:10 CEST Myriam Schweingruber wrote:
> >> > I wonder why nobody
> >> > examined this POV before starting to shift to Telegram. In this regard
> >> > Mattermost appears to make much more sense as we could run it on our
> >> > own servers, if we really need a phone client.
> >>
> >> Speaking as maintainer of a project which heavily uses Telegram: it
> allows
> >> backlogging and it is usable from behind any connection. For me it is
> >> impossible to connect to IRC from the University, the University campus
> or
> >> the
> >> research labs.
> >
> >
> > Why?
>
> Universities usually firewall their internet connections to permit
> only port 80 and 443 outbound.
> Sometimes you have to use an authenticated proxy to do that as well.
>
> If you're lucky some universities will allow port 22 (SSH) outbound.
>
> This makes IRC unavailable obviously, although tools such as Telegram,
> Slack, etc. which all use https and websockets to function work
> perfectly fine.
>
I am not sure that I can realise the obvious here. I had used IRC in such
an environment for years. If I recall it correctly, all I needed was an
interim box. In worst case, I am sure that this would not be a problem for
the KDE infrastructure to help a few KDE contributors in that case out. If
it was, we need to think about a solution for the community in my opinion.
>
> Regards,
> Ben
>
> >
> >>
> >>
> >> Bye,
> >> -Riccardo
> >>
> >>
> >> _______________________________________________
> >> kde-community mailing list
> >> kde-community@kde.org
> >> https://mail.kde.org/mailman/listinfo/kde-community
> >
> >
> >
> > _______________________________________________
> > kde-community mailing list
> > kde-community@kde.org
> > https://mail.kde.org/mailman/listinfo/kde-community
> _______________________________________________
> kde-community mailing list
> kde-community@kde.org
> https://mail.kde.org/mailman/listinfo/kde-community
>
[Attachment #5 (text/html)]
<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May \
10, 2016 at 9:50 AM, Ben Cooksley <span dir="ltr"><<a \
href="mailto:bcooksley@kde.org" target="_blank">bcooksley@kde.org</a>></span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex"><span class="">On Tue, May 10, 2016 at 8:42 PM, Laszlo \
Papp <<a href="mailto:lpapp@kde.org">lpapp@kde.org</a>> wrote:<br> ><br>
><br>
> On Tue, May 10, 2016 at 9:37 AM, Riccardo Iaconelli <<a \
href="mailto:riccardo@kde.org">riccardo@kde.org</a>><br> > wrote:<br>
>><br>
>> On sabato 7 maggio 2016 18:23:10 CEST Myriam Schweingruber wrote:<br>
>> > I wonder why nobody<br>
>> > examined this POV before starting to shift to Telegram. In this \
regard<br> >> > Mattermost appears to make much more sense as we could run \
it on our<br> >> > own servers, if we really need a phone client.<br>
>><br>
>> Speaking as maintainer of a project which heavily uses Telegram: it \
allows<br> >> backlogging and it is usable from behind any connection. For me \
it is<br> >> impossible to connect to IRC from the University, the University \
campus or<br> >> the<br>
>> research labs.<br>
><br>
><br>
> Why?<br>
<br>
</span>Universities usually firewall their internet connections to permit<br>
only port 80 and 443 outbound.<br>
Sometimes you have to use an authenticated proxy to do that as well.<br>
<br>
If you're lucky some universities will allow port 22 (SSH) outbound.<br>
<br>
This makes IRC unavailable obviously, although tools such as Telegram,<br>
Slack, etc. which all use https and websockets to function work<br>
perfectly fine.<br></blockquote><div><br></div><div>I am not sure that I can realise \
the obvious here. I had used IRC in such an environment for years. If I recall it \
correctly, all I needed was an interim box. In worst case, I am sure that this would \
not be a problem for the KDE infrastructure to help a few KDE contributors in that \
case out. If it was, we need to think about a solution for the community in my \
opinion.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> <br>
Regards,<br>
Ben<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
>><br>
>><br>
>> Bye,<br>
>> -Riccardo<br>
>><br>
>><br>
>> _______________________________________________<br>
>> kde-community mailing list<br>
>> <a href="mailto:kde-community@kde.org">kde-community@kde.org</a><br>
>> <a href="https://mail.kde.org/mailman/listinfo/kde-community" \
rel="noreferrer" target="_blank">https://mail.kde.org/mailman/listinfo/kde-community</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> kde-community mailing list<br>
> <a href="mailto:kde-community@kde.org">kde-community@kde.org</a><br>
> <a href="https://mail.kde.org/mailman/listinfo/kde-community" rel="noreferrer" \
target="_blank">https://mail.kde.org/mailman/listinfo/kde-community</a><br> \
_______________________________________________<br> kde-community mailing list<br>
<a href="mailto:kde-community@kde.org">kde-community@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-community" rel="noreferrer" \
target="_blank">https://mail.kde.org/mailman/listinfo/kde-community</a></div></div></blockquote></div><br></div></div>
[Attachment #6 (text/plain)]
_______________________________________________
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic