[elfchief]

I've only ever had one problem with Backblaze, in my ... 7 or 8? ... years as a customer.

The problem: The UI for excluding directories is horrific. It uses the Windows "Browse for Folder" *SHBrowseForFolder) dialog, which requires you click down through each and every level of your directory structure to get to the directory you want to exclude. You can't cut and paste, it doesn't start from the directory you added your last exclusion in, it's just lots and lots and lots and lots of clicking.

This doesn't seem like it would be hard to fix, so I'm guessing they don't consider it broken?

If the Backblaze folks are still reading: Could you please, pretty please, with sugar on top, for the love of god, fix your fucking exclusions interface? Please?

[froindt]

I'm baffled that anyone uses that interface! I think it's literally my least favorite interface in Windows.

Is there a saving grace for that browse folder interface? A certain use case where it's really good?

[AlfeG]

>> You can't cut and paste, it doesn't start from the directory you added your last exclusion in, it's just lots and lots and lots and lots of clicking.

But it's not entirely true. You can paste full path to needed folder in input below directory tree. I've used this many many times

https://dl.dropboxusercontent.com/s/58tncadu2z7ix29/bzbui_20...

[atYevP]

Yev here -> if you don't want to use the UI (meant for non-tech savvy folks) we do have advanced exclusions via XML - take a look -> https://help.backblaze.com/hc/en-us/articles/220973007-Advan....

[elfchief]

That's the thing -- I do want to use the UI and I don't want to have to hand-edit XML. I just want the UI to not use the single worst dialog box in all of windows.

I am baffled at why Backblaze clings so tightly to the existing dialog box.