You are reading content from Scuttlebutt
User has chosen not to be hosted publicly
User has not chosen to be hosted publicly
User has chosen not to be hosted publicly
@mikey %Iq7LGlI/gcZ91fzR1fmT6lFaRJYTcjUQuipeQ1+UURo=.sha256

Iā€™m concerned that we are both not identifying the immediate cause; and the root cause.

on improving Scuttlebutt, "how hard could it be?"

hi šŸ›

from my experience, i've seen so many butts burn out due from Scuttlebutt's broken developer foundation (lack of specs, mad science reinventions, accrued technical debt, etc), or said another way: the mistaken belief that making (minor or major) changes to Scuttlebutt will be easy. unfortunately, to do anything in Scuttlebutt (even adding a minor feature, or fixing a little bug) requires yak shaving, which is made worse when all the code is split amongst dozens of tiny modules with deep dependency trees. ( %B1ZgTyZ... )

in my mind, the only way out of this mess is to collectively commit to and focus on a clear goal: improving the root foundation on which Scuttlebutt is built, so future Scuttlebutt developers can be happy building apps and things. so far we've been stuck trying to iteratively improve Scuttlebutt, and so far most of our efforts have failed. until we fix the Scuttlebutt developer experience, i think we will continue to see new contributors with bright eyes and bushy tails be in pain trying to add a good-natured user-facing feature, while old contributors who are jaded leave with the only knowledge we have (as how Scuttlebutt actually works is still mostly undocumented).

i do think the underlying protocol of Scuttlebutt is really great, and worth keeping, but we really need to think about what battles are most important to fight. i reckon we're trying to fight every battle and thus losing. i think we should focus on our replication (and maybe our database), and give up on everything else. for example: why do we need to re-invent social media within our messages, why not adopt ActivityPub? why do we need to re-invent our own app themes, why not adopt Microformats? and don't get me started about muxrpc.. šŸ˜ŗ

ā„¹ļø

User has not chosen to be hosted publicly
@mikey %xyeXMOea3qHhHjloQ7ipdAAJTDkSu2bPoVEXZVC0mZs=.sha256

i guess another way to say what i mean, with regards to the original post: i don't think Scuttlebutt contributor burnout is because we're moving too fast, i think burnout happens because contributing anything is so hard, even if the task is small or even if the contributor is very skilled. so to get something to DONE means doing heaps and heaps and heaps of work, most people get worn down, not enough good feels along the way. you want to do X but now you're stuck doing A, B, C, D, E, and Ffffffffff. šŸ’œ

User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
@Anders %GZ5k/w3pjmths0eGSMMtWTW5xw2yUuPhiVxpvhUunr4=.sha256

@dinoworm šŸ› I very much agree to what you said here. I do think that we are moving in the right direction though. I had a ESC call this weekend and after that I wrote down some thoughts very much aligned with this thread and with Bundys burn out thread. The following list is just my random thoughts, so in no particular order.

Good things

  • Working in crews over longer periods. Two recent examples of this: NGI pointer and ahau. There are several advantages to this. First of all working with lovely humans and a daily basis totally rocks. I've been really enjoying working with the rest of the NGI crew. I can see some of the same dynamics with ahau. Secondly this has allowed us to tackle some of the things that would have been impossible or lead to burn-out if done solo like private groups and db2. In the NGI pointer we will be tackling another of the gnarly bits in the JS stack, the dreaded triangle of death that is: ssb-friends, ssb-replicate and ssb-ebt.

  • Manyverse donations has allowed Andre to keep working on manyverse for a long period being paid. This is really important I think and I think it's really important that we either set aside a certain % of the open collective SSBC money or even better create a new OC for whatever client we want to promote as the boring butt client.

  • Paying people for the things we are about. The newsletter is a really important part of the community and the way @elavoie started this and later handed it over to @cblgh is something I think we should really inspire to. Also this is payed which is really important I think.

  • Making a maintainable boring butt client. I've been fascinated to see how many people started contribution to oasis. It's really a testament to a really good foundation that @Christian Bundy has established. Also that we have had multiple people working on in. Both payed and not payed.

  • ssb-js another one of @Christian Bundy great ideas. I think we need go through all the modules on ssbc and move them over and deprecate SSBC. Either that or clean up the people there and move a lot of stuff to ssb-unmaintained. ssb-junkyard was a great first step in cleanup up stuff.

  • dev.scuttlebutt.nz is really great in that we finally have decent documentation and not only for js but also for rust and go. It complements the protocol guide well I think.

  • https://scuttlebutt.nz/ is pretty great as well. Kudos to the people that made it. It could use and update though.

@mix %3MZgWGgxrkDIn4/a+2k2CdJ4aPPp3dcOP0EEldhIvdI=.sha256
Voted > Iā€™m concerned that we are both not identifying the immediate cause; and t
@mix %BCJsQNABUhSP10vzuMkIcmjWGc7UrN0qRSm8gdcAs68=.sha256
Voted [@dinoworm šŸ›](@6ilZq3kN0F+dXFHAPjAwMm87JEb/VdB+LC9eIMW3sa0=.ed25519) I ver
Join Scuttlebutt now