Wanted to share something with this community and see if it’s useful to anyone. Inkwell (inkwell.social) is an open source, multi-tenant social journaling platform built on ActivityPub. The goal is to fill the long-form writing gap in the fediverse in a way that’s accessible to non-technical users, not just developers who can spin up their own instance of WriteFreely or Ghost.
What it does: users sign up, write journal entries or articles, and those posts federate as Article objects per FEP-b2b8 with preview Notes so they render cleanly in Mastodon and other microblogging clients. You get a title, excerpt, and link rather than a decontextualized URL. Follows, boosts, and likes all work bidirectionally with Mastodon.
It’s ad-free, algorithm-free, and the code is open source on GitHub (github.com/stantondev/inkwell). The hosted instance is at inkwell.social if you want to try it, or you can self-host your own.
Some things that might interest this community: ActivityPub federation with HTTP signature verification, Stamps (emotional reactions) instead of generic likes, a tipping system called Postage for supporting writers, newsletter delivery, custom profile themes, and data import from other platforms. Currently working on improving comment edit propagation and post scope handling for better fediverse compatibility based on community feedback.
Would love to hear thoughts, especially from anyone who’s been looking for a long-form option in the fediverse or anyone interested in running their own instance. What’s working, what’s missing, what would make this more useful to the ecosystem?
#fediverse #activitypub #longform #writing #opensource
Edit: Adding this after looking into the spec more closely. Inkwell publishes Article objects following the draft FEP-b2b8 guidance. I was wrong about the Mastodon behavior in my original wording above. Inkwell includes a preview fallback, but Mastodon does not currently appear to render that preview behavior as envisioned by the draft. That is my mistake.
Well, the good news is that you don’t have to face it all alone.
The AP developer community is here and happy to explain the difference between the theory (the spec, the protocol, the FEPs), and the reality (for most FEPs implementation is limited in scope).
b2b8, for example, was championed by @evan, and I pushed for broader support alongside Ghost, WordPress, and WriteFreely. It is largely well supported except for the preview piece, which only BridgyFed supports.
Claude will tell you lots of right things, and I’m sure it’ll confidently tell you some wrong things too. If you ever need to double check something, ask on the fediverse subreddits or @technical-discussion — you should be able to reach it from your Piefed account.
@julian It’s been a great multi-implementer effort, both from the long-form text producers and the microblogging services.
@inkwell@piefed.social one warning about doing ActivityPub development with LLMs: codeberg.org blocks a lot of LLMs for training and for RAG/MCP. Since FEPs are hosted there, I’ve found that searching for information on FEPs will result in incorrect information.
Thanks again Evan! I think that is where my bad information came from and good to note. I’ve been lucky and really appreciate the support. If there is anything I can do to improve on my side, I’m all ears!
Thanks again, Julian! I will absolutely follow the suggestion on asking for advice. I’ve received great feedback when posting about the app and will hopefully go about it better moving forward. xD