Hi everybody,

i’m a long time Debian user and, while i’ve always loved the Linux experience, the bluetooth side of things was always a little bit… painful.

Lately, i’ve been digging on how bluetooth on Linux works (i knew about BlueZ, but i didn’t know about HCI sockets, standard protocols for bluetooth controllers, …). Seeing how Android manages to work fine with bluetooth (yes, i know, money and company support, blah blah blah), i was thinking about re-writing the bluetooth daemon, in order to be modern, modular, safe (written in Rust), stable and retro-compatible (exposes the same D-Bus APIs as BlueZ) I already found some documents about HCI socket in Linux, HCI communication with bluetooth controllers, HID standards for Bluetooth, etc…

My questions are:

  • is this a good idea?
  • does somebody want to collaborate?

Thanks for reading.

  • 4am@lemm.ee
    0·
    9 months ago

    you’d be better off fixing the existing project

    by breaking its API compatibility

    wut

    • Kangie@lemmy.srcfiles.zip
      0·
      9 months ago

      You have conflated two statements.

      1. You’re better off not fragmenting the ecosystem
      2. If they decide to go ahead with the rewrite, consider whether or not maintaining API compatibility with BlueZ is actually required / desirable.