This repository publishes a feature matrix showing protocol capabilities supported by Nostr clients.
Open source
24 alternativesehagaki
vsblossy
ehagaki vs blossy
How do ehagaki and blossy compare? Here are the facts side by side: pricing, platforms, open-source status and what each one is for.
| Directory detail | ehagaki | blossy |
|---|---|---|
| What it is | ehagaki provides a post-only Nostr client that compresses media on the device before upload. | Blossy supports building customized Blossom servers through a framework written for the media protocol. |
| Website | ||
| Type | Open-source project | Open-source project |
| Topic | ||
| Pricing | Not confirmed | Not confirmed |
| Platforms | Not recorded | Not recorded |
| Open source | Yes | Yes |
| Language | English | English |
| Alternatives |
Other options to consider
Sites similar to both ehagaki and blossy.
BlazeJump provides core protocol interactions through a minimal Nostr client written in C#.
Open source
24 alternatives
This comparison list tracks which Nostr clients support different protocol features and NIPs.
Open source
24 alternatives
Blossom specifies HTTP endpoints for storing blobs on media servers using Nostr public and private keys for identity.
Open source
24 alternatives
bloom combines a self-hosted media server with a Nostr relay for decentralized media sharing.
Open source
24 alternatives
cfrelay runs a Nostr relay on Cloudflare Workers and supports the basic NIP-01 protocol.
Open source
24 alternatives