I want to participate, but periodically I check https://www.scuttlebutt.nz/faq/applications/multiple-devices... and it hasn't changed, and for me, having a single device to which the entirety of my identity is tied is a non-starter. Even so, the tech seems interesting, and I hope that limitation goes away one day.
Solution ive seen many of the serious users use is raspberry pie running patchfoo at home and connecting to your rpi.
Added hustle and you are basicaly centralising it for yourself.
re size: you really don’t need _everything_ locally all the time. You can delete unused blobs easily, which take up most of the space.
It’s all very implementation specific as well.
This doesn't work with multiple devices, since they'll be two different logs. However, there is ongoing work to support multiple identities. One identity could broadcast that another identity is a "sameAs" - causing friendly peers to sync with the other identity as well.
Personally, I haven't found this to be a problem. I find separate identities less distracting. (My favorite reason to use SSB is that continuous syncing is not an expectation.)
Their plan is to support this at a client level: you create multiple identities with metadata indicating that all are the same person on different devices, which clients can then use to group them appropriately in whatever way makes sense.
UX wise, it may make sense for some clients to obscure this architecture from new users somewhat and treat them visually as the same identity, but that's down the line (and I'm sure some purist clients will never want to do this).
The SSB protocol and feed database are both very flexible and can be used in the way you want if someone builds the app for it.
hmm.. at it's core it's just a database (that syncs across the friend graph), you might find cel's work on git-ssb and ssb-npm-registry interesting. you could just as well make something like discourse ontop of it.
we are currently discussing something more _groupware_ like to remove the dependency on github for issue tracking.
I'm mainly making the point that their landing page has done a pretty bad job of explaining and selling the product.
Does the sync allow for deletion too?
there's talk of moving message content out of the sigchain so you could "delete" (ask your peers to delete) a post: %QJEpN8LN1t3BrIkUQ3WoOMWRsMArbVUZCpTeBYcuqfw=.sha256
Other systems all use some variant of immutable data structures (hashes, append-only logs, DAGs, etc.) vs CRDTs which can do immutable OR mutable data.
Also, you could join as many "pubs" as you like - based on your interests. You'll start receiving feeds from other people who share the pub, and their friends as well.
Is this a feature of SSB or a bug? I mean once I'm in the network and well-entrenched, I could see it being a feature. But how do I even get to that point? (Oh and does Manyverse address this at all? Sorry I don't have Android.)
Manyverse is the first SSB app that implements DHT invites: https://gitlab.com/staltz/ssb-dht-invite and the plan is to make it easier for anyone to invite anyone else, so that we rely less on a single "cluster". We want to get to the point where there are isolated islands of SSB networks.
But the point you seem to be talking about is also discovery, e.g. something like a "search" feature for friends. We don't have any idea in mind for that, and we also question whether that's necessary at all, specially as we seek to bring this app to countries with limited or no internet access.
> Manyverse is the first SSB app that implements DHT invites
Ok - this is cool! I can see how SSB/Patchwork/Manyverse could be used to replace old invite-only forums (which I've enjoyed with 'real life' friends in the past.)
So, yes, I do think discovery is a huge problem for SSB (and Dat, too) because one of the blissful (and terrible) things about the Web is that arbitrary people can find each other. This seems to be an even bigger problem now that certain networks are massive in scale - so the 'island' approach is one that excites me. Not sure about 'isolated', though. With Patchwork, I begin to wonder why I'm able to read things that I can't respond to - and then I realize that I probably don't want to anyway. I may just not understand the whole thing tho. :)
The DAT link is dat://520a00daf0a309bef7722b3f3338854e9da667d01e48dc7b83b118d86354d6d3
The DAT Installer is here: https://github.com/staltz/dat-installer
[1] https://twitter.com/manyver_se/status/1044569401595514880
Can also be installed via Dat Installer https://github.com/staltz/dat-installer (yep that's right, you can install a decentralized app through a decentralized app)
[1] https://dymaxion.org/essays/briarvision.html previously discussed at https://news.ycombinator.com/item?id=18027949
[Cabal]: https://cabal-club.github.io/
There seems to be a large overlap between the SSB and Cabal communities.
Scuttlebutt is a social network platform where each uxer has a personal diary where each page is a signed message that links to the previous page. to receive updates on someone's diary, you follow the person. on each page, content is free-form. the most common message type is 'post', but there's a chat app (similar to Cabal) that uses message type 'scat_message': https://www.scuttlebutt.nz/applications#scat.
Cabal is a chat app, built using the Dat protocol (https://datproject.org/). Dat has a similar architecture, except the diaries (sigchains) are centered on content rather than people. so to receive updates on a diary, you follow the _content_, which in Cabal is a chat group similar to a Slack group.
many.butt.nz:8008:@o3OcykTU7zdsm+WKoGl74XAoyDI/SWlVbIeyHHinQXQ=.ed25519~Se1dEm/vb/9c/pKs9eqGY7514p0b7KdR5/+myMIKCKo=
welcome to the 'verse! ️️
I am sorry to ask these (I guess mundane) questions here but I tried the docs and it isn't really clear. Also patchwork desktop app brought my laptop to a standstill so couldn't explore much.
"Unfortunately, your email to GitLab could not be processed. We couldn't find the project. Please check if there's any typo."
Also, are issues turned off on the repo?
An authority could shut down a pub, or stop a feed from propogating if they really wanted to, over a channel they control. But they can't really stop every single comms channel.
