tingletech
"""
- The Software shall not be used in any kind of system which includes amongst its functions the ability to purposefully do harm to human beings.
- The Software shall not be used, directly or indirectly, in the creation of an artificial intelligence, machine learning or language model training dataset, including but not limited to any use that contributes to the training or development of such a model or algorithm.
"""
you can use /slots on the llama-server if you want to get more up-to-date details on session token use.
I always run models in their default context, which is 262144 for Qwen3.8 27B. I've run sessions in hax where it hit that cap multiple times and compressed the context down to 15% and continued with no problem.
The blog posts are all attributed to "Lucas Vieira" and the dev group https://faisca.dev that is attributed as the author has 2 other projects. Lucas comes up in LinkedIn and looks like an actual person working in San Francisco.
Re: curl; this seems to work:
cargo install fakecloudSearXNG is more of a metasearch, the dude who wrote it pops in on here and is working on a cool sounding project that is more like a local personal search engine, I forget the name, but I've been meaning to check it out.
There is also Common Crawl.
https://docs.openwebui.com/features/chat-conversations/web-s...
the paper https://arxiv.org/abs/2607.20709
This 2025 discussion links to this too https://news.ycombinator.com/item?id=44117779
pre-read is just looking at how long it is in the headings, and planning out what chapters to focus on if it was a text book. (its sort of iterative, you do a pre-read for the whole book, and then for each section you break it into)
The fast read you try to read only with your eyes, sweeping your eyes across multiple words at the same time, suppressing the urge to say the words to yourself in your head.
iirc the how to read better and faster book even had a cardboard mask you put on the page to practice the sweeping, and some pages that were laid out weird to try to teach you how to do it.
Some ai text just seems really easy to speed read, like if it's tuned for an easy reading level. In PRs some ai seems like it's arguing over weird flex technical details and really starts torturing the language in a way that makes it the opposite of easy to read.
One's hosted on porkbun and one's hosted on namecheap.
Weeding (deselection works) is a fundamental part of collections management. Every trained librarian is going to understand this.
The interlibrary loan system has mechanisms in place to make sure the member libraries keep two copies of each work in each region. Collection managers consult these databases during weeding to make sure they don't deaccession the last copy.
If the monograph was never collected by a library and it gets caught up in a destructive scanning project then I guess it was pretty "rare" in a literal sense. "Rare Book" in library land is sort of a term of art and I'm not sure if the books in these destructive scanning projects meet the criteria.
I find that when I try to speed read modern human writing, there are often errors (like missing or misused words) or awkward expressions that I do have to slow down and think harder a lot to really parse it.
With AI writing, it's sort of self redundant and the information density of each sentence seems to have more even information density. This makes it very easy to do a very high level speed read and get the full gist.
There are also what I'm assuming are bots on hugging face (or maybe non-native english speakers who are using ai for translation) that interact with me where I have no idea what they are saying until I read it very slowly.
https://github.com/brian-learns/llama_cpp/blob/main/update.s...