GranaryConvert Nostr Content into Feed Formats

What Is Granary and How Does Conversion Work?

Every social network stores posts in its own structure. A post has an author, a timestamp, text, attachments and sometimes references to a parent post or a reaction. A converter reads the source record, pulls out those pieces, and writes them into the structure a target format expects.

In practice, this means a Nostr event can become an Atom entry, an RSS item or an ActivityStreams object. Each target has its own rules for dates, identifiers and media, so good converters handle edge cases such as missing fields rather than failing. Granary's job is this translation step, and it leaves publishing and hosting to you.

The result is only as good as the source data. Fields that exist in one network but have no counterpart in another may be dropped or simplified. Testing a few representative posts before you convert a full archive is a sensible habit.

Who Is Granary For?

Granary fits people who already work with code or publishing workflows. A common case is a blogger who wants Nostr posts to appear on a personal site as a feed. Another is an IndieWeb enthusiast who wants microformats2 markup for posts that originate on Nostr.

Developers building bridges between networks are the second main audience. Someone maintaining a service that mirrors content between the fediverse, Bluesky and Nostr can use a single library instead of writing three converters. Researchers comparing decentralized protocols can also use it to examine how the same post looks in different schemas.

It is less suited to readers who want an everyday app. Without a graphical interface, you will work with commands, code or the web demo. That trade-off is intentional for a library, and it is worth understanding before you invest time in a project.

Why Convert Nostr Posts into Feed Formats?

Nostr is built around relays and signed events, which is powerful but not what most readers expect. Feed formats such as RSS and Atom are familiar to anyone who has subscribed to a blog. Publishing Nostr content in those formats lets people follow it with tools they already use.

Interoperability is the other reason. Fediverse servers speak ActivityPub, while Bluesky uses the AT Protocol. A conversion layer lets the same material travel between these worlds without requiring every reader to adopt a new protocol. This is one of the core ideas of decentralized social software: the content should not be trapped in a single app.

There are trade-offs. A converted post may lose details that only exist on the original network, such as certain interaction types. Reviewing the output before you publish it at scale helps you catch these gaps early.

Developer Notes on Recent Changes

Recent releases include several changes that matter if you already use the library in a project:

• Set createdat to the current time when converting. Some relays require it, so the input object's published value is no longer used for this purpose.
• Always include the alt element in imeta tags for images and videos, even when it is blank. NIP-92 requires at least one field besides url.
• The create method now signs activities before sending them to relays. You must set the privkey member attribute.
• A new raise keyword argument raises ValueError when a required object, such as the target of a like or repost, cannot be fetched via ATProto.
• For fediverse actors with the unlisted audience, add misskey requireSigninToViewContents, which mirrors Bluesky's no-unauthenticated label.

Test these changes in a staging environment before updating production code.

Supported coins

The project documentation names Dash and Nostr as the coins and networks it relates to. Granary is built around content conversion rather than wallets or transactions, so its connection to the crypto space runs through decentralized networks like Nostr. Treat these references as context rather than a list of supported assets.