From: Frantisek Borsik <frantisek.borsik@gmail.com>
To: libreqos <libreqos@lists.bufferbloat.net>
Subject: [LibreQoS] New devblog: API, Challenges and Licensing
Date: Fri, 17 Jul 2026 21:07:52 +0200 [thread overview]
Message-ID: <CAJUtOOjg-uY1AsoxkO5q8D1OQawXrDy7jDu5=Ck8vVq-xThfMA@mail.gmail.com> (raw)
Hello to all,
Sometimes, technical problems, licensing issues and the need to eat collide
<https://devblog.libreqos.com/posts/0015-free-as-in-freedom/>. API access
to LibreQoS was one of those uncomfortable areas. In this post, we’ll talk
about our design philosophy, competing needs that lead to the separation of
the API, and how we’re working to find a happy medium in release 2.2.
Read more in the latest devblog from Herbert:
*https://devblog.libreqos.com/posts/0018-libreqos-api/*
<https://devblog.libreqos.com/posts/0018-libreqos-api/>
All the best,
Frank
Frantisek (Frank) Borsik
*In loving memory of Dave Täht: *1965-2025
https://libreqos.io/2025/04/01/in-loving-memory-of-dave/
https://www.linkedin.com/in/frantisekborsik
Signal, Telegram, WhatsApp: +421919416714
iMessage, mobile: +420775230885
Skype: casioa5302ca
frantisek.borsik@gmail.com
reply other threads:[~2026-07-17 18:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAJUtOOjg-uY1AsoxkO5q8D1OQawXrDy7jDu5=Ck8vVq-xThfMA@mail.gmail.com' \
--to=frantisek.borsik@gmail.com \
--cc=libreqos@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