010: thread spec

[mixmix]

No description provided.

[mixmix]

Preview HERE: https://github.com/ssbc/sips/blob/964e9a5cf407f1adf6e26f3b656c0e769f21caf4/010.md

[staltz]

I like the mermaids. 🧜‍♀️

The document needs a little bit of structure, with abstract, specification, etc. Also we need to address those TODOs before merging. And I need to give it a read to make sure it's more prescriptive (telling readers what they should do to implement this SIP) than educational (giving readers a tour through threads world), with some MUSTs and SHOULDs.

[mixmix]

@staltz I want to do the minimal additional work to get this merged.

TODOs:

• I don't know how forks are handled, or what the logic is because I didn't implement it. I don't think this should be held up on that
• channels ... shrug, I don't have energy, but can point to the right code

Prescriptive vs. educational, yes keen to see that done.

Given I don't want to do much more work on this, but we need it written down somewhere, would you be down to pair on this to get it done?

[staltz]

Given I don't want to do much more work on this, but we need it written down somewhere, would you be down to pair on this to get it done?

I'm your inverse, I feel less motivated when I'm pairing to get things done. I suggest we just relax the deadlines with this PR. You (or me) can come back to it some time in the future and finish the TODOs.

[ahdinosaur]

I don't know how forks are handled, or what the logic is because I didn't implement it. I don't think this should be held up on that

for what it's worth, thread forks should probably be a separate spec anyways.

[mixmix]

A wild @ahdinosaur appears! Hi <3
Yeah making it a different sip would feel nice ... or just not requiring it to be in here ...sigh

@staltz can we just merge this. It's better than nothing, and not having it in master means it's not really visible

[staltz]

@staltz can we just merge this. It's better than nothing, and not having it in master means it's not really visible

Nope! Let's please not push documents that have TODOs in them as official specification. If someone really wants to read something in progress, they can just open the "Pull Requests" tab and browse this.

It would also go against the REVIEWING.md which wasn't written in vain, so please don't merge things that are work in progress.

[mixmix]

I want to remove forks from this spec, and merge it
Can we do that @staltz ?
I want to be able to link to this at a stable location

[mixmix]

DONE - removed forks

[staltz]

I'll take a look, thanks

[staltz]

Super sweet SIP. I like how it's complete: specifies msg schemas, specifies how the tangles works, how channels works, how content warnings work etc.

I have a few suggestions to fix before merging, nothing that requires you to write anything yourself, since I put the code suggestions inline. Mostly, there is some ambiguity with the notation [X] which could confuse some readers. That's the most important thing to fix.

Then, there's just a suggestion to relax some MUST to SHOULD.

That's all I have, and then feel free to merge.

[mixmix]

merge squashed!