"Early" vs "Late" is delineated by the start of the seventh month of the year.
All major functionality must be present, but "minor" features (confetti, graph annotations, manalinks) can be broken.
Newly submitted answers must be in the provided format. (Option available just in case this market ends up running long) Also, they will be declared invalid if they are submitted out of order. The Oldest sort must be preserved at all costs.
1,000
3.00@MichaelWheatley I cloned the Manifold repository and set up my own version of it, I was able to create a question, bet on it, and resolve it:
I wouldn't call it completely 'local' though -- I used the Supabase platform for the database since that is what is already built in to the product. The main part is running on my machine.
I think this might count for your market's purposes?
@Eliza I played around with using fully local Supabase and got it to the point where the site was reading and writing from the local database. Not sure if that was required to resolve Yes or not.
@MichaelWheatley was there anything else in particular you needed to see to count as "running locally"?
@Eliza Sorry, I've been a bit busy. That looks pretty good. What were the main stumbling blocks? Was there any breakthrough that allowed it to just get figured out recently?
What were the main stumbling blocks?
Honestly, not much. I downloaded the code and had my own locally running version within 2 hours, including the time required to sign up for multiple cloud services that the project uses. Beyond that most all I had to do was replacing some constants in a few files. It took a bit longer to get the scheduler running locally for whatever reason.
Was there any breakthrough that allowed it to just get figured out recently?
I'm pretty sure the main thing is "no one was trying". Somewhere in the last 6-12 months (roughly), they removed additional dependencies between the various cloud services which certainly made it easier.
What I had:
Main web server running locally
API server running locally
Firebase cloud service for Auth (built-in this way)
Supabase cloud service for database (could switch to local Supabase but not sure if that's intended for production....)
Google Secret Manager for all those secret keys (seems straightforward to rip out and use something else locally if someone cares)
I ran the scheduler locally instead of in the cloud
I was able to make changes to the code and then play around with the results.
I am pretty confident someone who wanted to host their own private Manifold could do so with 1-2 days of work and be ready to go.
The code is not really set up for this but I can imagine someone who cared convincing the team to replace those hard-coded constants with a system encouraging you to set up your own instance. (Not sure if that's something they would actively spend time on though.)
@JamesEdingtonAdministrato Doesn't have to be directly descended from Manifold. But it's hard to imagine someone would converge on all the same major features if starting from scratch.
@marketwise A few people have tried and given up. I'm told their infrastructure is a bit o f a haphazard mess, so it's not well suited to this at the moment.