@randolo is looking for someone to discuss Scuttlebutt on their podcast.
I have been doing a weekly podcast since 2007 and would like to have people join us to talk about Scuttlebutt and Patchwork. It's called Visions Under Construction, and while it began as a tech talk about VoIP, it changed last year to a more human-oriented chat. We talk to people about their vision of what they'd like to see, what they're working on and how they hope to evolve.
@Stephen Reid shared a conversation with @Richard D Bartlett on Stephen's podcast.
Geeky
@noffle made an indexed-tarball creator.
It's a tar archive, but with constant time random reads & writes & deletions, as well as ZIP-style multi-file support.
@gozala shared a list of interesting programming languages plus thoughts on them.
@Piet has been "...experimenting with using an oldschool relational db for scuttlebutt." Then discovered that SQLite has a JSON plugin that allows you to query stored JSON structures. Needless to say there was much geeking out over possibilities by many people.
@cryptixInTheCloud shared "...a screenshot of tale:net and patchbay running of the scuttle-shell started by patchtron"

@aljoscha forked a post about a database that allows efficient querying of the causal order of ssb messages to not derail the thread.
TLDR: Building a database that supports querying the causal order is not trivial, but possible.
Also...
I finally wrote up the abstract bpmux interface for multiplexing, and bpmux/rel, a concrete protocol for providing this interface over a reliable, ordered, bidirectional stream. In addition to the multiplexing features provided by packet-stream, bpmux has backpressure on all payload data, allows cancellation and closing of all logical channels, and supports heartbeats for the top-level connection, all logical streams, and requests. All of these are required for building robust distributed programs.
There are many details for the curious
@bobhugen has been "...collecting a bunch of related threads about rethinking details of the SSB protocol."
----
These summaries are brought to you by @masukomi. I would love to hear your suggestions about how to make them better, or ideas on things to include.
post 3 of 3