Recall Network: Share, Follow, Discover
P
Paul Richards
Turn the content you create in Recall into a knowledge-sharing network
We've seen an increase in the use of shared cards, and saw this as a great opportunity to make it easier for the great content being created in Recall to find its way to others who'd benefit from it.
Right now, a shared card only reaches the people you send the link to. But a lot of what our users are building, summaries of dense papers, curated reading lists, notes from talks, recipe collections, is genuinely useful to more than one person. This is a way to let that content be found, followed, and learned from.
Think of it as the lightweight, Recall-native version of something like Medium: a place to share what you're already learning, without the effort of writing long-form or the friction of sign-ups for readers.
The idea:
When you create content in Recall, you can choose to share it publicly. That gives you a public Recall profile with a short bio and a list of all the cards and collections you've made public. You can curate collections of your best cards on a topic, "Best resources on agentic AI", "My favourite recipes", "Top programming tutorials", and share them as a playlist of summaries.
Your shared content becomes discoverable, so anyone interested in the topic can find it, not just people you send a link to. Others can like, comment, and save your content into their own Recall. They can follow you, so they're notified when you publish something new.
Key components
- Public profile page where others can see all your shared content
- Likes, comments, and follows
- Content discoverable publicly
- View and save counts on your shared content
- Notifications for followers when new content is published
Curious to know what the community thinks and to get your feedback below.
Log In
c
connie
just wow... I am starting a small community group texting service, it is a one shot thing with no archive, either you get the message or it's gone. In a way that is good, there is no build up of old stuff.. texting is now or never kind of thing. What perks me is that... maybe it would be a good idea to be able to capture the group texts so that members can refer back to messaging, example Farmer Joe has beets for sale...on May 29 but in my system.. to avoid congestion and over communication... members are allowed to text their "message" only once a week. Not 100 x a day. So me the farm market buyer might find it useful to retrieve John's text and connect with him for current availability of beets despite the one shot weekly message.
My messaging service key point, all members will be local verified, be it drivers license or utility bill. It will be totally local. All members of the group messaging then will be assured of all the other identities. No spoofing, ghosting, faking.
But it would be crazy awesome if I could build an archive so people could access a history of the text messages.
That also works well for me, if there are issues, I can back track and see what was texted but hopefully I will not have to do much forensics, as this will be an honour system and each member is validated. No bots.
Conrad Hild
cheers
M
Michael Leone
This is a really fascinating idea. Building a community around this is next level for a product like this!
s
schroell
I really like the direction of this proposal, especially the idea of turning Recall into more of a lightweight, native knowledge‑sharing layer with public profiles and collections.
For context, I don’t actually use Recall as my first brain. My primary “thinking environment” lives elsewhere, and I use Recall more as a structured knowledge store and as a place to land and organize complex web content. So I’m not the core target user for whom all content is authored and refined directly inside Recall.
That said, your idea starts to get very interesting for my workflow once three pieces come together:
* The public profile / public collections layer you described
* A way for external users to comment and interact with that content
* A clean way to write into Recall from the outside, ideally via MCP or a similar API surface
In that setup, Recall becomes a kind of retrival of curraded information platform with publishing backend abilities for curated insights coming out of my first‑brain system, rather than the place where I do the primary thinking. I could have agentic workflows in my main environment that assemble and refine client‑ or topic‑specific dossiers based on fetched content from Recall and then push those into Recall back as public or semi‑public collections.
On top of your public profile feature, that would let me expose curated knowledge hubs for my clients: themed collections for specific industries, technologies, or projects that live at a nice, human‑friendly URL, with commenting and interaction built in. Today I approximate some of this with things like LinkedIn posts, but I don’t have the same structured knowledge graph or the same ability to automate the publishing pipeline.
The real power for me would be in closing the loop: comments, reactions, and engagement signals on those Recall collections could flow back via MCP into my own systems. That would let me feed client feedback and interest levels into my internal decision matrices and prioritization logic, and then automatically adapt what content I create or deepen next.
So even though I’m not your archetypal “Recall as first brain” user, this feature plus a write‑path into Recall would unlock a set of use cases that go beyond the ones you outlined: client‑facing knowledge hubs, interactive advisory spaces, and fully automated learning loops between my internal first‑brain environment and Recall as a public knowledge frontend.
P
Paul Conway
A very good idea that can help to build a group of followers on a subject. It could also work in education for study groups to information for collective submission, or revision for exams.
R
Ricardo Youle
I like this line of thought :) Will the card's chat history also become available when sharing publicly?
r
rafael.jose.kraisch
I thought it was great. As a science communicator, I can use Recall to share notes about articles and posts.