unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Corwin Brust <corwin@bru.st>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 39448@debbugs.gnu.org
Subject: bug#39448: 26.1; ERC connect wierdness
Date: Thu, 20 Feb 2020 07:38:34 -0600	[thread overview]
Message-ID: <CAJf-WoQA0e2-svimSsK2OjJMhUFgHvozqS3yBHes7-X4qx336w@mail.gmail.com> (raw)
In-Reply-To: <878skx5qnc.fsf@gnus.org>

[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]

I haven't yet.  More, I upgraded to 27.0.50 from 26.3 and everything is so
snappy and nice -  I maybe won't dig too hard anymore.

Shall we close this or is it better that I do try further digging?

On Thu, Feb 20, 2020, 07:34 Lars Ingebrigtsen <larsi@gnus.org> wrote:

> Corwin Brust <corwin@bru.st> writes:
>
> > Once I completely disabled the Comcast security feature, whatever it's
> called,
> > ERC connects without difficulty.
> >
> > I think this may still be a valid bug, however, as I was able to
> > connect to Freenode (used for testing in all cases) from rcirc even
> > while Comcast's anti-productivity software was active.  I'm curious
> > how the two different IRC implementations handle/depend on IDENT.
> > I'll dig into this if I can and report with such clues or questions as
> > I find.
>
> Whatever "security" software they were using could be using deep packet
> inspection; i.e., blocking the connection based on the protocol contents
> of the packets.  It does sound rather unlikely that anybody would bother
> to do that for IRC, but who knows these days...
>
> Did you find any further clues?
>
> --
> (domestic pets only, the antidote for overdose, milk.)
>    bloggy blog: http://lars.ingebrigtsen.no
>

[-- Attachment #2: Type: text/html, Size: 1834 bytes --]

  reply	other threads:[~2020-02-20 13:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-06  5:37 bug#39448: 26.1; ERC connect wierdness Corwin Brust
2020-02-08 19:29 ` Corwin Brust
2020-02-20 13:34   ` Lars Ingebrigtsen
2020-02-20 13:38     ` Corwin Brust [this message]
2020-02-20 13:56       ` Lars Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJf-WoQA0e2-svimSsK2OjJMhUFgHvozqS3yBHes7-X4qx336w@mail.gmail.com \
    --to=corwin@bru.st \
    --cc=39448@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).