每日 Show HN

Upvote0

2026年5月20日 的 Show HN

23 条
427

I reverse engineered Apple's video wallpapers #

github.com favicongithub.com
106 评论11:54 PM在 HN 查看
Ever since Apple introduced their video wallpapers I wanted to be able to put custom videos there. I decided to reverse engineer and see what I can do.

I built Phosphene to sell it, but the existing competitors were polished enough that the time it would have taken to catch up wasn't going to pay off. So I'm open-sourcing it.

WallpaperExtensionKit.framework is what powers macOS wallpapers. It controls what’s shows in the Settings app. It took a lot of trial and error to replicate the behavior, but the result is that your custom wallpapers appear alongside everything else. I wanted to have an “add” button there too, but I couldn’t find a way to do so, so there’s a companion app that will put your video where it needs to be.

Unlike Apple's Aerials, the video keeps playing on the desktop (not just the lock screen). The renderer drives AVSampleBufferDisplayLayer directly with PTS-offset gapless looping, and pauses or downshifts based on thermal state, battery level, brightness, and window occlusion.

It’s free and works well.

38

Hocuspocus 4 – Yjs collab server #

github.com favicongithub.com
8 评论2:51 PM在 HN 查看
We released Hocuspocus v4 under the MIT license a few weeks ago. It now runs on Bun, Deno and Cloudflare Workers.

For context: Hocuspocus is our open source WebSocket backend for real-time collaboration and is built on Yjs, a CRDT library (props to Kevin Jahns, the Yjs core maintainer). Hocuspocus sits on the server-side and provides real-time sync, presence/awareness, persistence, and Redis-based scaling without writing the merge logic yourself.

At Tiptap, we use it as the collaboration backend for our cloud services, but it works with any Yjs client (Slate, Quill, Monaco, ProseMirror, or your own setup), and Yjs documents aren't limited to text at all. You can sync any structured data through them.

The biggest change in v4 is that it's no longer tied to Node. The previous versions depended on the ws package, which meant you couldn't run Hocuspocus on Bun, Deno, or Cloudflare Workers. We moved to crossws, a universal websocket adapter, so that the same server now runs on Node, Bun, Deno, Cloudflare Workers, and Node with uWebSockets. That also lets you run collab at the edge, if needed.

The other changes are smaller but matter if you're using Hocuspocus in production:

