You are reading content from Scuttlebutt
Feed of @xj9

ALL YOUR BASE ARE BELONG TO US

projects

tomo/os - relax - walkaway handbook - walkaway utah

contact

@xj9
Re: %IiJZ/creq
git ssb create --private
@xj9
Did a git update in repo walkaway-handbook
@xj9
Voted #theoutcome I've recently released Anthropocene v0.1.0 Check it out https
@xj9
Voted # Secret Islands Using D3 to visualize ssb activity across a procedurally
@xj9
Followed @mary
@xj9
Followed @Matilde Park
@xj9
Did a git update in repo walkaway-handbook
@xj9
Voted # What are the layers of Scuttlebutt? I'm feeling inspired to write a subj
@xj9
Voted [@andrestaltz](@QlCTpvY7p9ty2yOFrv1WU1AE88aoQc4Y7wYal7PFc+w=.ed25519), if y
@xj9
Re: %Mi10Mjl3R

i'm not super on board with baking everything into the same protocol. #cjdns does the overlay thing already, why don't we use that? secure scuttlebutt and cjdns work well together. i've had a lot of success with my own mesh experiments reaching ssb peers over cjdns plus any other protocol that works over IP.

the approach i'm taking with tomo and relax is similar to the OSI network model. layered protocols that operate on higher and higher levels of abstraction. sometimes making the barrier between established layers works (think ZFS), but i'm not sure that is the case for an ssb-native overlay network. i'd love to be convinced otherwise!

some integration between ssb-server and cjdroute would be cool, but i'm definitely more in favor of making ssb simpler vs adding features to the protocol. the ideal would be a suite of complementary protocols that solve specific problems instead of trying to solve everything all at once.


Show whole feed
Join Scuttlebutt now