Josh @joshuap@mastodon.xyz
Ruby, Linux, OSS Enthusiast and Software Developer. Currently making https://www.honeybadger.io and https://www.exceptionalcreatures.com
Does anyone else wish Firefox's address bar supported readline?
Current status: compiling haskell for days.
Extremely difficult content Show more
Was wondering why pacman started taking forever to download packages lately... mirrorlist was outdated. https://www.archlinux.org/mirrorlist/
Hello Mastodon, been a while.
Alcohol/domestic abuse/advertising/snark Show more
Checking out NixOS. Impressed so far; system config is the only part of my desktop which isn’t checked in to git (and one of the more complicated parts), so having a single declarative config feels like the missing puzzle piece to a fully reproducible desktop. Also love how it manages dependencies. Removing all traces of a package is as simple as removing it from the config and rebuilding.
Hi Fediverse. 👋
I really want to get this :honeybadger: emoji on Mastodon. I use it on Slack all the time and it’s 👌🏼.
Honeybadger t-shirt
What if Mastodon were aware of multiple active accounts on different instances? Maybe you could opt to follow someone everywhere (even if they join a new instance) or just locally (like it does now). Might help more folks join topical instances.
I love that #ff is still a thing on Mastodon, I assume because Mastodon itself doesn’t incessantly suggest people to follow.
"Facebook Dives into Home Device Market with Video Chat Product Named 'Portal'"
"According to people familiar with Facebook’s plans, Portal will be equipped with a wide-angle lens that is capable of recognizing individual faces and associating them with their Facebook accounts."
Fuck you Mark
Changing code comments and no code obviously should cause all passing builds *except* JRuby to start failing on Travis...
...and obv. when I ssh into a failing build and manually run the tests, they should all pass.
Just FYI, the #OpenBSD project knew about the potential harm of #Spectre and #Meltdown 11 years ago
https://marc.info/?l=openbsd-misc&m=118296441702631&w=2
This is before exploits routinely started getting catchy names and even before MySpace was a thing. Let alone Twitter and Facebook was around to share news of the impending CPU apocalypse
Too bad so few people listened
https://mastodon.social/media/I10ysFRGxesWg61C5gU
https://mastodon.social/media/-_luWj8UwuEKaeoIq74
CPU Vulns are now public. There are two distinct vulns, in summary:
Meltdown: Memory accesses executed out of order after faults are leaked into caches. "Fixed" by KAISER at the cost of far slower switches between kernel and userspace. Mostly specific to Intel processors.
Spectre: Speculatively executed instructions on branch mispredictions can leak the address space through caches. No fix available it seems, and it affects Intel, AMD, & ARM processors. Possible to exploit from within browser sandboxes.
Well, I am being begged for “my opinion” on the “30% slowdown bug”… except that I have no info except what everyone is speculating about!
My current thoughts:
1) I hope they haven’t blown one out of my private stash,
2) I’ve been ranting about Intel processors for so many years now that I get to say “told you so!”
Ulterior thoughts:
i) if you really think this is the only surprise in store then you are naive,
ii) Intel will not die, not for this.
Next week I’ll have more time to discuss :)
I read a lot in 2017, but I didn’t hit my book goal. 2018 book goal: 24 books (2 per month). Also want to read more articles/papers (and keep track of them better).
