Ask HN: What Are You Working On? (December 2025)
81–90 of 1001 posts
Re: Ask HN: What Are You Working On? (December 2025)
#82Longer term personal aim is a self-hosting platform based on k8s with straight forward bootstrap, similar to Yunohost but k8s based.
Re: Ask HN: What Are You Working On? (December 2025)
#83It can work already as a "Generic" ActivityPub server and it can be made to work with Client-to-Server API, but given that there are not mature clients for that, I am now in the middle of an exercise where I am taking the existing server and implementing Lemmy's and Mastodon's APIs based on top of it. Once I can get any Lemmy and a Mastodon client working, I will then start changing their own SDKs, and then I can replace calls from their application-specific APIs with direct calls to Linked Data server.
[0] https://activitypub.mushroomlabs.comRe: Ask HN: What Are You Working On? (December 2025)
#84Re: Ask HN: What Are You Working On? (December 2025)
#85Re: Ask HN: What Are You Working On? (December 2025)
#86• I open-sourced and released some iOS dev tooling I built for Claude Code that multiplied my personal coding productivity: https://news.ycombinator.com/item?id=46264591 Nobody cares yet, but it makes me feel good to share something cool.
Re: Ask HN: What Are You Working On? (December 2025)
#87Re: Ask HN: What Are You Working On? (December 2025)
#88The project has a CLI interface that is free and open-source, but you have to self-host the gallery. We are also building a SaaS app which is basically a managed version of the open-source tool with a visual builder and we take care of the hosting and CDN.
Re: Ask HN: What Are You Working On? (December 2025)
#89It started out as something marginally more useful than vendoring your dependencies as submodules + baking in the knowledge of how to build a bunch of common projects.
I realized, though, that there was somehow a huge gap in the insane world of C build tools. There's nothing that:
- Lets you pin really precisely and builds everything from source (i.e. no binary repository)
- Does not depend on either a scripting language or a completely insane DSL (Conan uses Python, CMake is an eldritch horror, ditto Make, lots of other tools of course but none of them quite hit the mark)
- Has a good balance of "builds are data" and "builds are code".
Anyway, it's going great. There are, of course, a ton of problems to solve. Chief among them is the obvious caveat that C is not a monoculture like Rust. There will be zero upstream libraries that use this tool natively. But I don't think it matters. I think I can build something which is as much better to the existing tools as, say, UV was to existing Python tools, even with that disadvantage.