• 0 Posts
  • 40 Comments
Joined 1 year ago
cake
Cake day: July 3rd, 2023

help-circle


  • Here is a explanation:

    When you eat, your body process the food and tries to utilize it for different things (Nutrients absorpsion, muscle/fat/bone repair and creation and so on). This processes are not 100% independent and they are modulated via several ways, as an example insulin regulates(or inhibits, depends who you ask) lyposis, which is the fat burning process.

    There are a large number of ways to regulate all of this process and to some extend they all regulate each other constantly.

    Now, the yoyo effect, i.e. ganing lots of ways after finishing a diet: After your body runs in a deficit for a whiley your body is behaving as is food was scarse then, when you increase your calorie intake your body uses its enzymes, hormones and whatnot to assure that the most energy is saved, it can do this, going back to the fat example by raising your insuling levels more than usual and so, storing more energy from the same meal.

    It makes sense from a evolutionary view also, your body can’t try to store everything when your starving, since it needs the extra effort to go get food, then, when you find the food it tries to store it all and also, since it has enough you can spare some hours of letargy, i.e. why peoole get sleepy after a big meal. Also relevant, when you are in a deficit your body starts pumpling growth hormones, even tho it has nothing to grow off, but the hormone is there to kick start creation as soon as some extra energy is avaliable.

    Of course that, compunded with how normally people tent to underestimate their calorie intake is even worst. Which happens a lot.





  • 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)

    1. 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!







  • 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)