Bluetooth as direct reticulum interface #716
-
|
Is it technically possible to have bluetooth as a direct reticulum interface (not for using it to connect to RNode or some other device)? Briar seems to be able to send and receive messages via bluetooth without pairing or any setup (setup that is not the initial key exchange). Bluetooth is available on every phone so I think it will be good if the project can take advantage of this. It will also make playing with this network way easier (and more interesting than just using the tcp interfaces) and maybe more popular. |
Beta Was this translation helpful? Give feedback.
Replies: 9 comments 8 replies
-
|
It's very possible. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, this is correct. If you'd like to see a very rough draft in a
different contact, check out this repo:
https://github.com/regulad/BlueHeaven. Note that the code here is
unnecessary high-level, it's written mostly with Kotlin coroutines. The
final product will be mostly just access through pyjnius.
…On Sun, Feb 16, 2025 at 2:16 PM Linux in a Bit ***@***.***> wrote:
It's in early stages (not public yet), I believe @regulad
<https://github.com/regulad> is working on it.
From what he's said in the Matrix room, it's going to be Android-only at
first, but it will be possible to implement the wire format for other
systems in the future.
—
Reply to this email directly, view it on GitHub
<#716 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMQAOMSXZL5UZF5UCAUHAJD2QDP2XAVCNFSM6AAAAABXGN7WD6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMRRG4YTENY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
With the advent of bitchat, this topic is becoming more interesting. Can we learn anything from the way bitchat is implemented? |
Beta Was this translation helpful? Give feedback.
-
|
As is the decision to develop natively for Apple platforms.
…On Fri, Jul 11, 2025, 7:43 AM Linux in a Bit ***@***.***> wrote:
Ah, but the use of BLE for *everything* is an interesting decision.
https://code.briarproject.org/briar/briar/-/issues/1033
—
Reply to this email directly, view it on GitHub
<#716 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMQAOMWPMP25TKCFP5TVX5D3H6PPPAVCNFSM6AAAAABXGN7WD6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNZTGEYTSNY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
As for things that can be brought into RNS, here's how I see it:
RNS right now needs a little more work on modularity before I can implement
a durable BLE interface. More complex interfaces like BLE and future
self-healing TCPIP interfaces (mDNS-based/DHT-based; like I've discussed in
the chatroom previously) would become cumbersome to develop inside of the
already very mature monolithic RNS stack.
I think the best option is to develop a better method of loading external
interfaces than just loading loose python files from the config directory.
Currently, they would have to be packaged with something like `stickytape`,
and cannot hook into `python4android` properly for distribution with
Sideband. This was particularly annoying when I was trying to use `bless` &
`bleak` for BLE.
In my experience the best option for monkeypatching code reliably into a
python package is something like what discord.py does with its
discord.py-ext packages, where a module in the package like discord.ext is
scanned for any submidules installed into discord.ext.*, where they are
then imported dynamically and made available for runtime use. RNS wouldn't
even have to scan, installed modules could just be declared by the
configuration.
A system like this would also allow interfaces to be developed under
licenses like GPLv3, and would maintain the dependency-free nature of core
RNS.
…On Fri, Jul 11, 2025, 1:40 PM Zenith ***@***.***> wrote:
Despite the repo and "white paper" for BitChat, there is no PFS
demonstrated either. The "perfect" in "perfect forward secrecy" isn't an
adjunctive. It pisses me off to no extent that one of the *worst*
possible implementation of a system can get that much attention in so
little time when it fundamentally fails to understand *what* the problem
with decentralized communications are.
—
Reply to this email directly, view it on GitHub
<#716 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMQAOMWUPJ43X7ENQIYBRC33H7ZIJAVCNFSM6AAAAABXGN7WD6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNZTGQZTCNY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Fantastic view. Maybe this is a solution that itself creates too many
cascading problems.
I also read he ... <sigh> ... 'vibe coded' it.
…On Fri, Jul 11, 2025, 1:40 PM Zenith ***@***.***> wrote:
Despite the repo and "white paper" for BitChat, there is no PFS
demonstrated either. The "perfect" in "perfect forward secrecy" isn't an
adjunctive. It pisses me off to no extent that one of the *worst*
possible implementation of a system can get that much attention in so
little time when it fundamentally fails to understand *what* the problem
with decentralized communications are.
—
Reply to this email directly, view it on GitHub
<#716 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALE3POE6BKKHIPJEXIUV7ST3H7ZIRAVCNFSM6AAAAABXGN7WD6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNZTGQZTCNY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
It's a vibe! 🫂
…On Fri, Jul 11, 2025, 8:00 PM markqvist ***@***.***> wrote:
I also read he ... ... 'vibe coded' it.
As it turns out, the yapping slop bullshit generator, is in fact, a
yapping slop bullshit generator.
https://www.inc.com/chloe-aiello/security-flaws-with-jack-dorseys-bitchat-highlight-a-system-problem-with-vibe-coding/91212412
(archive <https://archive.ph/wip/4TOqR>)
I hope this can provide some clarity for people bitching and whining about
the "No LLM" clause.
Omg. Lol. I stay out of the loop for a few days and this is what I wake up
to.
—
Reply to this email directly, view it on GitHub
<#716 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALE3POHF7OTSKM4ID3JEXQT3IBF27AVCNFSM6AAAAABXGN7WD6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNZTGYZTCNA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
I am interested in implementing a simple BLE interface with bless and bleak that would work between x86 linux computers (such as laptops). I suspect this should be doable, but I wanted to double check that this hasn't already been done or if there are any existing implementations for android that I could start from, in the interests of compatibility. Also, please feel free to let me know if this is a completely useless endeavor or if I should take a different approach. I want too use Bluetooth to connect to an offline computer across the room (the network config and physical setup in our optics research lab prevents WiFi/Ethernet/Serial from being viable). |
Beta Was this translation helpful? Give feedback.
-
|
This is possible, but it wouldn't be easy to fit into reticulum nor
distribute it. Check the comment i left earlier on this discussion about
loading interfaces at runtime.
…On Wed, Jul 30, 2025, 10:52 AM Kaedon Cleland-Host ***@***.***> wrote:
I am interested in implementing a simple BLE interface with bless
<https://github.com/kevincar/bless> and bleak
<https://github.com/hbldh/bleak> that would work between x86 linux
computers (such as laptops). I suspect this should be doable, but I wanted
to double check that this hasn't already been done or if there are any
existing implementations for android that I could start from, in the
interests of compatibility. Also, please feel free to let me know if this
is a completely useless endeavor or if I should take a different approach.
I want too use Bluetooth to connect to an offline computer across the room
(the network config and physical setup in our optics research lab prevents
WiFi/Ethernet/Serial from being viable).
—
Reply to this email directly, view it on GitHub
<#716 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMQAOMXOJ2UP5UBVDID3Z4T3LDLZTAVCNFSM6AAAAABXGN7WD6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGOJTGU2TQOI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
It's very possible.
The only problem is that Bluetooth/BLE was implemented in a way that makes this very hard to do, especially on Android.
I don't have specifics, but I can tell you that others are actually starting work on it ;)