For the books I love and want to read over and over, physical. For the books I want to read once and maybe reference from time to time, digital all the way. My e-reader makes digital books a breeze to read, and I'm actually at the point where it's 5GB of storage isn't enough for my library.
mrwiggles
https://bennycheung.github.io/ask-a-book-questions-with-langchain-openai
https://github.com/langchain-ai/langchain
Essentially, you cut the pdf/text file up into chunks, process it to embeddings, then ask the AI questions and it responds with the relevant segments of the book
Hook it up to Langchain with Python and ask a book questions.
As someone in their 30's who didn't take care of my teeth for a while, I'm going to have to second this recommendation. It will save you a lot of grief down the road.
This is the result of the death of isps as net-neutral carriers.
Well that's disturbing.
Except, what it produces is very similar or identical to some copyrighted works, licensed under the LGPL, like in this case. You don't have to copy a whole program to plagiarize someone
I think this largely boils down to the time scales required. A person copying your work has a minimum amount of time it takes them to do that, even when it's just copy and paste. An LLM can copy thousands of different developer's code, for instance, and completely launder the license. That's not ok. Why would we allow machines to commit fraud when we don't allow people to?
💩 -gle making piles people can step in
Well that's terrifying
So, from what I understand, the login cookie is considered "Strictly necessary" as it is involved with the necessary functions of the site. As far as privacy policy and cookie explanations, lemmy has none, and I've been campaigning in Github to get the necessary changes made to make the Lemmy UI compliant, which to my understanding it is not currently. This has nothing to do with cookie banners and everything to do with privacy policy.
And this is why you password protect your ssh keys