Well, true, but tyres wouldn't make it a double distance, it's not that simple. The case isn't clear, if course, but the claim says that the odometer tried to reduce the range after it got out of the warranty period.
Not saying anything about the merit of the case, just the the claim itself sounds interesting and that if true, you can't wave it away with "you changed tyres".
Fucking hell, that site a million partners who all have "legitimate interest". I've clicked on like a third of them and then gave up. I don't need their shit.
Now that they have their own Putin, why not?
hunter2
it doesn't look like *s to me
asd
I generally use 2000px on the long edge. That's the limit on 52frames.com and for the rest it's usually good enough.
Not optimal if you want fast loading times, but at least it's good enough to print.
I dunno: double-jointed sadistic french bisexual, struggling for money but overly confident.
You could just block most of the internet services - gmail, youtube, facebook etc under these rules, and then wreak havoc. I bet they'd roll back these laws in record time if someone pushed them to the limits :/
Like others here, I'll almost always do:
I'll frequently also enable Sharpen and either Filmic RGB or Shadows and Highlights, depending on the style I want.
I'll sometimes crop the images.
When I actually want to do manual editing, it'll mostly be a small tweak in the RGB levels followed by Colour balance RGB module. I'll also adjust exposure partially, via masks, and similar other tweaks.
Very rarely ill want to heal something with Retouch.
When I'm really having fun (and time), I'll just go tinker with everything else just to see what happens. It's rare that I have the time, though.
I went a slightly different selfhosted route: I made a website with Public CMS. It's WYSIWYG, simple and straightforward, and just goes to my existing stuff anyway.
For private things its usually a Google photos album or folder.
I mean, often enough even that phone call won't help.
But you're right, as long as everything is working normally, working on premises slows you down to do maintenance, updates etc etc. Cloud (of all kinds) takes that work away and you can work faster. And in the VC-driven daily and eternal grind, moving faster is the only thing that matters.
I'm building a NAS for the first time on my own, so I wanted to share the story so far here.
I'm not a stranger to custom builds, in fact I don't think I ever bought an assembled PC (not counting second hand 386 box a million years ago). But this is my first small, low power build, so it's not perfect, I already ran into a wall (more later).
I base the build on an AsRock mini-ITX board, the CPU is included, it's passively cooled, low power consumption but still powerful for a NAS. I'm sticking it into a Node 304 Fractal Design case. Here's the full list of parts I got:
I planned to have an SSD for OS, these two disks for my photography and media, and then later on expand with more storage (preferably SSD, when I can afford it).
As mentioned, I messed up: the M2 slot on the motherboard is a "Key E" slot. I never bothered with these keys before, so I didn't know that a Key E slot does not have a SATA protocol, it won't take my SSD.
Another thing, the PicoPSU is a 20-pin power supply, and the board has a 24-pin slot. It should still be fine, the specs say that this is still okay, but I'll have to see. According to my back-of-the-napkin calculations, 90 Watts should be enough power for the mobo and CPU, the SSD and the two spinning disks.
Anyway I'll get a regular SATA SSD tomorrow and see how it's shaping up. Let me know if you want me to post more on my progress/end result or if you have any questions.
Taken for the 52frames.com challenge last week. I have a few more shots on my (relatively new) photo site.
Pedometers, you mean?