timvisee

Dev of Qdrant here.

What would change that to 'very happy' in your use case?

The majority of comments complains about non-USA. But the author clearly states:

Fine, maybe country first

It's an example - limit typing. But adjust it to your own use case.

I've also received about 40 messages, on mail adresses I've never used before.

I have dyslexia, and I hate them. It makes me read slower and not better.

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.

In my 5 years I was basically only allowed to use Microsoft tools. It's one of the most stupid things I've ever seen.

A VPN won't make your route shorter

The email I have in that list is invalid and must be generated. It's on a domain I own.

I'm seriously impressed on how far this has come. Tried a few websites in the experimental mode, it renders quite well.

If not now, maybe in the future

I do have a good use case for magic links.

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 always feel rendering such blurred panes takes quite a performance hit. Do we have any numbers on this?

I might just be old - when this was done on the CPU.

While I agree FOSS doesn't give you the right to users money.

It is especially painful if (big) companies make big money with your free product.

`git rebase --onto FIRST_ID^ NEW_PARENT`

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.

https://stackoverflow.com/a/29916361/1000145

Does it still do this when piping into things?

It does for me. Firefox on Android.

I don't like this kind of smoothing at all. It feels slow to me. Please just toggle without animations instead. And yes, I know these examples have been slowed down.

Qdrant does this as well, with 100% accuracy. But it's not on small categories, but rather on small segments.

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.

And auto vectorization isn't all that common. In many cases you need to structure your code in a certain way, in which case you're better off doing it yourself if you want the vectorization benefit.

With regards to competitors picking similar things up, we've this article explaining why a dedicated vector search service is a good idea: https://qdrant.tech/articles/dedicated-service/

Fun fact: if you don't want to put a command in history, prefix it with a space. This works in many shells.

It handles 150k messages in a folder without a sweat for me. Do you have more?

Black Mesa (the game) is also factastic. Highly recommend!

Another good reason to allow other browser engines on iOS devices.

That would make it a bit harder to link to you, but definitely not impossible. It would definitely have been better to not do it at all.

I think it shouldn't be in this article at all. You're comparing a tool that is not optimized nor efficient in any way against others that are. That while Qdrant has a very well optimized offering as well. This is comparing a walker against modern cars and paints a bad picture.

I created `prs` which solves a lot of painpoints I had with pass and other clients.

It is compatible with pass and uses the very same store.

https://github.com/timvisee/prs

Awesome work!

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.

https://github.com/qdrant/qdrant

That's weird! A force refresh (CTRL+F5) doesn't work?

That MDN page has a lot of noise and is not straight to the point. I guess that may be a side effect of JS though.

Then you haven't seen Rust's documentation yet.

https://doc.rust-lang.org/std/index.html