RonSijm

What kinda "multi-monitor" features are you looking for?

I usually use Visual Studio (the real one, not VSCode) - and their multi-monitor support seems fine to me. You can drag out any window component and put them somewhere else in a different screen. And when you drag things somewhere else, you can still snap them back together, so it's really just 2 windows again, not just loose floating boxes.

I suppose in the days of 'Cloud Hosting' a lot of people (hopefully) don't just randomly upload new files (manually) on a server anymore.

Even if you still just use normal servers that behave like this, a better practice would be to have a build server that creates builds, like whenever you check code into the Main branch, it'll create a deploy for the server, and you deploy it from there - instead of compiling locally, opening filezilla and doing an upload.

If you're using 'Cloud Hosting' - for example AWS - If you use VMs or bare metal - you'd maybe create Elastic Beanstalk images and upload a new Application or Machine Image as a new version, and deploy that in a more managed way. Or if you're using Docker, you just upload a new Docker image into a Docker registry and deploy those.

I would assume this just relies on the Discord API being read by the bot - and not on having a local discord installed...

Hmm, well the first round(s) are doable for beginners. If you want to get into programming, these kinda games are a good way to start, since you're getting visual feedback of what your bot is actually doing.

And you can participate in loads of languages, so you can pick anything that you're somewhat familiar with.

However, once you're getting into higher rounds, ranks, and leagues, you'll be playing against other peoples' bots. So obviously if you have 0 experience it'll be way harder to beat people with loads of experience, that understand which algorithms are suitable etc.

But I'd say go ahead and try it out. Its free. Maybe it turns out to be too difficult, maybe you'll manage.

You can use Tblock - Or you can check which router they have, and tell them to flash it with FreshTomato

Then their router can service as a raspi with a pihole: https://wiki.freshtomato.org/doku.php/advanced-adblock

Chaotic neutral: If you complain a lot and keep saying your ticket has high priority, you'll automatically have lower priority than the guy that doesn't really care when I do something

Defragging an SSD on a modern OS just runs a TRIM command. So probably when you wanted to shrink the windows partition, there was still a bunch of garbage data on the SSD that was "marked for deletion" but didn't fully go through the entire delete cycle of the SSD.

So "windows being funky" was just it making you do a "defragmentation" for the purpose of trimming to prepare to partition it. But I don't really see why they don't just do a TRIM inside the partition process, instead of making you do it manually through defrag

If “build the server and client in the same language” is a hard requirement, I believe your only choice is JavaScript…

You can probably also use Java. And I've used dotnet / c# for it. You can build the server in ASP-core, and a desktop client in Avalonia, or a website in Blazor

Like feathering somebody after tar pitting. I dont know what that would’ve meant. Maybe servers ridiculing an attacker or something

Could be a feature where servers would add your IP to a list, and send it to the clients (like a list somewhere in case of a website)

Then clients would start sending random metasploit-esk requests to those IPS

I guess cloud big boys would be using key management systems to move the key off the local instance

Yes, AWS uses KMS - by default everything like RDS is encrypted at rest through the AWS default KMS key (default for your account, not globally default). I'm still not entirely sure what the point is, since once you login to the AWS console, or connect to the database, everything is decrypted by default anyways. So I suppose the main thing it protects from is physical access.

You can make it more complicated by having more complicated KMS schemes, for example, see Demystifying KMS keys operations - That has a pretty good explanation of what KMS is, and the point of encrypted at rest (at AWS).

A reason customers could ask for encryption at rest could be that they want to be in control of the decryption key. Then at any point that would give them the ability to revoke the decryption key, and practically revoke your access to their data

But as @recursive_recursion mentioned, you should probably ask the stakeholder what the point is. 90% of the time the point is just some checkbox on a ISO27001 or SOC2 form. And "really providing any extra security" is not

https://www.consilium.europa.eu/en/meetings/jha/2024/06/13/

In public session, the presidency will inform ministers about the state of play of a legislative proposal to combat child sexual abuse. The proposed EU law would make it mandatory for internet companies to alert the authorities about online child sexual abuse on their platforms.

[...]

eff.org

The Belgian proposal was debated behind closed doors, and civil society groups have only recently been able to even evaluate and discuss the proposal after it was leaked to the press.

A bit of a discrepancy here between how it's framed, "we're having public discussions" vs getting information from a leaked document marked as "Classification: Top Secret – For official use only" - I wonder who's telling the truth here, the EFF, or a Council of EU governments that secretly want to implement mass surveillance.

Also funny how it's always the same playbook. "Lets do this under the under the guise of combating child sexual abuse."

The amount of times I’ve been alerted in the middle of the night because CPU was running high for 5 minutes is too damn high.

I'd suggest to just set up automatons to fix those things automatically. Lets say 80% CPU for 5 minutes it too high. Ok, add an auto-scale rule at 65% CPU for 3 minutes to add an extra node to the cluster to load balance the CPU load

It’s like we’re trying to prevent outages by monitoring for potential issues rather than actually making our system more robust and automate-able.

Like it sounds like you're saying the issues are caused by systems not being robust and lack of automation... If they're this scared of outages and breaking SLA, they should work on having less outages, or having fall-backs when they occur.

But it could get pretty difficult to get management to do this kinda things from random suggestions from some SRE. I'd probably talk with the team-lead about this, and other people in your team, cause you're probably not the only one with these issues. And then have a meeting with the entire dev/SRE team and management to point out it's not sustainable the way it's going, and with suggestions to improve it