• 0 Posts
  • 70 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle







  • the result of the sexual harassment investigation they had been carried out is unknown to the public as far as I know (I assume by now it’s concluded).

    I don’t remember where it was posted - maybe a community note on YouTube - but they basically said that the third party investigation they had done concluded that the accusations were unfounded.



  • I don’t know Rust, I’m just here to chill. I can tell you what I would do, and have done, in PowerShell to solve this. From there you can translate that to Rust.

    Let’s go with your limit of 200 requests per second. At the start of the script, I create a stopwatch. Literally, a stopwatch that’s tied to real world time and can be reset. Then, I have a variable that counts my requests. Every time I make a request, I increment it. Before every request, I check if the variable is 200. If it is, check the timer to see if a second has passed. If not, calculate how much time is left until a second has passed and sleep for that amount of time. After doing that check/sleep, reset the request counter and the stopwatch. From there, continue on.











  • kn33@lemmy.worldtoSelfhosted@lemmy.worldShould I bother with raid
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    2 months ago

    It’s up to you. Things to consider:

    • Size of data
    • Recovery speed (Internet speed)
    • Recovery time objective
    • Recovery point objective (If you’re backing up once per day, is it okay to lose 23 hours of data when a disk fails?)

    If your recovery objectives can be met with the anticipated data size and recovery speed, then you could do RAID 0 instead of RAID 1 to get higher speeds and capacity. Just know that if you do that, you better be on top of your backups because they will be needed eventually.