At present, I think most implementations are based on Node.js.
An important thing in SSB is "Pubs". The link above says this:
> "Pubs" are bot-users that have public IPs. They follow users and rehost the messages to other peers, ensuring good uptime and no firewall blockage.
> Pubs have no special privileges, and are not trusted by users. However, because Scuttlebot has no DHT or NAT-traversal utilities, users must "join" a Pub to distribute their messages on the WAN.
Without a lot of active experience with SSB or its clients, it seems that pubs are a weak point and a centralizing influence. Sure, I could host a pub myself, but then I'd need to attract a good sized fraction of the overall SSB userbase, so that those connecting to my pub could find interesting users.
I'll wait another week or two before I completely abandon it.
I should write up my experience with the #SSB network. I'd heard so much about this wonder of #DCO (disconnected operation) and #P2P (peer-to-peer) that I think my expectations were too high.
I'm not very conversational there. I pretty much just read others' posts. I rarely respond or post.
#SSB seems to be a "refrigerator magnet" type of place.
Let me explain that term. When #GD2 sends me some of her artwork, I stick one piece up on the fridge (using a magnet). That's "Look at what [my granddaughter] drew / colored / painted for me". So "refrigerator magnet" is hey, look at what I did.
Copying a 'pub' invite and pasting it into the client is not easy. It took several tries on the Apple iPad, and was only possible by learning to trick the text selection function. On Android, there are some characters in the pub invite that can only be selected if you select all (grabs way more than what you want, leaving you to edit after pasting). I eventually resorted to copying the portion that selected easily, and manually entering the rest.
Each device / installation gets its own individual identity hash. In your profile, you can attach a friendly name, which is displayed to others instead of the full identity hash. Don't try restoring a hash from one device onto another, because the #Secure_Scuttlebutt network seems to deliver everything to the first device and leave the second one alone.
There seems to be a smallish set of users, many of whom are building SSB software, hosting pubs, and building similar #peer-to-peer ( #p2p ) networks.
I am nowhere near an expert with it, and I generally only open the client about once per week. It usually takes a while to update, so at first, the old posts from a week before are all you see.
I’ll have to read more about #Secure_Scuttlebutt to see whether #SSB is meant to allow the same userID across multiple devices. If I get a contact or join a ‘pub’ on one device, is that connection also available on the other?
@dredmorbius with #Scuttlebutt everyone gets what they subscribe to. That's it. If you want to send Y over #SSB, you have to get users to subscribe to it *personally*, not just get admins to federate with it, in case it also contains some X some of their users might want in their timeline. If nobody subscribes to it, it doesn't get propagated. People running #SSB "pubs" can accept or reject a user, but they are not acting a sole gatekeeper for a captive market of users as instances do. @clacke
@paulfree14 hmm. The Firewall does a pretty good job of censoring all the sites that talk about or private VPNs or encrypted communication. I'm not aware of anything specific that's available on these topics from mainland China without a VPN. GH is available here, as is GitLab, so maybe one could search them for some #AwesomeLists, or try tools like #Lantern? Tools that use protocols like #SSB, #Serval, or #Briar that don't need the net to share data between devices could also be useful.
Getting together with some folks to work on some #ssb projects! Set up a pub, viewer, and git-ssb today so we're not freeloading on the kindness of others.
pub: pub.decentralized.with.parts (@fqaUNltSCZmr5Sf7mNmd+nTt66UjaRFXhSa7LTIQ8B8=.ed25519) let me know if you want an invite, I'll be setting up a landing page shortly.
From the #SSB principles stack 1/2: "Tending and pruning are not a stranger's duty, it is through near moderation and free listening that we improve our surroundings. Infrastructure is a voluntary act, multimodal welcoming is how we on-board people via diverse connectivity modes (technological acts of inclusion) as well as with greetings (words of inclusion)." https://www.scuttlebutt.nz/principles/
From the #SSB principles stack 1/2: "We acknowledge the natural, the virtual, and the social environments. Our responsibility is to recognize which resources are abundant, which are sufficient, and adapt accordingly through efficiency.
Technology is simply the means by which we communicate. We use local-first publishing so that each person owns their words and actions. Our solutions are piecemeal upgradeable, replaceable and incrementally improvable." https://www.scuttlebutt.nz/principles/