It’s probably part of the great filter.
It also goggles up tape measures.
It’s probably part of the great filter.
It also goggles up tape measures.
I haven’t played TF2 in a while (before f2p?), my understanding is that community servers were mostly fine and how we’re mostly on random casual games?
At least this game has a dedicated server option, contrary to the other TF2.
Amazon can get fucked if they try and retaliate.
LinkedIn is such garbage
[Object][Object]
You’d think so, but no.
Short story is the ‘nominal’ size is the size before going into a planer to smooth the faces.
Yes, it makes little sense, like many things related to construction stuff.
parents ahould get their information from likeminded facebook groups (totally not propaganda)
The classic No Giant Eagles In My Backyard
sleep deprivation and coke would explain so much
Sounds dangerous.
There’s hope though, I’ve desensitized our mister cat over the years and you can now safely rub his belly (mostly).
Sad that this is even a thing to begin with.
Well I feel wooshed
Almost looks like Daniel Radcliffe
In true open source fashion, git clone and compile print it yourself?
Ultimately, do whatever you think you’ll be able to keep up with.
The best documentation system is useless if you keep putting it off because it’s too much work.
It can be in git even if you’re not doing ‘config as code’ or ‘infrastructure as code’ yet/ever.
Even just a text file with notes in markdown is better than nothing. Can usually be rendered, tracked, versionned.
You can also add some relevant files as needed too.
Like, even if your stuff isn’t fully automated CI/CD magic, a copy of that one important file you just modified can be added as necessary.
Also, the crackling might be something about the sampling rate. It’s been a while since since I poked around with audio, but I vaguely remember changing the default sampling rate and restart pulseaudio or something like that.
In my case, I think the onboard audio device is in the same group as the motherboard chipset, which would explain the host crashing when passing through.
If I’m honest? probably nowhere near enough.
The 46 hours is assuming it moves at 300mm/s on that axis for 46 hours, which just isn’t the case.
I say this, but as a ballpark figure this is still useful. Even if typical prints probably take longer than that to reach 50km on an axis, that still tells me I certainly don’t lubricate them as often as I should.
Maybe that’s something printer firmwares could one day be modified to calculate and warn the user about.