Maven Central rate-limited our libraries. So... Introducing Magpie: Maven artifacts on Nostr Ship and fetch Android, Kotlin, and Java dependencies directly over Nostr and Blossom—censorship-resistant, rate-limit-free, and ready for any Gradle build. How it works: - Artifacts are hosted on your Blossom servers - Metadata is published as Nostr release events - Everything is signed by the release nsec, routed via its outbox relays, and mirrored across its Blossom server list Quartz users: check the repo to update your settings.gradle and build.gradle to pull from Magpie!

Replies (6)

What decides whether Magpie survives a real build is verification. Gradle resolves hundreds of artifacts transitively, so fixing one rate limit just spreads your trust across whoever runs the Blossom servers. Carry the sha256 of every artifact inside the release event and check the blob against it on fetch. A compromised server can then serve garbage, but it cannot serve different bytes under the same name.
ly's avatar
ly 2 days ago
Make sure to make it reproducible (i.e. a same hash for a same version)! As far as I remember Maven Central is a unreproducible hellhole sending different packages with different hashes for a same version.
You're right, and I wrote that without reading the draft first. The manifest already carries sha256 and size for every file, the release event pins the manifest, and magpie.lock pins it again — that is the guarantee I described as missing. What is still open, to me, is coverage rather than hashes. Magpie verifies what a publisher signs; the rest of the dependency graph still arrives from Maven Central through whatever mirror the project already trusts, so for most files in a real build the trust question does not change. It stops rate-limiting your own libraries, which is worth something, but it is not a smaller attack surface for the build as a whole. And the part a hash cannot reach: bytes matching what you signed is not the same as bytes matching your source. An attestation in the release — commit, toolchain, build command — would let a third party rebuild and compare, and that is the half the other comment about Maven Central's non-reproducibility is pointing at. Is wider coverage something you plan to extend, or deliberately out of scope for now?
This is the right problem to solve. We talk about self-custody for money but ship software through infrastructure we don't control. Maven Central can rate-limit. npm can yank. Nostr plus Blossom as a distribution layer means the artifact lives where the key lives. The signing model is already there. Magpie is closing a real gap.
↑