Launching... Manyverse for iOS!

🔗 App Store Link

More info on the manyverse blog. Enjoy!

@gwil Inside the app in the side menu there is a "report bug" link, that will just open an issue in GitLab: https://gitlab.com/staltz/manyverse/issues/new

@andré

Congrats on this release! I'm really excited and happy to see this.

@gozala I know about Multipeer Connectivity APIs, but I'm under the impression that it's only iOS-to-iOS, and that doesn't really interest me.

@gozala Open Wireless Link looks really interesting, thanks for that link! Connectivity in general is a low-priority for me now that I've worked enough on it that it's good (not perfect!) while there are other parts that certainly not good (such as initial sync UX and performance), those are high-priority.

For some inspiration on how to expose something as a transport, check:

• https://gitlab.com/staltz/multiserver-rn-channel
• https://github.com/staltz/multiserver-dht

If there's native code in C (that's the case for Open Wireless Link), then we would need to create Node.js native bindings for that, see https://github.com/staltz/utp-native-nodejs-mobile and https://github.com/mafintosh/utp-native for an example.

Gratz!!!!

I believe @andrestaltz made the ssb-keys-mnemonic plugin ;)

exactly @Rômulo Alves.

There are 2 problems with sharing the same key across multiple devices:

The unique keys are used to identify you when you are "online" (which we call gossiping). Devices in the network will get confused if they suddenly see 2 devices identifying themselves with the same key at the same time.

There's also the risk of breaking your own index of messages. Each message you create receives the id of the previous item in your database and a time-stamp. If you post a message on device 1 and then post a second message on device 2 (before it has a chance to download message number 1) you'll suddenly end up with a newer message containing an older time-stamp.

I (and most multi-platform users) use 2 separate identities that are "linked" to each other via their bios. I for example have @Hendrik Peter and @Hendrik Peter (Mobile) .