1. Every core class and hook payload takes a generic Context type now, so the auth/session shape you build in onAuthenticate flows through every other hook with full type safety (defaults to any so existing code doesn't break).

2. Document updates are now processed sequentially per connection through an internal queue, which fixes a correctness bug where async hooks could cause CRDT updates to apply out of order under load.

3. Transaction origins are structured objects now with a source field instead of raw values and there's an isTransactionOrigin() helper for narrowing.

4. Hook payloads use web-standard Request and Headers instead of Node's IncomingMessage.

5. The wire protocol is backward compatible in both directions, so you can roll out servers and providers independently.

If you want to test Hocuspocus v4: npm install @hocuspocus/server @hocuspocus/provider

Docs at: https://tiptap.dev/docs/hocuspocus

Source at: https://github.com/ueberdosis/hocuspocus

Because running real-time collaboration on Workers or Durable Objects is new in v4, that's the use case we'd most like to hear your questions and feedback on.

36

I made a tool for learning scales, chords, and how to combine them #

projects.alesh.com faviconprojects.alesh.com
24 评论5:44 PM在 HN 查看
This started out when I vibe-coded a guitar scale fingering generator. It came out pretty good, and I started adding stuff to it: chords, then how chords and scales interact.

Then I added charts for other instruments I mess around with: piano, cello, alto recorder.

There's a complexity toggle to go from basic harmony to extended/experimental stuff.

It's honestly still mostly a toy, but I thought other people might be interested in playing with it. Source is on github, so it's easy enough to run locally and fork.

https://github.com/aleshh/gtr-scales

31

Git-based front-end interface for Hugo #

github.com favicongithub.com
10 评论9:57 PM在 HN 查看
I built simple Git-based CMS for Hugo static site generators. No backend, no database, no configs. Just login with Github, select your repo and start editing. If you use Hugo for blogging, feel free to check it out at https://github.com/arashthr/hugo-flow

> Why did you make it? I wanted to be able to write posts on my phone, and it's not easy to do that with Markdown. Adding images is also always a headache: copy them, minimize and compress them, remember the correct syntax for images, and type the path.

> How did you make it? I used Google Stitch for the design and Antigravity for coding.

> What about alternatives? Check out Front-end interfaces page in Hugo website. None of them is as simple and dumb as I wanted.

> But is it actually working? It's not perfect, but it works well for me. You're welcome to open issues if you find problems.

23

Dari-docs – Optimize your docs using parallel coding agents #

github.com favicongithub.com
7 评论4:53 PM在 HN 查看
It’s well known at this point that documentation needs to be optimized for AI agents - we’re all pointing our Claude Code / Codex / Pi agents at documentation, and expecting the models to figure out how to implement a product.

This, however, changes the entire optimization problem when writing documentation. Good documentation now becomes more objective - you are solving the very concrete problem: can a dumb harness running the dumbest model implement this reliably?

Humans can typically compensate for inconsistent terminology or scattered context across pages, but for agents, this often will waste time (or even just completely confuse the agent).

We’ve been building a small project around this called dari-docs: users can upload their documentation via website or CLI and run agents across different providers to see where they falter. You can upload your documentation, feed a list of tasks, and ask agents with varying intelligence / cost levels to complete those tasks in parallel. When a run is complete, you get back a list feedback markdown files from each agent run and can apply changes based on agent feedback.

Managed service: https://optimize.dari.dev/, repo link: https://github.com/mupt-ai/dari-docs

The agents actually try to use the product end-to-end. They search through the docs, follow instructions, run commands, try examples, and attempt to debug failures. Importantly, this is not a static LLM review of the documentation. The agents are actually attempting the integration.

You can also enable live verification with test credentials so the agents can actually verify workflows against real APIs:

  dari-docs check . --live-verify --secret-env DARI_TEST_API_KEY --task "Create a checkout session"
If you’re building a CLI, API, MCP server, or SDK and actively maintaining docs for humans or agents, we’d love to work with you and test this on real workflows!
9

The AI Quant Desk for Onchain Finance #

grid.raster.finance favicongrid.raster.finance
4 评论8:49 AM在 HN 查看
Most Web3 tools only track basic balances and approximate wallet data.

Raster brings TradFi accounting rigor to DeFi through a unified Truth, Risk, and Decision Intelligence framework.

Our proprietary attribution engine reconstructs a fully auditable state from raw blockchain activity to deliver deterministic PnL (Truth). We calculate deep, real-time portfolio risk signals (Risk) to power our governed AI Decision Intelligence, built specifically for deep analysis and institutional workflows.

8

Remote Job Board #

remotejobs.place faviconremotejobs.place
0 评论11:52 PM在 HN 查看
Built a job board for best remote jobs from top private and public companies. no signup or middleman, apply directly
4

expo-callkit-telecom – easily integrate CallKit/Core-Telecom #

github.com favicongithub.com
0 评论6:53 PM在 HN 查看
I built an expo-module that makes it easy to integrate CallKit/Core-Telecom into a React Native app. I've built a VoIP app before and this was one of the hardest parts. The existing react-native-callkeep is harder to use, isn't easy to set up VoIP notifications with and hasn't been updated in two years. This new module is tested with the latest versions of iOS/Android, Expo and LiveKit. It has a simple and unified API across iOS/Android.
2

Visual studio for cloud #

github.com favicongithub.com
1 评论9:51 PM在 HN 查看
Hi HN, I'm Julia. ICE (beta) is an open-source integrated cloud environment for multi-cloud infrastructure. I also call it Visual IDE but for cloud or Figma for cloud.

Main features: - Multi-cloud project management - Cloud blocks and templates - AI assistant - Cost estimation - GitHub integration

Providers: - Google Cloud — stable(ish) - AWS — in progress - Azure, IBM a others... — planned

Feedback is welcome!

2

Homecrew – Share agent skills across your team and keep them in sync #

crew.logic.inc faviconcrew.logic.inc
0 评论4:28 PM在 HN 查看
Hi HN, we share a ton of agent skills at my startup¹ and keeping them in sync was a pain, especially the full cross-product of every team member and every agent they use.

We built Homecrew to solve it for us and open-sourced it. We use it to share skills, make them accessible to every agents, and keep everything in sync.

It works for managing and finding skills outside of your team as well, but its primary motivation was sharing private internal skills.

It's git-based, so if your team has a git repo of skills, Homecrew should "just work".

Hope you find it helpful. Would love any feedback.

¹ https://logic.inc

2

Formae now supports Kubernetes, Helm, .tfvars and a public plugin hub #

github.com favicongithub.com
0 评论4:25 PM在 HN 查看
Hi HN! I’m Zach, co-founder / CTO of Platform Engineering Labs.

We’re building formae, an open-source IaC system that stays in sync with real infrastructure instead of relying on manually maintained state and drift detection. We’ve just shipped Kubernetes, Helm, and Terraform .tfvars support.

The goal with this release was simple: make it easy to start using formae with infrastructure people already have. formae can now discover existing k8s workloads automatically and the ability to utilize existing Helm charts.

Coming from Terraform / OpenTofu and already have variable definitions everywhere? formae now supports consuming values from existing .tfvars files. You can manage whole k8s clusters - from VMs to workloads - in the same consistent model. Changes made through Terraform, Pulumi, kubectl, or cloud consoles are automatically discovered and synced back into formae.

This release also includes the new public plugin hub, which is now home to our official plugins and, hopefully over time, community-built ones too.

Links:

https://github.com/platform-engineering-labs/formae

https://platform.engineering/

https://blog.platform.engineering/formae-now-comes-with-k8s-...

We’d love feedback from anyone working in platform engineering, DevOps, or SRE.