1,656 karma · joined June 18, 2010
Edit: unless you're Swiss, your opinion is irrelevant. Swiss voters have a right to decide how they want to live. They're not beholden to EU laws; they can make their own sovereign decisions, and everyone must respect that.
Furthermore, it didn't feel LLM-generated to me. Quirky, yes; nothing wrong with that.
There are many similar models from other companies; however, while Bluetooth is advertised as its primary connection, this one also has a USB port, which works with Linux!
Bluetooth also works, but it was too unreliable for me. I ended up using Claude to write a small CLI tool which prints via raw USB: rock solid and simple.
That said, I also support Anna's Archive. We need access to books.
So this offers an alternative, legitimate, route to exactly the website content you're suspicious of.
Because there's a danger now that any writing (human or otherwise) can be labeled LLM-produced. So we need accurate heuristics, or none at all.
A patent document can be represented in a graph. That opens it up to various transformations, refactoring, and validation – all mathematically rigorous! This is far more reliable than asking an LLM to check a document.
Using git enables not only regular diffs, but also structural diffs, which compare legal elements rather than just lines.
The LSP (yes, that too!) makes drafting much easier, with autocomplete and validation as I type.
I plan to open-source the DSL, and the tool that processes its files and outputs jurisdiction-aware, nicely formatted documents...
A few months ago, for the first time in my life, I had to write a patent document. It was very complicated – too complicated. Noting the structure, I searched for tools, but found only LLMs. So I wrote my own tool.
The amusing thing is, LLMs prefer the DSL-structured document!
Patent texts read as prose, but are actually precisely structured legal documents. The latest developments in this domain involve LLMs to create and modify patent documents, but even though the legal profession seems to have fallen all in on it, it's essentially rather fragile and error-prone.
I've gone the deterministic direction, which has opened up some very cool, previously unexplored, possibilities!
Also, Moho offers far more comprehensive (and comprehensible!) lip-sync: https://lostmarble.com/papagayo/
I get that you're using AI to boost capability with less effort, but at the moment, I think the more specialized tools are still a better avenue for this.
Lastly, I followed the link to Jellypod (https://www.jellypod.com/). It's pretty good, but falls into a vocal "uncanny valley". Even a human reading from a script wouldn't sound that perfect; the enunciations immediately come across as artificial.
Now, if this was an extension to Synfig (also open source!), it would be a much more interesting venture...
However, since the Zip disks were formatted with an Amiga file system – I used PFS3 (https://en.wikipedia.org/wiki/Professional_File_System) – they couldn't be used with a PC.
I'm curious whether the data is still readable, after 30 years...
That said, it's not too late... I still have my Amiga system in storage, and a VHS recorder.
There was this, from the same era: https://en.wikipedia.org/wiki/ArVid
And I have this for my Amiga, also same era: http://www.hugolyppens.com/VBS.html
This is a famous "killer" feature from WordPerfect: the ability to view and edit the low-level formatting for a document. It's invaluable for fixing weird bugs.
However, it works only because WP uses the "text-stream" paradigm, where a document comprises a linear stream of text with formatting codes (Bold, Font, Hard Return, etc.) embedded directly at the point at which they're applied.
In contrast, Word uses the "nested containers" model (characters inside words, words inside paragraphs, paragraphs inside sections, etc.), where this feature can't be replicated.
I didn't look closely at your code, but just thought to mention this feature.
UA 571-C remote gun sentry
Obviously developed in Ukraine ;-)
The formatting had to be manipulable in code; the first two options were unsuitable for my use case. That left OOXML and ODF.
Both docx and odt are zip files, with XML content. Any guess which one turned out to be the better choice? I was left wondering why docx even exists in the first place.
Anyone using OOXML can rightly be regarded as stupid. There are far superior formats, and we should insist on their usage.
However, I'd never use it. Reason: having everything dynamically created JIT means there's a trade-off somewhere else; in this case, it's energy consumption. I'd rather "cache" applications (ie. have them as installable software, which has been built just once) than endlessly recreate software from scratch each time, with all the energy usage that entails.
The computer doesn't "enjoy" books – it assimilates them as data. That data isn't stored verbatim; it's used to train a system. In return, ChatGPT is made freely available, and millions of people benefit from it.
What is morally wrong about this?
(But whether any EU member is capable of rising to this (very shallow) challenge... well, I'm justifiably cynical.)
And, to my eyes, it simply looks better.
"Most ARM single board computers depend on proprietary binary blobs to boot or ship with outdated vendor kernels that are never upstreamed and quickly abandoned. Libre Computer takes a different approach: we fund and contribute to the mainline Linux kernel and U-Boot directly, ensuring our platforms run on upstream open-source software with minimal proprietary firmware."