Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is Rumble compatible with SSB (Secure Scuttlebutt) protocol? #59

Open
strypey opened this issue Sep 8, 2018 · 3 comments
Open

Is Rumble compatible with SSB (Secure Scuttlebutt) protocol? #59

strypey opened this issue Sep 8, 2018 · 3 comments

Comments

@strypey
Copy link

strypey commented Sep 8, 2018

Rumble seems to have similar project goals to the Scuttlebutt network, which runs on the SSB (Secure Scuttlebutt) protocol. Is Rumble compatible with SSB apps, and would it be possible to bridge users of the two networks?

@Marlinski
Copy link
Owner

Marlinski commented Mar 11, 2019

It looks similar but Rumble doesn't need the internet infrastructure to operate (though it could use internet link at times). All of the message exchanges are done when carriers of the mobile device (humans, though it could be also a special device) actually meet and the phones being within range of each other can connect. It is not compatible with SSB but I imagine it would be possible to build a bridge whenever Internet is available.

@strypey
Copy link
Author

strypey commented Mar 11, 2019

This is exactly how SSB works too. From the Scuttlebutt Protocol Guide:
"Scuttlebutt is a protocol for building decentralized applications that work well offline and that no one person can control."

There are a number of working SSB clients in use, including Patchwork for desktops, and a mobile client called Manyverse that has a beta available for Android.

The Serval Project is another decentralized comms project that aims to build device-to-device communication, without a hard dependence on a network connection.

I mention all of this not because I expect all decentralized tech projects to fold into one mega-project, I don't. But I do observe that it really helps boost adoption of new comms apps, if their users can connect not only to other users on the same app, but also users of other similar comms apps (shared network effect). I also think it's valuable for groups working on similar projects to be aware of each other so they can clearly communicate their points of difference to users, and maybe even learn from each other's experiments (both successes and failures). Thanks for your work on Rumble :)

@chorliya
Copy link

It looks similar but [..]

looks dead as a doorknob

.o0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants