Some major concerns with #bichat are the leakage of bluetooth identifiers, range, battery, and the need for location services

On the plus side it's available without any additional device

If nostr:nprofile1qqspp9hkhc9y6lcwesklfmfvs6plzsl0eq0whglvumd2m5hu5ax8anqprpmhxue69uhkummnw3ezucmgv95k6cfwd9hxvme0qyt8wumn8ghj7mmjv9hxwetn09hxxtn5v43kstcpr3mhxue69uhkymmnw3ezummjv9hxwetn09hxxtn5v43kstcsa3stq could include an open relay on their router, we could have mesh comms across ALL nostr apps, with greater range, full end user privacy, and a financial incentive to run a node (if you're on a tollgate wifi you pay sats for internet)

Reply to this note

Please Login to reply.

Discussion

Missing link is wi-fi mesh over bitchat

Could be fixed on the router, right?

No. I envision mobile devices being mesh routers.

Yes, please! Let's make a TollGate compatible client for mobile devices. We are aware of some of the challenges, but we want to help to make this happen.

What are the challenges to enabling mobile as WiFi mesh devices?

Mostly permissions. Apps require user permission to connect to a new network for the first time. Traffic from a mobile access point could be difficult to tunnel through a VPN. Background Mode can be unreliable because the operating system prioritizes the battery over apps.

Ideally such features would be developed at the OS level. However, we also didn't have the bandwidth to go far down the mobile rabbit hole, because there are plenty of low hanging fruits in OpenWRT.

We are looking for mobile developers who know what's the right way forward. nostr:nprofile1qqs9g69ua6m5ec6ukstnmnyewj7a4j0gjjn5hu75f7w23d64gczunmgpzemhxue69uhhyetvv9ujumt0wd68ytnsw43z7tpaud2 nostr:nprofile1qqs8y6s7ycwvv36xwn5zsh3e2xemkyumaxnh85dv7jwus6xmscdpcygpz9mhxue69uhkummnw3ezumrpdejz76jympz