Show Navigation
Conversation
Notices
-
I may back up, remove and reinstall #Manyverse before I give up on it. A lot of the people I used to see are overly political. I don’t miss that, but I’m interested—or at least I was—in the potential to enable normal (not politically obsessed) people to connect outside of #corpocentric #socnets.
-
So #Manyverse is a client for #SSB, the Secure Scuttlebutt protocol ( see https://scuttlebot.io/more/protocols/secure-scuttlebutt.html ). Read the link to see more about the protocol.
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.
-
They have no way to notify users when there’s an issue. https://github.com/ssbc/ssb-server/wiki/Pub-Servers
Apparently, there was a crashing bug that took down pubs in certain circumstances. Looks like only one pub is currently open to the public.
-
Another issue, which I've observed before. #Manyverse #iOS doesn't respond quickly to user input, so it often seems frozen. I tend to click 3-4 times before I remember to wait for it to respond.
-
In any case, the pub outage tells me that #SSB, in its current design, is unsuitable for connecting regular people together.
Maybe I'll look at #Jami again to see whether it's made progress toward fixing its issues.
Or #Tox, or #Briar.