HappyRedditRefugee

Amazing solution, didn't arrive to that one, I was thinking just making a timing constraint to reveal the number that would make the precaculation practically imposible, but the commitment schmeme is waaaay more elegant.

Where I come from we just take the meat of the fruit and blend it with milk or water (and yes, we call that juice), I you have never try it, go get a ripe mango, blend it with milk and you'll have a delicious smootie, you can use water but imh milk is superior for that use case.

Of cours that is no possible with oranges for example, but there a aloooooot mor fruits than oranges.

If you ever have the oportunity to have some guayaba-milk-juice, don't pass it up, the shit is the nectar of the gods.

Not very important, even if generated by a single actor N has not such a big importance. If I were implementing something like this I'd just probably make it -hardcoded-.

If you reaaaallyyyy want to decide on a N on the fly, I'd put a restricction (a<Nx<b) make each participant generate a Nx and then sum then all, -multiply'em If you wanna be hardcore- But I'd be tricky to get it right, for example a party might be able to consistently make N whatever the max value of N is by making their Nx very big -Which, well, I don't really know how it would benefit that party and how would they exploit it-. Maybe using a operation like a XOR on the Nx would be robust enough, and would mitigate the kind of attack that I described above

Tl;dr: you can just have a random party generate it.

1. Decide on a random N and what tails (even) and heads (uneven) mean.

2. Each party generates a random number

3. Combine the numbers with a conmutative operation of some sort, the harder the operation the better.

4. Take the hash N times. (Can be done independently by each participant)

(4.5) optional: for extra robustness, do some hard-to-calculate transformations to the result of 4. (Can be done independently by each party)

5. The final result is either uneven or even === coin toss. (0 will be treathed as even*.*)

This is not infalibe, one party could get all the numbers a precalculate a answer to get a specific result but they will need to randomly try numbers. adding some timing constrains, using big numbers and hard operations would make that sort of attack not really practicable.

Nice question, had fun thinking about it!

Could you dm it to me?

that makes more sense! I was so outraged

Doesn't really apply in this situation, does it?

Early checkout?! I havent been to a hotel that restricts when you can check out, some have just boxes for the key cards.

Hey OP, could you send some links about QAZWSX? I coulndt find anything

Either you run the RP in the VPS and point to the ips on your server or you run it on the server and access it like you are accessing Jellyfin.

Easiest option is a container with Nginx proxy manager (imo) with NPM you can get free let's encrypt certs, but be aware, in case you want automated certificates, NPM will need to run on the machine pointed to by the DNS (in your case, your VPS I guess)

People stop buying things because they've detached from social media

What do you mean by that? Social media is quite popular.

First time I hear that, happend to you?