Many ISPs need the kinds of quality shaping cake can do
 help / color / mirror / Atom feed
From: Brian Munyao Longwe <blongwe@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: libreqos <libreqos@lists.bufferbloat.net>,
	Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
	"Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [LibreQoS] making openwisp genuinely usable
Date: Wed, 6 Mar 2024 20:02:58 +0200	[thread overview]
Message-ID: <CAHSdPfatSk+zwOjbak7GuZhCCs0gsEzh7K+fbUH1FdBSdrLhOA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7Wb5UPSa5aF5XMp2YDJh0XHrLJEuFCDxH+3ZuJ1Q5cfw@mail.gmail.com>

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

Hi Dave,

Thanks for this, have shared with various networks in Malawi and Kenya. I
hope some of them join.

Best,

Brian

On Wed, Mar 6, 2024 at 3:57 PM Dave Taht via LibreQoS <
libreqos@lists.bufferbloat.net> wrote:

> I keep trying to connect ISPs and developers to finish making openwisp
> usable, by at least
> gathering together existing UISP and other cloud management software
> users to complain about their pain points to the core openwisp devs.
> Tomorrow, there is this.
>
> https://twitter.com/openWISP/status/1765118727706571041
>
> The amount of vendor lock in provisioning and controllers, needs to
> end. Network visibility needs to improve. And devs need to get paid to
> work on the right problems.
>
>
> --
> https://www.youtube.com/watch?v=N0Tmvv5jJKs Epik Mellon Podcast
> Dave Täht CSO, LibreQos
> _______________________________________________
> LibreQoS mailing list
> LibreQoS@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/libreqos
>

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

      reply	other threads:[~2024-03-06 18:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-06 13:57 Dave Taht
2024-03-06 18:02 ` Brian Munyao Longwe [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/libreqos.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=CAHSdPfatSk+zwOjbak7GuZhCCs0gsEzh7K+fbUH1FdBSdrLhOA@mail.gmail.com \
    --to=blongwe@gmail.com \
    --cc=dave.taht@gmail.com \
    --cc=libreqos@lists.bufferbloat.net \
    --cc=make-wifi-fast@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