Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Dave Cohen <craetdave@gmail.com>
Cc: "Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>,
	libreqos <libreqos@lists.bufferbloat.net>,
	"Drew Clark (Breakfast Media)" <drew@breakfast.media>
Subject: Re: [NNagain] metro connect this week in ft lauderdale
Date: Sun, 25 Feb 2024 22:37:29 -0500	[thread overview]
Message-ID: <CAA93jw6OpQf-OXyz-HrUUMv0TD2H8Beu-7CTere0GV7tK+yxiw@mail.gmail.com> (raw)
In-Reply-To: <56A3CE3D-DD10-4DD3-82B1-2C6BD444B8E2@gmail.com>

On Sun, Feb 25, 2024 at 10:11 PM Dave Cohen <craetdave@gmail.com> wrote:
>
> Metro Connect is the money conference. There’s a heavy investor (PE/analyst/etc) presence there so it’s always been the one show that our CFO or Corp Dev people would go to. It’s not exactly a technical audience but the panels will generally veer towards “how are we deploying our capital”, which may touch on the parts of the “state of the fiber market” that interest you, or they may not. The one thing that may make it valuable is that it’s US-centric, unlike the other industry boondoggles like ITW or PTC. My 1.5 cents says not worthwhile but I also can’t speak to exactly what conversations or audience you might want to be busking for.

You think these sort of folk might be interested in something that
offers more consistent latency over fiber, at 30 cents of CAPEX, and
makes for better wifi?

I've got a new supply of libreqos stickers, and a freshly washed
"bandwidth is a lie' t-shirt, and it is only a 2 hour drive. Hallway
track might be fun.

>
> Dave Cohen
> craetdave@gmail.com
>
> > On Feb 25, 2024, at 9:01 PM, Dave Taht via Nnagain <nnagain@lists.bufferbloat.net> wrote:
> >
> > I am in general leery of attending conferences that cost $2k. Usually
> > when I get attracted to one of these, I end up sitting outside, and
> > busking with my guitar with a stack of bufferbloat books, and trying
> > to get in on the hallway track, rather than actually getting inside
> > the door.
> >
> > But the state of the fiber market, as it perceives itself, is on my
> > mind. Is anyone going to this? I'd enjoy a day spent wandering around
> > here:
> >
> > https://events.capacitymedia.com/event/4fb357d0-6f2e-41cd-aa19-2565077ec3fc/websitePage:cbbfe534-365b-496f-885e-9f78b584a0f2
> >
> > The last time I did the busking trick I netted 70 bucks for the day,
> > almost enough to cover my hotel, and the free food was awesome.
> >
> > https://blog.cerowrt.org/post/trouble_in_paradise/
> >
> > --
> > https://blog.cerowrt.org/post/2024_predictions/
> > Dave Täht CSO, LibreQos
> > _______________________________________________
> > Nnagain mailing list
> > Nnagain@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/nnagain



-- 
https://blog.cerowrt.org/post/2024_predictions/
Dave Täht CSO, LibreQos

      reply	other threads:[~2024-02-26  3:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26  2:01 Dave Taht
2024-02-26  3:11 ` Dave Cohen
2024-02-26  3:37   ` Dave Taht [this message]

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/nnagain.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=CAA93jw6OpQf-OXyz-HrUUMv0TD2H8Beu-7CTere0GV7tK+yxiw@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=craetdave@gmail.com \
    --cc=drew@breakfast.media \
    --cc=libreqos@lists.bufferbloat.net \
    --cc=nnagain@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