Closed mixmix closed 1 year ago
Also yeah maybe different conversation but how will ahau do things? Stay on v1 and have 1.1, 1.2 etc?
@Powersource ready for review!!!
Changes made:
group/add-member
schema (Ahau will need v1 + v2)group/add-member
schema
creator
field (in case the person receiving the add-member doesn't replicate the group creator yet, which is needed)groupKey
> secret
(I like this term more now... why not... future mix will hate me I'm sure)bendybutt-v1
(this is the only id used in recps now)decided to undo the groupKey
to secret
change. I wish it was secret
, but it will just cause a cascade of code changes elsewhere which is silly
@mixmix let's get this merged and published :) would be nice to have addMember verification back in tribes2
@mixmix boop
Pubished as v3.0.0
We have a required change to the format of the
group/add-member
message:If we're making breaking changes lets change
groupKey
tosecret
Look at us, version out specs!
:fire: this PR will require us to do some changes to schema in this spec. Will wait for other PRs to settle down. We may also need to keep both version of the spec, i.e. v1 and v2, as if there are json files being pulled in by Ahau for migration