Show HN: Akiradocs – open-source Documentation Framework with AI features https://ift.tt/izZSL4D

Show HN: Akiradocs – open-source Documentation Framework with AI features In the age of information, documentation is your team's strategic asset. AkiraDocs turns that asset into a powerful, intelligent platform that grows with your organization. Transformative Capabilities: Automated content generation Instant multi-language support Data-driven SEO optimization Flexible integration Invest in documentation that delivers real value. https://ift.tt/j1EZwOR December 3, 2024 at 12:18AM

Show HN: Automate your studio – mute a mixer channel to turn your PTZ camera https://ift.tt/SUl2qNo

Show HN: Automate your studio – mute a mixer channel to turn your PTZ camera Seamlessly automate your audio-visual setup! This open-source framework uses the Open Sound Control protocol to integrate audio mixer consoles, OBS, PTZ cameras, and more. Perfect for live production enthusiasts, streamers, and tech tinkerers. I have made it originally to meet our needs, then opensourced it: We needed to move a PTZ cam based on the stage/pulpit mute states on our X32, but it is capable for way more. Let me know what do you guys think! Cheers! https://ift.tt/pWtQT9J December 2, 2024 at 11:42PM

Show HN: Steel.dev – An open-source browser API for AI agents and apps https://ift.tt/eWAzj2G

Show HN: Steel.dev – An open-source browser API for AI agents and apps https://ift.tt/VoZeFRz November 26, 2024 at 07:04PM

Show HN: Bring Pokémon nostalgia to your code editor https://ift.tt/ZRkh3FY

Show HN: Bring Pokémon nostalgia to your code editor I created this VS Code extension to scratch a nostalgic itch of mine and thought I’d share it. vscode-pokemon brings Pokémon into your code editor, adding a touch of joy and nostalgia to your coding experience https://ift.tt/NV4UmAW December 2, 2024 at 02:19AM

Show HN: Markwhen: Markdown for Timelines https://ift.tt/vhk1eb2

Show HN: Markwhen: Markdown for Timelines https://markwhen.com December 1, 2024 at 11:28PM

Show HN: Jinbase – Multi-model transactional embedded database https://ift.tt/OtpdvY4

Show HN: Jinbase – Multi-model transactional embedded database Hi HN ! Alex here. I'm excited to show you Jinbase ( https://ift.tt/2fHa8hr ), my multi-model transactional embedded database. Almost a year ago, I introduced Paradict [1], my take on multi-format streaming serialization. Given its readability, the Paradict text format appears de facto as an interesting data format for config files. But using Paradict to manage config files would end up cluttering its programming interface and making it confusing for users who still have choices of alternative libraries (TOML, INI File, etc.) dedicated to config files. So I used Paradict as a dependency for KvF (Key-value file format) [2], a new project of mine that focuses on config files with sections. With its compact binary format, I thought Paradict would be an efficient dependency for a new project that would rely on I/O functions (such as Open, Read, Write, Seek, Tell and Close) to implement a minimalistic yet reliable persistence solution. But that was before I learned that "files are hard" [3]. SQLite with its transactions, BLOB data type and incremental I/O for BLOBs seemed like the right giant to stand on for my new project. Jinbase started small as a key-value store and ended up as a multi-model embedded database that pushes the boundaries of what we usually do with SQLite. The first transition to the second data model (the depot) happened when I realized that the key-value store was not well suited for cases where a unique identifier is supposed to be automatically generated for each new record, saving the user the burden of providing an identifier that could accidentally be subject to a collision and thus overwrite an existing record. After that, I implemented a search capability that accepts UID ranges for the depot store, timespans (records are automatically timestamped) for both the depot and key-value stores and GLOB patterns and number ranges for string and integer keys in the key-value store. The queue and stack data models emerged as solutions for use cases where records must be consumed in a specific order. A typical record would be retrieved and deleted from the database in a single transaction unit. Since SQLite is used as the storage engine, Jinbase supports the relational model de facto. For convenience, all tables related to Jinbase internals are prefixed with "jinbase_", making Jinbase a useful tool for opening legacy SQLite files to add new data models that will safely coexist with the ad hoc relational model. All four main data models (key-value, depot, queue, stack) support Paradict-compatible data types, such as dictionaries, strings, binary data, integers, datetimes, etc. Under the hood, when the user initiates a write operation, Jinbase serializes (except for binary data), chunks, and stores the data iteratively. A record can be accessed not only in bulk, but also with two levels of partial access granularity: the byte-level and the field-level. While SQLite's incremental I/O for BLOBs is designed to target an individual BLOB column in a row, Jinbase extends this so that for each record, incremental reads cover all chunks as if they were a single unified BLOB. For dictionary records only, Jinbase automatically creates and maintains a lightweight index consisting of pointers to root fields, which then allows extracting from an arbitrary record the contents of a field automatically deserialized before being returned. The most obvious use cases for Jinbase are storing user preferences, persisting session data before exit, order-based processing of data streams, exposing data for other processes, upgrading legacy SQLite files with new data models and bespoke data persistence solutions. Jinbase is written in Python, is available on PyPI and you can play with the examples on the README. Let me know what you think about this project. [1] https://ift.tt/Dq3cfj9 [2] https://ift.tt/gQsoqhS [3] https://ift.tt/xj9f1LV https://ift.tt/2fHa8hr November 30, 2024 at 01:55AM

Show HN: wazero compiler ported to 4 new OSes https://ift.tt/YVm7nzt

Show HN: wazero compiler ported to 4 new OSes Release 1.8.2 of wazero, the zero dependency WebAssembly runtime for Go, brings the amd64 compiler to 4 new OSes: NetBSD, DragonFly BSD, illumos and Solaris. The compiler also supports Linux, FreeBSD, macOS and Windows, on amd64 and arm64. This didn't require any changes to the compiler, just enabling it after setting up tests to validate that it already worked. Now the HN hook: noticeably absent is OpenBSD, which I failed to get working, even after taking W^X into account (we already had that for arm64 on macOS). If you wanna help, please drop us a note! https://ift.tt/Him1WBZ December 1, 2024 at 12:18AM