What would change that to 'very happy' in your use case?
1,533 karma · joined April 20, 2015
What would change that to 'very happy' in your use case?
> Fine, maybe country first
It's an example - limit typing. But adjust it to your own use case.
I do have two friends who like it. Maybe it's subjective?
Either way, I'm very happy people put effort in developing reading aids like this.
I creates a bar management/sales platform for our group of friends. It's self service so people purchase their products on their phone and pay later.
People get... intoxicated... after which passwords appear to become quite the problem. Magic links solved that.
To solve the multi device and in-app browser problem people can also open the links on another device. That'll show a short code they can enter on the original device to actually log in. It's not perfect, but it works.
I do fully agree that passwords should always be an option as well.
I might just be old - when this was done on the CPU.
It is especially painful if (big) companies make big money with your free product.
is also super powerful to put a series of commits on top of a new parent when history has changed.
That happens with PRs and squash merges quite often.
You could put different categories in different shards though, resulting in the same effect.
You can also specify exact=true to do the same on any size, but this can get rather slow when your collection grows.
Disclaimer: I'm part of Qdrant.
It is compatible with pass and uses the very same store.
At Qdrant we do this at scale. Store billions of vectors in a cluster of any size. Also in Rust which turned out to be an amazing choice, and fully open source. It uses various features to keep things performant, such as vectorization (multiple arches), quantization (form of compression) and more.