found the cause of the issue. one of the ssds has a heat sink, but it seems to slightly interfere with the cpu cooler. it is likely that the ssd was occationally disconnected because of this.
The attackers get some lil access and then use that to ultimately gain full, remote access to your device.
Meaning they can read and write.
Meaning they can see all your files, watch you work, read your messages, use your keyboard, create new files, and modify existing ones. 😱
@sliminality Don’t forget never updating your OS (who needs security fixes anyway) and your hardware (faster and more power efficient CPU architecture? Nah..) 😂
@Twitch hey there, apparently this password is too easy to guess: «TV@tFf_Cr8hXYDGzZ!Gn9VPj.!U*4fBLfbkZ6h3ybqkgcYKBzwCB*V4r@3RUyGfp2nxnbB!8CBVpERPbddE2ucfBW@Q8RR6b9Qwj»
I wonder how much more complex you want it to be… 🤔
@grossbart That is only the case in lazy languages. In JavaScript, a function that returns an fp-ts Option, returns the evaluated computation. The caller doesn't get to decide anything, all power is still with the function itself.
Are low core web vitals important for internal websites or should I be like... fuck it, FAANG employees don’t deserve it. .. ? The engineer in me says: perf matters! But then, I’m having hurdles placed at every step, and it’s so damn demotivating if I’m the only one who cares.
I reported a bug to Vercel, they don’t consider the bug fix important, but rather… «it will be a “feature update”». As in: Hey folks, we've released a new version, it's got loads of features, such as, it now works as it is supposed. Great feature, y'all should start using it rn.
I love adding workarounds into my projects because a broken build system can't handle perfectly valid filenames.
https://t.co/kIOkISDiP5
Bazel is good for Google and… uhm… nobody else. Stay away from it if you can.
Bazel is like VimGolf for your UNIX-fu, forces you to find creative ways to write build (genrule) scripts:
tar chf - $(locations :src) | tar xf - -C $${WORK} --strip-components=3
There are a dozen ways how to copy files, but a simple `cp` would be too ordinary…
Just because a package is marked as tree-shakeable on bundlephobia, and has a module entry point, doesn’t mean it actually is. The source must also be written as ES module. graphql-tag for example fails this precondition.
@paul_irish@ph1 I couldn’t figure out how to configure Kodiak to auto-accept PRs from dependabot which bump specific packages only (eg @types/*, since there is no danger in breaking something when CI passes)
I try to push code only to be presented by this. Git is GPL, wtf do you want, Apple? Also, it wouldn't be so infuriating if I didn't have to reinstall git (and XCode) after every single system update. Is it so hard to install software that survives a macOS patch update?