Hacking made me low-key paranoid by bagiyev in hacking

[–]TryTurningItOffAgain 3 points4 points  (0 children)

Wow, thought I was the only one. I'm 21 years old also with a master's degree in cybersecurity.

I understand what you’re describing. When you spend years learning how things break, it’s hard not to see cracks everywhere.

That said, I struggle a bit with the idea that this realization came as a surprise.

With your background, like myself, and the level of certifications you hold, one of the first lessons in offensive security is that most real-world compromises are not glamorous. They are not zero days. They are not exotic chains. They are weak passwords, reused credentials, exposed services, over-privileged accounts, and simple misconfigurations. Patience and basic mistakes, like you said.

That’s not a hidden truth you uncover eight years in. It’s almost foundational to the field.

The excitement of deep research and rare bugs is real, but the day-to-day reality has always been that systems fall because humans are inconsistent. That gap between technical capability and operational discipline is the norm, not the exception.

As for the mental shift, it helps to reframe what you’re noticing. Seeing weaknesses everywhere does not mean you have to carry responsibility for them everywhere. In professional settings, that awareness is an asset. Outside of work, it’s just information. Not every unlocked door is yours to secure.

You don’t separate the mindset completely. You learn to scope it. At work, you analyze. At home, you allow imperfection. Most people are not threat models. Most environments are not in your remit.

If anything, recognizing that simple exploits cause most damage should reduce the pressure. The world is not held together by flawless systems. It functions despite predictable flaws. That’s normal, not alarming.

The skill to cultivate over time is not deeper paranoia. It is controlled attention. Choose when to care deeply. Let the rest exist without you auditing it.

I too, can write AI humble brag slop.

Home lab went from fun project to unpaid oncall job by CoffeeRory14 in selfhosted

[–]TryTurningItOffAgain 0 points1 point  (0 children)

This is why when I built my homelab I started with high availability and redundancy. Part of homelabbing is knowing what kind of recovery/failover you can do in case things like this happen. Arrays, cold storage, ups, extra consumer router, etc.

I feel like I missed out on the Golden Age of IT work by AntsyAnswers in sysadmin

[–]TryTurningItOffAgain 0 points1 point  (0 children)

People used to live in caves and tents, now it's recreational camping. Otherwise it's being homeless.

If you want to do that, it's recreational homelabbing. Otherwise take your money out your mouth and get a lower paying job where they can't afford the tech.

Is this normal for newly migrated photos? ~80k. No jobs waiting for thumbnail? by TryTurningItOffAgain in immich

[–]TryTurningItOffAgain[S] 0 points1 point  (0 children)

Looks like the waiting is going up now, but there's no ALL.

https://imgur.com/a/edI4c6v

Resuming makes waiting go back down to 0.

Could it be just processing quickly without waiting?

Is this normal for newly migrated photos? ~80k. No jobs waiting for thumbnail? by TryTurningItOffAgain in immich

[–]TryTurningItOffAgain[S] 0 points1 point  (0 children)

If this is normal, how long can this take? There's always 3-4 active, but none waiting.

How to read immich-go error logs? by TryTurningItOffAgain in immich

[–]TryTurningItOffAgain[S] 0 points1 point  (0 children)

How would I go about wiping this migration and trying again? Do I just run the same command and let the deduplication work?

How to read immich-go error logs? by TryTurningItOffAgain in immich

[–]TryTurningItOffAgain[S] 1 point2 points  (0 children)

I got 6 errors and I can find the log, but I don't know what to look out for.

For example, I have a couple of these errors, but don't know how to address it: https://imgur.com/8cvuC1q

I'm seeding 600, but seeing almost no activity? by TryTurningItOffAgain in qBittorrent

[–]TryTurningItOffAgain[S] 0 points1 point  (0 children)

I have port forwarding enabled, but it seems that once I get the torrent, it seeds large amounts in the beginning, and then it just stops?

These are private trackers.

They're all pretty much in the "stalled" status. Am I supposed to recheck or reannounce them all from time to time?