%b1J7PGFi7g7yJkaB+3LK+8+PUebP/A2rn8kgvsKKPO4=.sha256

@Anders1 year ago %b1J7PGFi7g7yJkaB+3LK+8+PUebP/A2rn8kgvsKKPO4=.sha256

Content warning: hardcore fusion dance

  create fusion identity

    ✔ no err for create()
    ✔ 2 messages created
    ✔ correct type
    ✔ 2 recipients
    ✔ secret is encrypted

  invite + consent

    ✔ no err for create()
    ✔ no err for invite()
    ✔ no err for read()
    ✔ 1 state
    ✔ 1 invited
    ✔ 1 member
    ✔ 0 consented
    @ESsX+BEc ─> @gPDLMiFF
      1 fusion
      2 fusion/entrust
      3 fusion
    ✔ no err for invitations()
    ✔ 1 open invitation
    ✔ no err for consent()
    ✔ no err for invitations()
    ✔ no open invitations
    ✔ 1 invited
    ✔ 1 member
    ✔ 1 consented
    @gPDLMiFF ─> @ESsX+BEc
      1 fusion
    @ESsX+BEc ─> @gPDLMiFF
      4 fusion/entrust
    ✔ 1 invited
    ✔ 2 members
    ✔ 1 consented

#fusionidentity

@Matt Lorentz (phone)1 year ago %3HVcA3AC5582yWlXl/0f+SXKUR6VTkxcN0YGlfUPGzQ=.sha256

Post a reply

planetary attachment no.1

@mix.exe1 year ago %+oLaDxlo5vBq2f6JhDEx+02aikqrsYz/uKxEJKTf4j0=.sha256

#ssb-show-and-tell

Really excited about this. @arj and I just had a call where he caught me up on this work. I'm working on upgrading ssb-crut (which this uses), while arj updates some specs.

One of my goals is to get this mainstreamed this year ( @staltz I'm kinda looking at you with your manyvesse multi-platforms setup as a likely target, but we should discuss that ! )

@Anders10 months ago %+Me2V9PJlkX2qi7nut5ytgAuLkh38VKFyD1vjZ6G/1s=.sha256

An update on this is in order :)

After a bit of back and forth we settled on a name for a new concept in ssb-crut. Using nextStepData you can now pass in data to the transformation (what you do with each message of a tangle) that will not be part of the final state. We use this for adding types that makes it easier to reason about the different steps. The whole specification for fusion identity is now roughly 100 lines of code. This takes care of everything from schema validation to checking the logic of who is a member.

I also merged in the latest spec change so that things should be a lot clearer. We decided to focus on the basics for v1, so attestation and redirection is for future versions to spec. That being said, there is code for the current draft of those features in the JS module as well.

The last remaining bit is to come up with a proper way to encrypt things. That one is waiting for a larger db2 refactor to fall into place as part of the private groups work.

User has not chosen to be hosted publicly