Dear leader, where is this community platform you were talking to @ODELL about? In all seriousness though, inspiring chat. I have a good idea I want to vibe code tomorrow, it’s like cashapps new pooling feature, but for backup keys & blind signing (eventually) with friends / family / reputable people you trust. You dig?

Amazing work @calle! I'm trying helping porting some iOS features to the android app, made a PR yesterday, planning on continue tomorrow. Interested in this kind of help? Or maybe focus in other parts of the app?

thank you for using kotlin 🤙🏾 i'm a tap in

Installed fine from APK on GoS. Couldn't test in a mesh because the iPhone version requires iOS 16 and my ancient iPhone 6 doesn't support it. @jack Looking forward to its supporting meshing over Wi-Fi. I always have Wi-Fi on, bluetooth very rarely.

Zapstore updated?

It's working!

absolutely! appreciate it

It's in the works. I dig!

What are you using to “vibe code”

Sounds cool but I have no Bluetooths frens close enough but the household. We would just walk to each other to talk. Assume this is a city folk thing where humans are stacked on one another? In suburban semi-rural areas would there need to be BT transmitters or some shit?

BT can barely do 10 metres. spending so much energy supporting this method of connectivity for a telecoms protocol is retarded not surprised such retardation is trending on primal. someone is blowing the dog whistle for them

Listen to his ep, he explains the approach I will take. Cursor and goose

This is the message I got after a few seconds opening the app on a Graphene phone. Downloaded from Aurora store. Is there a way around this or maybe I should download the APK file instead?

Would it be better to create something like meshtastic that uses lorawan than this ?

the main thing is you all are gonna have to have another device to do it, there are a few phones with the capability but they tend to be expensive, mainly military use. i hate to break it to all the mobile device lovers that almost nobody has devices that are going to enable it. most public wifi networks have wifi isolation which means they refuse to route traffic between nodes on the network. specialised small devices that create meshes could be used but they essentially would be your uplink to an internet connection and have mesh networking between them, and then clients would connect to the mesh nodes like regular wifi. i'm happy about this, personally, i hate mobile devices, because the way that military and industry have set things up, they want to use it as a funnel for your attention. so, yes, it would require secondary devices to enable it with regular domestic wifi capable devices.

Apk file straight from github

many more restrictions on wifi and battery drain. probably won’t do it. bt+relay suffices.

Could this be mesh extenders which will work for Bitchat, Briar and Reticulum at the same time, or does it need to be specialized for bitchat mesh only?

I tried to emulate what @jack did (Swift, iOS native first), even though I had never used that framework before. I got a rough skeleton here @calle!

GitHub

GitHub - kiwihodl/SatsAt

Contribute to kiwihodl/SatsAt development by creating an account on GitHub.

It’s where you collectively store your sats at, because sats > bits. People can join a group, when all the members are there we will add a key each, the creator of the group sets max members and threshold. Will make it so you can whitelist outbound addresses. You use NOSTR creds for signing in, it saves to keychain. Encrypted DMs, add your own lightning nodes details so the group can save in sats on chain or lightning to hit their various goals. All in a days vibing!

No clue, I think the concept is great for certain geographies. Just not ideal in others. I know many with land that would love to have com towers to share data.

it would just be a router