Conversation
Notices
-
A discussion on why #ssb is still invisible:
http://evbogue.com:8807/%256h%2BVQMd3pTViGvMZ3yk9bdxJWpv2CqaT3QZH8Hk6DF8%3D.sha256
> That Mastodon guy turned GNU Social into a giant phenominon with 1. catchy name 2. a nice accessable interface 3. pictures of cute elephants.
Yup. What SSB needs is hype, usability (including #userops) and PR.
Also, a more official linkable gateway than random friendly user's instance on port 8807.
viewer.scuttlebot.io is official-looking but often unresponsive.
In my Copious Spare Time, I will make an OStatus/ActivityPub bridge, including general web bridge. Right after I finish my other vaporware project. Right after I learn all the OStatus ropes by digging into #pleroma.
I checked out the Pleroma repo 4 months ago. That's a start.
-
http://dci.mit.edu/decentralizedweb , or really http://dci.mit.edu/assets/papers/decentralized_web.pdf (pdf) seems an interesting read. Good to see big places like MIT caring about re-decentralization enough to have a specific site and project for studying it.
-
> The projects they profile are, I believe, the “spanning set” needed to illustrate all the advantages and obstacles to the distributed web that they wanted to cover. I’m reading their report (slowly) and want to complete it before responding, because it’s making me ask a lot of questions about SSB/Dat. They use these handful of services to illustrate some really interesting pitfalls—how does curation work, why don’t they collaborate/interoperate with existing centralized networks versus competing with them, how do they prevent re-centralization, how are hardware costs shouldered, etc., and of course also onboarding as discussed above.
https://social.heldscal.la/url/730840