@MrX

I read and collected Arxiv whitepapers starting after the launch of ChatGPT. I copied and pasted excerpts into Word to track them. Then migrated to Obsidian. That vault of some 1700 papers is now online. I figured it was time to see if others would find the collection useful. My whitepapers were organized into some 90 categories, all of which emerged from paper topics. New categories became necessary with the discussion of new methods, techniques, models etc. If I wanted to write about a topic, I'd upload an md file containing research excerpts on that topic to ChatGPT. This worked to a degree but maxxed out context pretty quickly. And I always had related research in multiple categories, according to how the research was framed. (Personas research in Aligment, Psychology, HCI, etc). So I used a plugin to create topic notes that built in and outbound wikilinks across the papers centered on shared concepts. When I ported this all online I added another layer of synthesis: Inquiring Lines as I call them. These cover cross-cutting, tension-surfacing, synthesizing, and frontier-opening research frames. There's 6,000 of them in my collection. Each is a page to itself that's a useful description of a research line of inquiry. These now also have prompts you can run yourself that will find related (and more recent) research - (I can't adequately maintain each topic with new research). It's all at https://inquiringlines.com/inquiring-lines/ if you want to poke around. As is everything in the age of AI, it's a work in progress. But there's a lot of rich material in there. Have a look. submitted by /u/Barton5877 [link] [Kommentare]

llllllll

Vim Classic 8.3 released [2026-06-02] I'm proud to announce the release of the first version of Vim Classic, Vim Classic 8.3.0, a stable, long-term support fork of the ubiquitous text editor, maintained without the assistance of generative AI tools. For more information about the motivations for this fork, please read this blog post. This release is based on Vim 8.2.0148, with a number of bug fixes and patches conservatively backported from future versions of Vim upstream. We elected to clean up this version of Vim, prepare it for a release, and imagine an alternate history where Vim 8.3 was released without Vim9 script. The result is Vim Classic 8.3. We chose to take this approach in order to reduce the long-term maintenance burden of Vim Classic, acknowledging that our fork lacks the resources and institutional knowledge available to Vim upstream. However, a consequence is that there are some Vim plugins which are not compatible with Vim Classic. We have made a special effort to assess patches from Vim upstream which mitigate some of the many CVEs affecting Vim which were discovered and fixed between versions 8.2 and modern-day Vim, but we can't be sure we've got all of the security patches which are applicable to Vim Classic (and practically exploitable). This version of Vim Classic is therefore recommended for early adopters who are comfortable adopting a security posture which accounts for the fact that we may have overlooked some bugs. We have not evaluated all of the many thousands of patches to land in Vim since version 8.2.0148, so your favorite bug from the last few years might make a reappearance when you install Vim Classic. Your patience and especially your assistance in identifying and backporting the applicable bug fixes for your use-cases is appreciated. Vim Classic is charityware, much like Vim, and we are happy to continue supporting Bram's passion of providing for children in need in Uganda. Switching from Vim to Vim Classic would be an opportune moment for you to make a donation! You can download Vim Classic from SourceHut: .tar.gz vim-classic-v8.3.0.tar.gz .tar.gz.sig vim-classic-v8.3.0.tar.gz.sig This release is signed with my PGP public key. Please subscribe to vim-classic-announce to be notified of important (actionable) news and releases in the future. Last, but not least, let me extend a big "thanks!" to everyone who jumped in to enthusiastically test Vim Classic, provide feedback, and contribute many patches and backports to get this release done. Happy editing! — Drew DeVault

Extension for Visual Studio Code - Browse Hacker News in the sidebar, preview articles, and save stories to Obsidian.

TCPA / Palladium / NGSCB FAQ

Been building Olaf, a companion robot, in the open for a while now and just closed out the phase focused entirely on making him expressive instead of just functional. Sharing the demo + what changed: Voice: swapped Cartesia for Google TTS — noticeably more expressive and natural. Head motion: tuned so movement tracks the words and tone of speech rather than firing randomly. Ears: redesigned the ear movement — surprisingly big impact on how readable his "mood" is. Heart: added a small display on the body that renders a beating heart. Multilingual: he can switch languages mid-conversation (in the demo he answers in Hindi). Still tuning the audio side. That's the expression engine done bar some fine-tuning. Next phase is the body — getting him mobile so he can move around the apartment. Everything's open source if you want to dig in. Would appreciate a star: Hardware: https://github.com/kamalkantsingh10/OLAF Voice agent / pipeline: https://github.com/kamalkantsingh10/olaf_companion Happy to answer anything about the build. Feedback very welcome — especially on the motion-to-speech syncing: right now I'm driving head/ear motion off the LLM output, and I'd love to hear how others have approached tying gesture to prosody. submitted by /u/KamalSingh10 [link] [Kommentare]