SCP-196

deleted by creator

Not sure why you were enabling HTTPS for a project that was not hosting an internet-accessible service, really. By which I assume you mean the service doesn’t have a publicly accessible web based UI or API component. What were you trying to access and how? The only scenario I could think of for this would be that your custom software relies on HTTPS for secure communication within its own internal network (such as on a VPN) to send sensitive data back and forth between services. In which case that feels like overkill for a college course, since you shouldn’t have any genuinely sensitive data that you need to secure if it’s just for testing and demonstration.

I had a problem and then I tried to solve it by installing a snap package. Now I have two problems.

Also, it’s a movie and these people are actors with no meaningful genetic relationship between them.

You don’t have to censor the word “Fuck.” This isn’t, like, a Christian minecraft server.

Generalizing is fine and a useful tool in certain situations. In others, it’s not, and can in fact be very harmful. It’s also sometimes good to explain why you support one versus the other in a particular scenario. Y’know…because that’s how conversations work.

Crazy that you’re the only person I’ve found in the thread that realizes this. Generational theory largely accepts that the concept of monolithic generations is reductive. Yes, people born in and around the same time can have shared cultural experiences, but the idea that those are what purely shape you ideologically or that you behave as a component of a monolith are ludicrous. And then there’s subgenerations, microgenerations, etc. Just look at the sociological research of Karl Mannheim for a very complex discussion on the topic.

Many of the issues they leave behind are ones that existed when they were born.

I’ve written poorer documentation than this.

“Here is a work around to fix [weird bug in production]:”

“Edit: Disregard the above. It fixes [weird bug in production] but causes [bad thing] to happen.”

“Edit 2: Apparently the first edit is wrong. It doesn’t cause [bad thing] to happen. Bad thing just happened to occur simultaneously the first time I did the workaround.”

“Edit 3: [weird bug in production] has been fixed. This workaround is no longer needed.”

“Edit 4: Turns out [weird bug in production] we fixed is what allowed our systems to communicate with one another. Had to rollback change. Work around is now considered ‘the fix’ going forward.”

“Edit 5: Turns out it DOES cause [bad thing] to happen, but [bad thing happening] is a core component of our system’s design and also PAYROLL NEEDS IT TO FUNCTION?!”