I’m quite interested in this. Where are you getting metadata and covers from? I found this pretty hard unless you pay for ISBNdb (OpenLibrary has bad covers, and Google Books API doesn’t give you high resolution ones I think).
Ha, openlibrary and google books for now. And yes, the covers are not great. Currently just pleased to get it working, will add better providers later.
Yes, it was polluted with multiple 'Not just [x] but [y]' examples - the most obvious tell of AI-generated text, among other aggravating examples. It was hard to read, but I was interested enough in the subject to slog through it.
"A straightforward, honest, zealous officer doing his duty in the most laborious manner—that’s my style. No Frills. No fancy work. Just honest perspiration. Stolid and a bit stupid—that‘s my ticket."
Yes, LLMs certainly learned these tropes somewhere. I'm just surprised that different models and different pre-processing methods arrived at the same dominant cliches.
I wanted to try NVIDIA’s aistore for our datasets, but I couldn’t figure out how to get a small version up and running so I gave up (a few years ago, today I’d get an LLM to show me how k8s works).
This is great! We need more alternatives to the full calibre stack for working with eBooks. Are you planning to keep it epub focused or would you consider adding support for something like azw3? Also is there a conformance suite for EPUB?
I am happy to extend the functionality, can you maybe create an issue on github.
I am mostly concerned with how big that functionality will end up being, but if its not too much, ill happily add it or at least leave the issue up for someone to pick up.
I think people underestimate how valuable these reports are, so I’m very glad that detailed investigation is done here. Every major grid operator around the world is going to study this and make improvements to make sure this doesn’t happen on their grid.
In a lot of ways it’s like investigations into airplane crashes.
The root cause tree on page 452 gives a good overview of how complex the behavior can be.
The good news is that the grid operators have a good idea of what the problem was/is and it's well understood how to fix it. The downside is that it will require quite a bit of both time and money to reinforce the grid infrastructure.
Spotted the US-american assuming their law system is used world-wide.
If over here a lady buys a hot coffee in a McDrive, drives away, spills the hot coffee on their legs and makes a car accident due to this ... she won't be able to sue the McDrive. There's no fine-print or "Coffee is hot, you dumb person" writing needed anywhere. She could be lucky if she doesn't get fined for endangering others by her stupid actions.
So, if we have a power outage here, the courts don't suddenly get busy. Because there simply no one is suing.
Fun fact: despite this bad power outage, the power grid systems in Europe are still better (even way better) than in the US. There is a comparable statistics measure called "SAIDI" --- system average interuption duration index. And duration wise, per custom and year, the US power grids are worse than over here than in most of West Europe: (US SAIDI 2020: 1.3 hours, German SAIDI 2020: 0.3 hours). That's a factor of more than 4 on the worse-iness of US power grid!
That could be an indicator that suing at the tiniest chance isn't helpful macro-ecnomical. Or that a general suing culture (with legalese trying to protect one from the economic risks) aren't actually helping improving things in the general sense, although they reduce the risk of getting bankrupt. But society-wise, a sue culture is most probably a negative: you spend energy/time/money on things that aren't necessary in saner law systems.
Separate reply for a separate topic: You're repeating the urban-legend version of the McDonalds lawsuit, not the real story, which you can find in numerous places, e.g. https://www.ttla.com/?pg=McDonaldsCoffeeCaseFacts. tl;dr, it was repeated wilful negligence by McDonalds, they'd already injured several hundred other people through it. They knew it was a serious problem but kept doing it anyway.
We had a problem some time ago with a major power outage due to operator negligence. When it came to assigning blame it turned out the corporate structure was such that it was impossible to sue the operator. Since it was in effect publicly-owned, the public would have been suing itself.
I want to like RustFS, but it feels like there's so much marketing attached to the software it turns me off a little. Even a little rocket emoji and benchmark in the Github about page. Sometimes less is more. Look at the ty Github home page - 1 benchmark on the main page, the description is just "An extremely fast Python type checker and language server, written in Rust.".
Haha, +1. I really like RustFS as a product, but the marketing fluff and documentation put me off too. It reads like non-native speakers relying heavily on AI, which explains a lot.
Honestly, they really need to bring in some native English speakers to overhaul the docs. The current vibe just doesn't land well with a US audience.
To be frank this is a service to you. No company you want to work at has a recruiter that doesn't understand the difference (a fully AI recruiter would be better than this experience).
Does anyone use this? I was setting it up a few months ago but it felt very complicated compared to MinIO (or alternatives). Is there a sort of minikube-like tool I could use here?
