34 lines
5.4 KiB
Plaintext
34 lines
5.4 KiB
Plaintext
|
ó
|
|||
|
|
¾^DjÅ ã ó0 • S r SSKrSSKJr " S S5 rg)uƒ Reticulum adapter — wraps RNS + LXMF (the standard host-side Reticulum
|
|||
|
|
messaging stack; see docs/ARCHITECTURE.md for why archy-messh talks to a
|
|||
|
|
real RNode-flashed radio via RNS rather than reimplementing Reticulum's
|
|||
|
|
wire format from scratch).
|
|||
|
|
|
|||
|
|
Reticulum has no built-in broadcast-channel concept the way Meshtastic
|
|||
|
|
("channel" PSK) or MeshCore ("public channel index") do — LXMF messaging is
|
|||
|
|
addressed point-to-point between Destinations. To bridge broadcast-style
|
|||
|
|
text, this adapter tracks a roster of peer LXMF delivery destinations
|
|||
|
|
learned from their announces (any Reticulum/Sideband/NomadNet/MeshChat user
|
|||
|
|
who has announced is added), and fans outbound bridge messages out to that
|
|||
|
|
roster individually. This is the simplest correct v0; a dedicated shared
|
|||
|
|
GROUP destination (symmetric-key, closer to a real "channel") is a known
|
|||
|
|
follow-up once Phase 0 proves the roster approach works at all.
|
|||
|
|
é N)ÚCallablec ó‚ • \ rS rSrSrSr SS\\\\/S4 S\S\4S jjrSS
|
|||
|
|
jr SS jr
|
|||
|
|
SS jr S
|
|||
|
|
\S S4S jr SS jr
|
|||
|
|
Srg)ÚReticulumAdapteré Ú reticulumz
|
|||
|
|
lxmf.deliveryÚ
|
|||
|
|
on_messageNÚ storage_pathÚ display_namec óÆ • Xl X l X0l S U l S U l S U l [
|
|||
|
|
5 U l [ R " 5 U l
|
|||
|
|
U R U l g ©N)
|
|||
|
|
Ú _on_messageÚ
|
|||
|
|
_storage_pathÚ
|
|||
|
|
_display_nameÚ_routerÚ _identityÚ _destinationÚsetÚ_peersÚ threadingÚLockÚ_lockÚASPECTÚ
|
|||
|
|
aspect_filter)Úselfr r r
|
|||
|
|
s Ú adapters/reticulum_adapter.pyÚ__init__ÚReticulumAdapter.__init__ sQ € ð &ÔØ )ÔØ )Ô؈Œ Ø ˆŒØ ˆÔÜ"%£%ˆŒ Ü —^’^Ó%ˆŒ
|
|||
|
|
ð
|
|||
|
|
"Ÿ[™[ˆÕó Úreturnc óÞ • SS K nSS KnUR 5 UR U R S9U l UR
|
|||
|
|
5 U l U R
|
|||
|
|
R U R U R S9U l
|
|||
|
|
U R
|