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.

Sign up for GitHub

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

Jump to bottom

Naming? #5

Open
twiss opened this issue Sep 28, 2023 · 2 comments
Open

Naming? #5

twiss opened this issue Sep 28, 2023 · 2 comments

Comments

@twiss
Copy link
Owner

twiss commented Sep 28, 2023 •
edited
Loading

The working title "Source Code Transparency" may be confusing since what we want to hash & publish is not necessarily the original source code but rather the "compiled" web bundle that's distributed. If we go the route of hashing web bundles only, perhaps something like "Web App Transparency" or "Web Bundle Transparency" might be better?
@estark37
Copy link

estark37 commented Nov 6, 2023

Another (small) factor to consider about the name is that it's tempting to abbreviate Source Code Transparency as SCT, which is confusing given the overlap with Signed Certificate Timestamps in Certificate Transparency :)

@twiss
Copy link
Owner Author

twiss commented Nov 7, 2023

Right :) Another option to fix that could be just "Source Transparency (ST)"? ("Code Transparency" would have a similar issue 😅)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@estark37 @twiss