-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reel: fixing meta and url scries, token rotation, and extra metadata #279
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Curious what the thinking/need for rotating the token is. Just to explicitly expire an old link?
Anyway, looks fine. Some questions/comments, but nothing hard-blocking.
``reel-metadata+!>(metadata) | ||
:: | ||
[%x any %token-url token=*] | ||
=/ =token:reel (crip (join '/' token.pole)) | ||
=/ =token:reel (crip +:(spud token.pole)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this meaningfully different from the +join
implementation?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this was giving me errors I think? don't quite remember
Co-authored-by: fang <[email protected]>
…nto hm/small-reel-fixes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes still look good. Thank you.
OTT, we weren't handling the grabbing the ID from the path correctly in the URL scries, and the metadata scry needed to be split between old and new versions. We previously weren't allowing you to rotate a particular group's token/metadata. This now correctly deletes the old data from the provider and gives new data, receiving a new token. There was also a small error in the set-ship thread where it had an extra slash. Finally we needed to include more metadata in the fields for invites and the DM we want to send.