From: Jonathan Foulkes <jf@jonathanfoulkes.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] COTS router with OpenWrt
Date: Mon, 28 Nov 2016 12:16:35 -0500 [thread overview]
Message-ID: <E3BC6365-C976-4561-A895-FAD842C4BB69@jonathanfoulkes.com> (raw)
In-Reply-To: <CAA93jw5JrLY16PdcyeHAoDkRcNdiPY16nJpq=-46r5+VrD7XbA@mail.gmail.com>
Hi Dave, a special thanks to you for all the cheerleading and pushing you do on this topic.
> I hope that your marketing campaign is being successful on these
> fronts. It has always been my goal to "enable better products", but
> not have the headache of making them myself, where 99.99% of the
> effort is (like in cerowrt), in making everything else "just work" and
> be reliable enough to ship.
I haven’t ramped up the marketing in a big way yet, but what I am doing is quite effective (e.g. click through metrics are 5 to 10x the norm); what’s been most astonishing is the word of mouth spread.
Yes, lots of effort in having a reliable, supportable product.
As you can see from the site, my messaging has been focused on regular end users, using terminology they can hopefully grasp (I get accused of both being too technical and not technical enough, so maybe I got it right ;-)
One area of messaging that I believe members of this list could provide input on is around how to get people to understand that ‘speed’ (line capacity) is not everything. I keep looking for ways to address that and wrote a short post on it: http://evenroute.com/the-last-50-feet/quick-vs-fast
I’ll post more thoughts on the other thread you started.
- Jonathan
> On Nov 28, 2016, at 10:57 AM, Dave Taht <dave.taht@gmail.com> wrote:
>
> On Mon, Nov 28, 2016 at 7:21 AM, Jonathan Foulkes
> <JF@jonathanfoulkes.com> wrote:
>> Thanks for the Introduction Rich, and thanks again to you and many others on this list for all your contributions over the years helping to combat bloat.
>>
>> This product was born of my own frustration with finding a way to help neighbors and family get a simple off-the-shelf solution that even non-technical users can deploy.
>
> I hope that your marketing campaign is being successful on these
> fronts. It has always been my goal to "enable better products", but
> not have the headache of making them myself, where 99.99% of the
> effort is (like in cerowrt), in making everything else "just work" and
> be reliable enough to ship.
>
>>
>> I look forward to participating more actively on this list.
>
> One of my thoughts has been since it has become so difficult in the
> USA for an open source organization to achieve 501c3 status (icei.org
> is now 5 years into their attempt) was to go the 501c6 route, like the
> linux foundation. We now have a reasonable set of companies doing the
> right things for queueing, updates, and so on, that perhaps banding
> together to promote "less lag, regular updates" would be a way to
> support some of the other costs of this effort, such as effective
> outreach.
>
>>
>> Jonathan
>>
>>> On Nov 26, 2016, at 9:08 AM, Rich Brown <richb.hanover@gmail.com> wrote:
>>>
>>> I have been exchanging a few emails with Jonathan Foulkes from evenroute.com. He tells me that his company is installing OpenWrt on a commercial, off the shelf (COTS) TP-Link router and selling them on commercially. His "secret sauce" is an auto-update facility and improved setup software, which includes a rate-detection step that operates continually to adjust the fq_codel parameters to the actual line rate. You can take a look at IQrouter.com, or look them up on Amazon.
>>>
>>> This might be a solution to our current conundrum about not having an easy solution that solves our family's networking problem. I'm going to get one of these and try it out.
>>>
>>> He has been following our bufferbloat and make-fifi-fast work closely, as well as the work on LEDE, which he'll consider once it hits a stable point. I have invited him to join this list.
>>>
>>> Welcome, Jonathan.
>>>
>>>
>>
>> _______________________________________________
>> Bloat mailing list
>> Bloat@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/bloat
>
>
>
> --
> Dave Täht
> Let's go make home routers and wifi faster! With better software!
> http://blog.cerowrt.org
next prev parent reply other threads:[~2016-11-28 17:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-26 14:08 Rich Brown
2016-11-26 14:45 ` Jonathan Foulkes
2016-11-26 19:56 ` Jonathan Morton
2016-11-28 15:21 ` Jonathan Foulkes
2016-11-28 15:57 ` Dave Taht
2016-11-28 17:16 ` Jonathan Foulkes [this message]
2016-11-28 17:40 ` Toke Høiland-Jørgensen
2016-11-28 17:41 ` [Bloat] How to "sell" improvement (was: COTS router with OpenWrt) David Collier-Brown
2016-11-28 17:59 ` [Bloat] How to "sell" improvement Kathleen Nichols
2016-11-28 18:37 ` David Collier-Brown
2016-11-28 18:58 ` Simon Barber
2016-11-28 19:25 ` David Collier-Brown
2016-11-28 19:40 ` David Lang
2016-12-04 16:08 ` Jonathan Foulkes
2016-12-04 22:32 ` David Lang
2016-11-28 19:26 ` Jonathan Morton
2016-11-28 19:42 ` David Collier-Brown
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=E3BC6365-C976-4561-A895-FAD842C4BB69@jonathanfoulkes.com \
--to=jf@jonathanfoulkes.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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