HN user

nigma1337

88 karma
Posts0
Comments50
View on HN
No posts found.

In the mild case, the common side effects are blunting of your emotions

Isn't this the primary effect, more than a side effect? Atleast in my case, it's been super helpful, going from jumping between a 1 to 7 in mood, to just lie around 4-5-6.

XML is the future 3 years ago

I have such a fear for this, that things i invest time/energy into today will be obsolete in half a year, and my time would be essentially "wasted".

As others say, learning the fundamentals will, and trying to get some more general skill out of every tech fad.

(although, full rewrite every 6 months is excessive imo)

I recently wrote my first PAM module, using pam-rs[1] so i could do it in rust.

It was a learning experience, a rather enjoyable one though. While going down the rabbit hole, I feel even deeper when my module kept halting in openssh, due to a bug[2] from 2018.

I didn't really feel the pain of debugging the author had, most likely just because my application was simple enough to be tested via log statements though.

[1] https://github.com/anowell/pam-rs [2] https://bugzilla.mindrot.org/show_bug.cgi?id=2876

I've only had one experience with azure support, Back when i was first getting into cloud/playing around with servers, I had forgotten to shut down the VPC i rented there, and I ended up with a bill of ~100$, which is a decent chunk for a student.

Wrote to support, explained my situation, and they removed the bill without any hassle.

My credentials are deactivated when I'm not using them.

This sounds rather interesting, mind elaborating how its done? How would they activate when you use them, but not if anyone else does?

It does also seem like the reporter was extremely careful as to not accidentally access user data

After seeing the pings, I immediately turned off the replication by executing the redis command REPLICAOF no one\n\n. No information from your redis server has been replicated to mine as I used nc and I got only the ping messages.

ofc it's real. They're saying "at this date, we wont update it anymore". The router still works, it just isn't updated anymore.

If i had an old product, there's also some point where i'd say "I wont be updating this anymore", as to phase it out. Expecting something to receive active support forever is unreasonable.

I've spent quite some time on things like cryptohack, and speaking to my cryptography friends, but ECC has never actually stuck as well as this does.

Brilliantly done!

Using it for k8s currently, in a request like

[{"op": "replace", "path":"/spec/template/metadata/annotations/restarted-at", "value": "'$(date -Iseconds)'"}]

to restart/redeploy.