Why allow hiding predictions? That means I can make a bunch of predictions and only reveal the ones that were right.
I don't wanna be a "Korinthenkacker", but "Build in Berlin" means to me the builder has to obey the Law and add an Imprint and Privacy Policy to his site...
Great idea! Just submitted my first pok.
Feature request: User groups and pok access levels. Restrict pok access down to a given set of users. I imagine that a large share of the pok volume does not (and should not) concern the wider public. For example, I could have a group with my buddies, and register a pok wrt my best friend breaking up with their partner.
This group concept could be exploited in the form of a plugin that can be hooked on Slack rooms or WhatsApp groups. Every time a pok is unsealed the Futuure bot could notify the room, letting others congratulate you upon a successful prediction (or the inverse).
Cool stuff. Automates the process we do on Twitter where we post the hash and then a scheduled tweet revealing.
Sadly, a list of hashes isn't that interesting. So it's not that interesting to read current list.
Blockchain is overhypered nonsense 99.9999% of the time. But seriously this is the one in a billion projects where you should use the Bitcoin blockchain as much as I hate to say it
I wonder whether predictions (aka "poks") are stored in encrypted form in their database? Knowing what people think will happen in the future is obviously rather useful information.
It seems like a centralized approach for this topic is not a good one.
Congrats on releasing it! The same idea was on my todo list for almost a decade:)
Have you figured out how to promote it (that's what stopped me from implementing the thing)?
I see that futuure is a tag. What I would do is predict that futuure will still be around in 5 years, and seal it for that long. I might look really smart with no potential downside!
Nice. I did something similar a couple of months ago that posts to Twitter: https://predictionelect.com
Okay, I'll bite. What's the point? My thinking here is "....and? that's it? why bother?"
Ah cool, back in 2012 I was going to build something like this and registered hashservice.com...but I never got around to it.
Though that domain name still has some interesting potential!
One alternative implementation of this which is very simple is as follows.
1. User makes a public declaration to always make a prediction using some platform. Like they release a tweet saying all future predictions will happen on futuu.re (or on a Blockchain)
2. They only release the sha hashes of their prediction to futuu.re, along with a date for that prediction, and users keep the true prediction with themselves. At any time before deadline they must reveal the content to the world and tell futuu.re about it. Futuu.re verifies that the sha matches the prediction and keeps an easy record. All predictions must start with a preamble.
3. futuu.re maintains three counters for a use, one showing the number of predictions made till that time, second showing predictions that should be revealed till that time, third showing the number of predictions that have been revealed . This establishes the long time accuracy of the user.
This way when someone reveals their pok then the public will know whether they tried to fool people because the users trust ratio will go down if they make a lot of predictions without revealing them. This is also more secure since the actual content is never stored on the server.
The only thing that needs to be done is to use a content formatter/validator at the time of hash creation for stylstic reasons and to make it convenient for public to verify the accuracy of the user.