-
Notifications
You must be signed in to change notification settings - Fork 84
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
Tweetable timestamps #57
Comments
Hmm, that's an interesting idea. What's the limit on maximum URL size for the shortener? |
This doesn't seem to do quite what I want (serialization problems):
|
Mind copying-n-pasting the error message you get? |
@kanzure ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When the proof is short enough, it's possible to link the proof in a URL shortener and post on twitter, including the entire matured timestamp. It would be nice if the client would give me a link in the following format:
This can get URL shortened and the URL shortener stores the proof and gives you a short URL to pass around in public. Fits nicely into a tweet, too.
Also, I believe the serialized timestamp should only include one attestation, not all of the available attestations from the OTS file.
When a timestamp was made from a merkle tree of many other elements, maybe the client should complain to the user and say that a URL shortener will not be likely to accept the input. These services often have a length limit, it's not like they gladly accept gif/webm
data:
URIs.The text was updated successfully, but these errors were encountered: