Staking Claims with Scheduled Tweets
shkspr.mobi
Staking Claims with Scheduled Tweets
1–10 of 33 posts
Re: Staking Claims with Scheduled Tweets
#2Smart,
what about using words (like a password phrase) instead of a hash? You can schedule title of the upcoming tweet, so people can like it and "subscribe" to notifications
Re: Staking Claims with Scheduled Tweets
#3My critique of this blogpost will have the sha-256 hash:2738490299aeefee10202fa46283bc856
Re: Staking Claims with Scheduled Tweets
#4My critique of this blogpost will have the sha-256 hash:2738490299aeefee10202fa46283bc856
I’ll post in 25 years in the future once I brute force this hash.
Re: Staking Claims with Scheduled Tweets
#5An old trick to make predictions without influencing the outcome:
E.g. https://twitter.com/gwern/status/1017575588641505280?s=20
Re: Staking Claims with Scheduled Tweets
#6Yeah the key point is:
‘ And, of course, a person can post two hashes – for contradictory messages – and only publish replies one of them. ‘
Re: Staking Claims with Scheduled Tweets
#7patio11 wrote about “dropping hashes” here: https://www.kalzumeus.com/essays/dropping-hashes/
Re: Staking Claims with Scheduled Tweets
#8Smart, what about using words (like a password phrase) instead of a hash? You can schedule title of the upcoming tweet, so people can like it and "subscribe" to notifications
I'm not sure of any hashing algorithms which use words as their output. Or have I misunderstood your comment?
Re: Staking Claims with Scheduled Tweets
#9Yeah the key point is: ‘ And, of course, a person can post two hashes – for contradictory messages – and only publish replies one of them. ‘
Perhaps also state when the reply is coming in the initial tweet so if you don't meet your deadline, people can assume you decided to hide it.
Re: Staking Claims with Scheduled Tweets
#10Smart, what about using words (like a password phrase) instead of a hash? You can schedule title of the upcoming tweet, so people can like it and "subscribe" to notifications
I'm not sure of any hashing algorithms which use words as their output. Or have I misunderstood your comment?
It's just a byte string converted to a hex string commonly. Chunk it into quads of hex and you can index into a 65k dictionary (the OED has more than twice that).