• 0 Posts
  • 539 Comments
Joined 3 years ago
cake
Cake day: June 20th, 2023

help-circle

  • With P2P file sharing, your client is sharing the files with random people on the internet and you’re identified by your IP address (or a VPN IP address / seedbox IP address / etc). MPAA hires companies to check for popular content and log the IP address, time, and content shared, and then sends that to the ISP. The risk and issue is sharing content with anyone randomly, since that is how your ISP is informed of the activity.

    With media servers, unless you’re somehow sharing publicly, it’s safe to assume your members aren’t going to report you to your ISP. I guess in theory the ISP could see high upload bandwidth and investigate, but more likely than not, if there are limits, automated systems will just throttle the bandwidth, and no deep packet inspection or other forensics is performed.



















  • I’ve never seen any interview as invasive as this, but i think simple take home assignments are useful to weed out people who don’t have basic skills for the role, can’t read instructions clearly, and/or don’t care enough for the role. It avoids me spending 30 minutes to an hour interviewing them to just reject them.

    The roles i interview for are mid level devops based, and we’ve found that the best way to do this is to provide the candidate a simple git repo with 2 branches, which can’t be merged due to a merge conflict of two text files; no coding required. Just asking the candidate to resolve the merge conflict and write a README with the steps taken is enough to have more than half of the candidates unable to complete the task. If we interviewed all those candidates first, and then had to reject them, it would probably be 1 full working day per month in aggregate that would be utterly wasted.