General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "jf@jonathanfoulkes.com" <jf@jonathanfoulkes.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] sad news...
Date: Sun, 5 Nov 2023 10:37:17 -0500	[thread overview]
Message-ID: <1C819B8E-03F4-4C52-8D19-B5C7CDD53382@jonathanfoulkes.com> (raw)
In-Reply-To: <B2B80091-F232-4E7E-BAD7-CD3091EC42D4@gmx.de>

Hi All, I’m the founder of Evenroute, and yes, this was a though one to go through.

Seb, I have to say, a big thanks to you for all the great feedback and support you give the OpenWRT community regarding QoS over the years.
You tirelessly reply to the same questions over and over, our product was aimed at making that workload lighter ;-)

> But even in this state they still seem to act exemplary, in posting information how users can switch to upstream OpenWrt.

Thanks for that, as a consumer whose been stuck with many a cloud-service enrolled devices that become a brick as soon as they discontinue it or go away, I was set on not doing that to our customers.
So every running unit a of the end of October was ‘liberated’ and can freely upgrade to newer OpenWRT if and when they chose to.

And yes, few options out there, it’s rather puzzling.

If anyone is interested in discussing the assets (the IP is three patents, a trademark and of course, the code), please reach out to me.

And thanks to the many of you who have encouraged us and supported us over the years, it means a lot.

Jonathan Foulkes

> On Nov 5, 2023, at 9:37 AM, Sebastian Moeller via Bloat <bloat@lists.bufferbloat.net> wrote:
> 
> ...it seems the evenroute closed shop, see:
> https://evenroute.com
> 
> they were IMHO a trail blazer in turning what we learned about bloat and how to ameliorate into a product that one could recommend one's not tech-affine family members in good conscience.
> 
> But even in this state they still seem to act exemplary, in posting information how users can switch to upstream OpenWrt.
> 
> That leaves only few options, covering the same group of users... 
> 
> Regards
> 	sebastian
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat


      reply	other threads:[~2023-11-05 15:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-05 14:37 Sebastian Moeller
2023-11-05 15:37 ` jf [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/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=1C819B8E-03F4-4C52-8D19-B5C7CDD53382@jonathanfoulkes.com \
    --to=jf@jonathanfoulkes.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=moeller0@gmx.de \
    /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