You’re aware that you can send whatever traffic you want over any port right? Using 123/udp for NTP is just convention. A light bulb that is updating its time over Tor is suspect. TP-Link would have their own infrastructure or use public pools to update the device’s time.

It’s been hacked, the light bulb is likely part of some botnet or under an attacker’s control directly. Which is why it’s sending that much data continuously. IoT/smart devices don’t send a lot of data in this sort of volume as most of the time they’re idle and maybe send a heartbeat or status update every once in a while to prove they’re alive.

This is what is called an indicator of compromise or IoC, it’s some behavior or pattern that can be used to determine what is happening or who is the one doing the attacking.

Likely OP would need to do some analysis to be able to get attribution unless it’s a very well known botnet actor in which case attribution is fairly straightforward.

It’s definitely been popped. Rip.

They have beaten this dead horse enough. There’s only so many ways you can make “Something Era shooter” without it literally being the same game with different skins.

The amount of money that comes out with each swing is drying up. Maybe they shouldn’t have tried to extract every last dollar out of their players and their IP and let it end on a high note.

Yes that drive should work, as long as it’s not a SATA M.2 SSD it should be compatible with the Yellow.

Yes there is! Great you have a strong, randomly generated password. There’s no collateral damage (you’re having your password manager generate the passwords right?) So your other accounts are safe, you only have to rotate one password.

Well what happens for instance if someone really wanted access to your account? Say it’s a bank, a social media account, or maybe it’s just a game account for an MMO that’s super high value, you have a long and strong password, but let’s say the service’s security wasn’t quite up to snuff or you got phished and gave your password by accident (these things happen, it’s not your fault).

This is where 2FA comes in, if someone manages to break your password the attacker needs your phone, your security key, your fingerprint, etc… To prove to the service they’re you. By having 2FA on the account you’re increasing your defense in depth for your account. If you didn’t have it your account is as good as gone as soon as an attacker cracks or gets your password.

It acts as a second lock that needs to be picked in order to take over your account.

I personally add 2FA to all of my accounts I can, the highest security ones get added to my hardware token. The ones I don’t need as high security go into my password manager (which has 2FA enabled but only available via my hardware key).

Additionally as often as possible I try to use a unique email address for each service (simplelogin, addy.io, or similar, + based email addresses are easily bypassed) they all forward to my email but now you have to guess my email for the service (my own private domains, so not shared with anyone else) and what mailbox it ends up in. As a bonus you can disable emails that are sending spam or see who got breached based on the email.

Again defense in depth, a long secure password is great but that’s only relying on a single lock. By having 2FA you’re doubling your security so to speak by requiring that extra key in order to access your accounts.

It’s because your nozzle is ever so slightly too low when you’re printing. I’d adjust your Z offset by one click upwards.

Reprint the cube, and see if that resolved it. If not adjust upwards by another click.

If after a handful of times you can’t get a decent ironing pass, I’d take a look at your extrusion multiplier. Drop it down by 0.01 and recalibrate and retry doing the above ironing calibration sequence again.

To be fair most of the class action lawsuits these days are “dumb.” It’s important to still fight these or else nothing will change. It’s a check valve on businesses and the government to prevent them from being completely unaccountable and harming entire populations of people.

They named the feature incorrectly, then they only updated the language and explained it properly after people got in trouble or hurt because they thought it meant something different. That to me sounds like malice or at least negligence to me.

Yes the suit sounds dumb initially. However if you think about how the average person might have been misled this does sound like Google needs to be held accountable.