yes, but there are still some limitations that i've run up against (which i am trying to fix) when it comes to repos with a lot of history.
you can work around this issue by using a lot of small repos, but once you reach a certain threshold it becomes impossible to clone a repo from ssb[0]. going further, you also cannot push repos beyond a certain size[1].
these are sample repos that these claims are true for, but i still have more measuring to do so i can say what the exact threshold is.
i lean very heavily on the tech that i use to find the places that need improvement. that said, ssb is an amazing technology and quite new. it works very well for the social networking use case. with some work, we can make it fast/reliable enough for general applications.
[0]: https://git.heropunch.io/%25SI144KecoPoa4uB8kGGUbC%2Fb6Mb4eP...
"""
If I were to write an internet health guide, it would start with:
“THIS IS NOT YOUR FAULT. YOU ARE INCREDIBLE. THESE COMPANIES ARE BAD AND THEY'RE RUINING EVERYTHING. BUT YOU? YOU'RE WONDERFUL.”
Then the guide would say that it's alright to want to be online, because connection through the internet is good-as-hell. I'd only ask for one thing from the reader: to stop waiting for these companies to get better. Instead, learn enough technical skills so that you're no longer reliant on them.
“You already have all the tools you need, so let's sharpen them!,” the guide would say.
"""
— https://coolguy.website/writing/the-future-will-be-technical...
Scuttlebutt is very good, but it would be cool to generalize it to the multiple-writers situation. Then we could have one standard for decentralized data streams and even currency tokens, without global networks:
"This seems to work well: the SSB network thrives off of being a group of kind, respectful folks who don't push to each other's master branch. :)"
Will this hold if the community expands to 10x or 100x the size? Surely conflicts of interest will arise, or just plain assholery/trolling.