From: Daniel Havey <dhavey@yahoo.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Bloat Digest, Vol 49, Issue 3
Date: Sat, 31 Jan 2015 13:40:28 -0800 [thread overview]
Message-ID: <1422740428.24297.YahooMailBasic@web141604.mail.bf1.yahoo.com> (raw)
In-Reply-To: <mailman.3.1422734401.24961.bloat@lists.bufferbloat.net>
Cable customer "service"...
Press 1 for more latency.
Press 2 if you would like to experience extreme packet loss.
Press 3 to pay more for less throughput...
...Daniel
--------------------------------------------
On Sat, 1/31/15, bloat-request@lists.bufferbloat.net <bloat-request@lists.bufferbloat.net> wrote:
Subject: Bloat Digest, Vol 49, Issue 3
To: bloat@lists.bufferbloat.net
Date: Saturday, January 31, 2015, 12:00 PM
Send Bloat mailing list submissions
to
bloat@lists.bufferbloat.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.bufferbloat.net/listinfo/bloat
or, via email, send a message with subject or body 'help'
to
bloat-request@lists.bufferbloat.net
You can reach the person managing the list at
bloat-owner@lists.bufferbloat.net
When replying, please edit your Subject line so it is more
specific
than "Re: Contents of Bloat digest..."
Today's Topics:
1. Re: [Cerowrt-devel] live
streaming from nz (Dave Taht)
2. New "comcast" tool (Dave Taht)
----------------------------------------------------------------------
Message: 1
Date: Fri, 30 Jan 2015 15:48:03 -0800
From: Dave Taht <dave.taht@gmail.com>
To: "Richard E. Brown" <richb.hanover@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
bloat
<bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Cerowrt-devel] live streaming
from nz
Message-ID:
<CAA93jw4d_V0VQ-DiKrVuFed3iHtamxunnaK+u9YmhgwT8kOD+A@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
I wanted to note that all the nznog talks were very good!
http://new.livestream.com/i-filmservices/NZNOG2015/videos/75358960
The one prior to mine went deep into some analytical methods
for detecting
significant latency events, the one after into the problems
cloudflare
deals with on ddos attacks, and the last talk the night
before went into
the problems new Zealand is having with their CPE in their
fiber
rollout.... Ending with a well received proposal to create
NZwrt as a
solution....
See the last, especially. Very inspiring, and being now
discussed in the
nznog list. Head over there for more details.
I plan to take a bit of vacation this week. If you really
need to reach me,
you will have to paddle out to
http://surf.co.nz/reports/north-tasman/raglan/
I missed the swell last week, darn it.
On Jan 30, 2015 12:17 PM, "Rich Brown" <richb.hanover@gmail.com>
wrote:
>
> Ahah! Dave's session seems to be at:
>
> http://new.livestream.com/i-filmservices/NZNOG2015/videos/75358960
>
> Look for the "NZNOG Friday 30th Morning" recording.
Dave's talk starts
about 2:20 into the movie (2 hours, 20 minutes)
>
> Rich
>
> On Jan 30, 2015, at 7:55 AM, Keith Duthie <keith@no.net.nz>
wrote:
>
> > It's available there now - I just watched it.
> >
> > On Fri, Jan 30, 2015 at 11:49 AM, Rich Brown
<richb.hanover@gmail.com>
wrote:
> >> Arrgh... I signed in time to see your "Thanks
for letting me show you
this..." slide. I hope it went well
> >>
> >> Do you know if the presentation will be made
available later? Thanks.
> >>
> >> Rich
> >>
> >> On Jan 29, 2015, at 4:32 PM, Dave Taht <dave.taht@gmail.com>
wrote:
> >>
> >>> I'm giving a talk in a few minutes at
nznog if anyone cares:
> >>>
> >>> http://www.nznog.org/home/video_full
> >>>
> >>>
> >>> --
> >>> Dave T?ht
> >>>
> >>>
thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks
> >>>
_______________________________________________
> >>> Bloat mailing list
> >>> Bloat@lists.bufferbloat.net
> >>> https://lists.bufferbloat.net/listinfo/bloat
> >>
> >>
> >>
_______________________________________________
> >> Bloat mailing list
> >> Bloat@lists.bufferbloat.net
> >> https://lists.bufferbloat.net/listinfo/bloat
> >>
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.bufferbloat.net/pipermail/bloat/attachments/20150130/5c6d87b2/attachment-0001.html>
------------------------------
Message: 2
Date: Fri, 30 Jan 2015 16:25:09 -0800
From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] New "comcast" tool
Message-ID:
<CAA93jw59ajdqqoFVzvymsi7ADUnJOFMgU-B=yRHiC+Q1Z--ZdQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
I was utterly compelled to file a few bugs on this.
https://www.reddit.com/r/programming/comments/2tz4qu/comcast_simulating_shitty_network_connections_so/
--
Dave T?ht
http://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks
------------------------------
_______________________________________________
Bloat mailing list
Bloat@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/bloat
End of Bloat Digest, Vol 49, Issue 3
************************************
parent reply other threads:[~2015-01-31 21:40 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <mailman.3.1422734401.24961.bloat@lists.bufferbloat.net>]
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://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1422740428.24297.YahooMailBasic@web141604.mail.bf1.yahoo.com \
--to=dhavey@yahoo.com \
--cc=bloat@lists.bufferbloat.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox