Error listing objects - "listing too many items for gateway-side filtering"

[arrogantrabbit]

@mpw

I’m wondering what led them to the decision to use unlimited prefixes

While I don’t know for sure, I suspect there is no malice or ill intent, they just did not think of this, being busy implementing 4781 features nobody asked for.

@arrogantrabbit

At some point, writing ultra reliable, ultra boring code becomes more exciting than jumping on every shiny new thing. Because stability for years without regressions is way more exciting that any possible fancy new features. New features are (often un-) necessary evil — they destabilize everything by necessity.

You can look at duplicacy and kopia backup programs as illustration. Duplicacy is barely evolves, it’s simple, and solid like a glacier. Kopia exists solely to tickle its developer ego. It shall be in Wikipedia article on feature creep. And it’s unstable, corrupts datastore, and is in permanent pre-alpha for years. Cool features but nobody wants to use it.

Here is a curious discussion on duplicacy forum, in the thread dedicated to harsh critique of duplicacy itself, no less, a tangent about Kopia:

[kopia] suffers from featurecreep (support per file compression algorithm?!), while lacking basic necessities (support for filesystem snapshots), and the UI is written on Electron — just look at resource utilization of a simple two page UI.

https://forum.duplicacy.com/t/dont-buy-this-scam/7617/11

Quite a few folks there expressed the same sentiment — great on paper, unusable in practice.