based.cooking VS zr

https://github.com/lukesmithxyz/based.cooking

Good stuff! It looks like you may need to set up SSL certs. I'll also bring your attention to the hugo-driven site, based.cooking, since it is a relatively suckless recipe site as well. Its github repo is here

That reminds me of based.cooking, which is a repository of recipes, but does not really have the family element you were talking about or GPL-3. However your idea seems pretty cool, I just don't know how someone could get families to learn about it.

Source Code

Also, turns out that site has a source repo if one wanted to clone it locally (or contribute): https://github.com/lukesmithxyz/based.cooking

  - https://github.com/LukeSmithxyz/based.cooking

Just recipes, and anyone can contribute their own: https://github.com/LukeSmithxyz/based.cooking

A person by the name of Luke Smith actually started a project with a similar goal of aggregating recipes a while ago: https://github.com/LukeSmithxyz/based.cooking

Here's the current site, albeit it's built in a fairly minimalist fashion: https://based.cooking/

I guess the entire initiative came out of complaining about modern web bloat: https://www.youtube.com/watch?v=cvDyQUpaFf4

Here he talks more about the actual site: https://www.youtube.com/watch?v=ykNEkiYr0QM

Personally, i don't really enjoy his tone or vocabulary choices, but the site works and one has to admire creating lightweight websites, even if they're largely incompatible with the modern trends in content publishing.

Wow this is immediately useful

Already discovered this recipe site: https://based.cooking/

I love how adding recipes is through pull requests: https://github.com/LukeSmithxyz/based.cooking/pulls

Amazing!

I have only one recommendation that might make the search a bit more relevant, e.g when searching for 'linux locking' or 'kernel locking' kind of things.

Try to upsort things that match near the top of the content, like the top of the man page vs middle vs bottom.

One easy way to do it without having to store the positions, is to index the ngrams with max(sqrt,8) of their line number, this will cover first 64 lines, you can also use log() or just decide ad hock, top, middle, bottom of the document, so you can use only 3 values.

e.g. https://www.kernel.org/doc/html/v5.0/kernel-hacking/locking.... would do unreliable_1 guide_1 locking_1 ... then at line 4 kernel_2 locking_2 ... after line 50 ... then_7 ... and after that everything will be _8.

then just make the query "kernel locking" to "dismax(kernel_1 OR kernel_2 OR kernel_3...) AND dismax(locking_1 OR locking_2 ...) with some tiebreaker of 0.1 or so, you can also say "i want to upsort things on the same line, or few lines apart" by modifying the query a bit.

It works really well and costs very little in terms of space, i tried it at https://github.com/jackdoe/zr while searching all of stackoverfow/man pages and etc and was pretty surprised by the result.

This approach is a bit cheaper than storing the positions because positions are (lets say) 4 bytes per term per doc, while this approach has fixed uppre bound cost of 8*4 per document (assuming 4 byte document ids)