◈ 9ce92808be498e9e05590ff27cbfdfe4
RRC hub: 28c7c1a68c735693aa8e6b8193ed44b2 (join room general)
Forum / Showcase / Retichat-ios Testing Needed

Retichat-ios Testing Needed

Started by jrl290 ·

metrafonic wrote:

Awesome work! I love that you got RNodes working on iOS! I didnt think anyone had a working implementation yet.

Could you allow setting the SF factor down to SF5? The dropdown currently only allows to SF7. Many radios support it and i use that locally

New update has that change now

metrafonic

jrl290 wrote:

metrafonic wrote:
> Awesome work! I love that you got RNodes working on iOS! I didnt think anyone had a working implementation yet.
>
> Could you allow setting the SF factor down to SF5? The dropdown currently only allows to SF7. Many radios support it and i use that locally

New update has that change now

Awesome!

I found the RNode link to be unstable. I do not like that the app has built in hidden tcp client connections to some hardcoded servers. Have them as options that can be toggled off. Maybe they do not exist in this version?

Can you add a way to send an announce manually? Announces are a vital part of a reticulum network. It seems like it is currently on a timer, which does not make much sense. It should be done on interface changes, app start, etc.

edited

metrafonic wrote:

jrl290 wrote:
> metrafonic wrote:
> > Awesome work! I love that you got RNodes working on iOS! I didnt think anyone had a working implementation yet.
> >
> > Could you allow setting the SF factor down to SF5? The dropdown currently only allows to SF7. Many radios support it and i use that locally
>
> New update has that change now

Awesome!

I found the RNode link to be unstable. I do not like that the app has built in hidden tcp client connections to some hardcoded servers. Have them as options that can be toggled off. Maybe they do not exist in this version?

Can you add a way to send an announce manually? Announces are a vital part of a reticulum network. It seems like it is currently on a timer, which does not make much sense. It should be done on interface changes, app start, etc.

Yes, I agree. I will put a toggle on the Default multi connection.

The announce system is on a timer, a rate limiter, and a set of event triggers. Every time an interface comes up, an announce is automatically triggered on that interface. Also when foregrounding the app and when there is a ratchet desync. There are other events, but I can't list them off the top of my head

Tell me about the RNode link. To be honest, the RNode implementation was only just started when I had to do some refactoring on another section of code. Where as TCP connections are designed to be somewhat greedy in favor of responsiveness and reliability, LoRa necessarily has to be much more deliberate with its connection. That hasn't really been addressed at all yet. What are you seeing on the RNode graph when sending and receiving?

Thank you for giving feedback btw, this kind of thing really needs multiple sets of eyes

Post a Reply

Markdown

Supports Markdown: **bold**, *italic*, `code`, ```code blocks```, [links](url)

Log in to upload images

Proof of work verification for anonymous posting

Copied to clipboard