Skip to content
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

FLIP 196: Restrict Capabilities Publish #197

Merged
merged 7 commits into from
Oct 24, 2023

Conversation

bluesign
Copy link
Collaborator

No description provided.

Copy link
Member

@turbolent turbolent left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, thank you for opening this FLIP Deniz! 👍

cadence/20230913-restrict-capabilities-publish.md Outdated Show resolved Hide resolved
cadence/20230913-restrict-capabilities-publish.md Outdated Show resolved Hide resolved
cadence/20230913-restrict-capabilities-publish.md Outdated Show resolved Hide resolved
cadence/20230913-restrict-capabilities-publish.md Outdated Show resolved Hide resolved
cadence/20230913-restrict-capabilities-publish.md Outdated Show resolved Hide resolved
@SupunS
Copy link
Member

SupunS commented Sep 13, 2023

What if someone else sends a capability to the inbox of my account, and once I claim it, I want to publish that? I guess that would not be possible with this change?
Not sure if that is even a valid use-case, I'm just asking out of curiosity.

@turbolent
Copy link
Member

@SupunS

What if someone else sends a capability to the inbox of my account, and once I claim it, I want to publish that? I guess that would not be possible with this change?

That would not be possible, but is also not possible with the linking-based capability API.

Copy link
Member

@SupunS SupunS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Being restrictive to start with, is always a good idea!

@j1010001 j1010001 added this to the OKR-23-Q4 milestone Oct 17, 2023
Copy link
Member

@turbolent turbolent left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Accepted 🎉

@turbolent turbolent merged commit 5873018 into main Oct 24, 2023
@turbolent turbolent deleted the bluesign/restrict-capability-publish branch October 24, 2023 18:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants