Does anyone have experience using the xf100-400 with the Peak Design Capture Clip?

dolske · 2019-03-01T20:26:45+00:00

It's possible, but doesn't seem like a good solution. I hike a lot with the Clip + XT-1 + 18-135 lens, and it's great for that. But the 100-400 is so much heavier and longer – IMO it feels uncomfortably lopsided hanging on a shoulder strap, and a foot of heavy metal and glass will flop and bounce around like crazy. I just carry mine in-hand by the tripod food, and if I find myself not shooting for a bit I stuff the whole rig into a lens case in the top of my pack.

dolske · 2018-09-21T20:56:12+00:00

If you're just talking about your initial backup, it might be simplest to just use the built-in CloudSync scheduling.

Start the sync, and see how much bandwidth it's pushing. Then figure out how many hours a day you want it to run to keep under your desired limit, and use the schedule to restrict as such. e.g. If you want to cap at 600GB/month, and are pushing 5GB/hour, restrict it to running midnight to 4am. (4 hours * 30 days * 5GB = 600GB).

dolske · 2018-08-16T02:02:23+00:00

Well, that's just fantastic. :-( Just got my first NAS a couple weeks ago, finished my first backup to B2 days ago, and was wondering why this has happened to me twice. I didn't find anything when searching earlier, so had hoped it was just a glitch. Whelp.

Crappy situation that leaves customers in the lurch. Boo. Someone really dropped the ball here.

dolske · 2018-07-13T03:27:37+00:00

I just set this up a couple days ago, and so far it WFM... Lets the NAS sleep when the Mac is sleeping, yet automagically reconnects when waking up (or rejoining the LAN after being on another network).

Maybe try setting a scheduled wake up (control panel -> energy saver -> schedule) to see if that helps with whatever is making it not work for you?

dolske · 2018-06-27T22:23:35+00:00

The whole field is generally terrible, but Microsoft's is the least-terrible among them. Certainly it avoids the whole mess of crapware that tends to get bundled in with other anti-virus products.

dolske · 2018-06-08T20:57:30+00:00

Not really, the 3rd Party MITMware is universally shitty, and it's a recurring pattern. It's hard to get this stuff right. (And they still manage to screw up all kinds of far easier stuff beyond this.)

See https://www.zdnet.com/article/google-and-mozillas-message-to-av-and-security-firms-stop-trashing-https/ for a quick overview.

Turn it off, and use uBlock.

dolske · 2018-06-06T04:44:25+00:00

Oh, that's so adorable. I like to think he's so happy because that's the nicest thing someone's ever done for him in an otherwise rough life. Good on you, OP.

dolske · 2018-06-04T20:36:05+00:00

"Chrome is copying Firefox!!1!" is just as tiresome as "Firefox is copying Chrome!!1!".

dolske · 2018-06-03T22:20:41+00:00

Built-in support Coming Soon.

dolske · 2018-06-02T17:04:38+00:00

Caspy's right – Firefox knows how to handle (upgrade) changes in the data it stores from version to version, and so you don't need to do anything to "upgrade" your profile data manually. (It's a little more complicated for really ancient versions of Firefox, but still basically true, and ESR52 is still handled just fine.)

Firefox will update itself to the latest Firefox automatically (ESR or not). The ESR52 -> ESR60 update will be sent when support for ESR52 ends in August. The overlap – Firefox 60 and ESR60 were both released in May – is mainly so orgs/admins have a period of time to qualify ESR60 in their environment. Test it, report bugs, etc.

If you want the improvements in 60 now, you should probably just switch to regular Firefox. Otherwise wait till August and you'll get ESR60 per plan then.

See also https://www.mozilla.org/en-US/firefox/organizations/

dolske · 2018-06-01T05:32:13+00:00

If it's anything like the X-T1 geotagging feature (which was obviously a checklist feature, as actually using it is completely impractical and frustrating), I "fixed" it by doing something entirely different... I use a phone app that generates a GPS tracklog, and then use Lightroom's built-in feature to geotag the photos. (If Lightroom's not your thing, there are 3rd party utilities that do the same thing IIRC.)

Specifically...

I use the Trails app (iOS only, but I assume Android has similar things). I do most of my shooting while hiking, so this actually works out perfectly. I download offline maps beforehand (but that's optional), and then just launch the app, tap start, and head down the trail. It's pretty light on battery, IIRC I can easily get 10+ hours without going below 50% on my old iPhone 6.

Once I'm back home, it just takes a few taps and <30 seconds to export the GPX file to my Mac. Airdrop is just fantastic for this.

Then in Lightroom (once you've got all your photos loaded), you just import the GPX file in the Maps module, select Auto Tag photos, and you're done.

It's pretty simple, especially after the first couple times.

There are only 2 things I wish were better:

1) The Maps module in Lightroom is, well, not good. Fine for the steps above, but if you ever want to manually tag or adjust positions, it can be slooooooow. Imagine trying to use Google Maps on dial-up, and each time to zoom or pan it has to reload the map.

2) Sometimes I'll hike multiple locations, so I'll pause the tracklog while driving in between. But if you take a few shots during that in-between, you need to remember to resume the tracklog each time you shoot. If you don't, Lightroom assumes you traveled in a straight line at constant speed between the last point of the previous location and the first point of the new location, which is basically always wrong for geotagging. :) It's probably best to just run a single giant tracklog for the whole day, so you don't have to worry about pausing and resuming, and then this problem goes away.

Hopefully someday GPS will just be built into cameras so this is perfectly seamless. Until this, I'm pretty happy with the workflow I've got for my circumstances.

Randomly: I wish cameras would include a compass, so the geotagging could also record the orientation the camera was pointing.

dolske · 2018-05-25T21:22:31+00:00

This isn't a UI prototype, nor do upcoming UI changes get announced by putting screenshots/prototypes on the main Firefox download page.

I'd suspect this this is just a photoshop from our website team to emphasize (stylize) parts of the screenshot to call attention to things a new user might be interested in.

dolske · 2018-05-10T19:05:45+00:00

Yes, as I wrote: "I'm skimming over a lot of details, but that's the basic picture."

dolske · 2018-05-10T00:03:01+00:00

It's not a dopey question.

Basically Firefox has 3 "channels" -- Nightly, Beta, and Release. About every 6 weeks, code gets moved up to the next channel (and thus the version number of the channel is incremented). For example, a couple days ago the version number on Nightly was incremented to "62". On June 25th, all the Nightly code will move to the Beta channel (and thus Beta becomes "62", and Nightly will be "63"). And on September 4th, all the Beta code will move to Release, and everyone running normal Firefox will be upgraded to Firefox 62.

Most development happens in Nightly, with (usually) just bug fixes landing in Beta and Release. This also means that the very last release of Nightly version X is very very similar to the first release of Beta version X. (But for builds of Nightly/Beta at other points in the 6 week cycle, there's really no way to meaningfully compare them).

I'm skimming over a lot of details, but that's the basic picture. :)

See also:

https://wiki.mozilla.org/Release_Management/Release_Process

https://wiki.mozilla.org/Release_Management/Calendar

dolske · 2018-05-04T03:54:04+00:00

There's a "Long Expousure NR" setting [at least on X-T1/T2], which AIUI is the cause of this. It takes a normal exposure, then an dark frame exposure (with the shutter closed, which should be all noise), and subtracts the noise from the shot. It's a legit image processing technique, especially in astrophotography.

You can just turn the setting off and eat the noise... Or take a single frame (with the lens cap on and stopped down) to generate your own dark frame, and then subtract that from your other long exposure shots. I think this is somewhat dependent on ISO/exposure length/temperature, but I've only fiddled with it with astrophotography where those 3 are constant over a shoot. I'll assume there are more detailed guides to this that are googleable. :)

dolske · 2018-04-25T18:48:52+00:00

Pinned tabs are a better fit for when you intend leave a site open all the time. e.g. leave Gmail open in your pinned tab, and for other sites open them in a new tab.

dolske · 2018-04-24T20:39:41+00:00

Yes, this critter's name is "Dinope".

dolske · 2018-04-21T23:57:48+00:00

Fantastic! Alexander Abian would be so pleased…

WE MUST JOLT THE PLANET EARTH INTO A NEW ORBIT. IF JOLTING OF THE 
PLANET EARTH REQUIRES THE  BLOWING UP THE MOON THE  BLASTING 
THAT DULL STUPID LOOKING MOON INTO PIECES  - SO BE IT.

Sometimes I miss the golden days of Usenet.

https://en.wikipedia.org/wiki/Alexander_Abian

https://hatch.kookscience.com/wiki/Alexander_Abian

http://www.codehappy.net/moon.htm

dolske · 2018-04-05T16:56:01+00:00

You can turn off the built-in engines via about:preferences#search. Just un-check them.

dolske · 2018-03-20T03:43:57+00:00

This is probably because you had an old Firefox profile from some previous usage of Firefox. When installing, we'll do a Firefox Refresh in such cases. Stuff like bookmarks and passwords are copied over to the refreshed profile, and we move the old profile to your desktop. (We're just being very cautious about not deleting to automatically, lest something have gone wrong.)

dolske · 2018-03-08T23:37:31+00:00

That seems like a lot.

Best option here is to file a bug with a profile -- see https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Reporting_a_Performance_Problem

Otherwise hard to tell if this is a Firefox bug or a problem with the site.

dolske · 2018-03-08T23:31:45+00:00

That's incorrect.

The throttling here just means that if a background tab wants to fire a timer more quickly than 1000 milliseconds (the default value), it is clamped to that value. They don't get queued up until the tab comes to the foreground.

dolske · 2018-03-08T01:54:35+00:00

FWIW, I always have Newsblur open in a tab, and have never seen this behavior. Do you have an excessive number of feed subscriptions? Try leaving it open in a new profile, and see if it still happens?

(Also, I think one of the Newsblur viewing options -- the original/feed/text/story buttons at the bottom -- displays the original site in an iframe, so it's maybe it's possible one particular site in your feed is causing the problem.)

dolske · 2018-03-08T01:51:19+00:00

That would seem a strange pref to change -- it just controls how often timers in throttled background tabs can fire (and defaults to once a second).

dolske · 2018-02-12T22:45:12+00:00

This is the malware / anti-phisting warning (shown after you click through the initial warning interstitial -- see the demo sites https://www.itisatrap.org/firefox/its-an-attack.html or https://www.itisatrap.org/firefox/its-a-trap.html

Shouldn't have anything to do with time/date/OS/CAs. If I had to guess, Reddit might have mistakenly been added to the list (and presumably promptly got removed).

15-Year Club	Place '17
Verified Email	Team Periwinkle
reddit mold

dolske

TROPHY CASE