coracle/flotilla
1
6
Fork 23
Code Issues 42 Pull Requests 2 Actions Packages Projects 5 Releases Wiki Activity

Social media features #22

New Issue
Open
opened 2026-02-17 18:05:28 +00:00 by hodlbod · 5 comments
hodlbod commented 2026-02-17 18:05:28 +00:00
Owner
Copy Link
Copy Source

Imported from https://github.com/andotherstuff/universes/issues/22 by @staab on 2025-11-14T18:28:20Z

See the coracle mockups for some ideas.

  • Home page feed
    • Conversation digests
    • Kind 1 etc posts from both spaces and outbox of follows
    • Onboarding items
    • Show context - where did this thing come from
    • Reply/reaction/zap indicators
    • Reply trees
    • Ability to publish a kind 1 note (to outbox and spaces)
    • Share to room action
_Imported from https://github.com/andotherstuff/universes/issues/22 by @staab on 2025-11-14T18:28:20Z_ --- See the [coracle mockups](https://www.figma.com/design/OR8KVS7rygIezLNpXgGCDS/coracle.chat?node-id=101-249&t=NNPE0XTtzVq4PagI-1) for some ideas. - [ ] Home page feed - [ ] Conversation digests - [ ] Kind 1 etc posts from both spaces and outbox of follows - [ ] Onboarding items - [ ] Show context - where did this thing come from - [ ] Reply/reaction/zap indicators - [ ] Reply trees - [ ] Ability to publish a kind 1 note (to outbox and spaces) - [ ] Share to room action
hodlbod added this to the Current milestone 2026-02-17 18:05:28 +00:00
hodlbod self-assigned this 2026-02-17 21:26:04 +00:00
hodlbod changed title from Figure out home page to Social media features 2026-02-18 19:02:58 +00:00
hodlbod modified the milestone from Current to Future 2026-02-18 19:06:11 +00:00
hodlbod modified the milestone from Future to Next 2026-03-11 22:59:27 +00:00
hodlbod removed their assignment 2026-03-13 20:49:28 +00:00
hodlbod modified the milestone from Next to Current 2026-03-19 15:46:27 +00:00
hodlbod removed this from the Current milestone 2026-04-02 18:57:16 +00:00
hodlbod added the design label 2026-04-02 19:36:47 +00:00
hodlbod added this to the Current milestone 2026-04-02 19:36:49 +00:00
hodlbod added this to the Microblogging project 2026-04-02 19:38:03 +00:00
Khushvendra commented 2026-04-04 11:48:00 +00:00
Contributor
Copy Link
Copy Source

@hodlbod Could i work on this issue?

@hodlbod Could i work on this issue?
hodlbod commented 2026-04-04 16:12:20 +00:00
Author
Owner
Copy Link
Copy Source

You already have 3 other issues, why don't you see what you can do with those first.

You already have 3 other issues, why don't you see what you can do with those first.
arunimas23 commented 2026-04-10 17:36:32 +00:00
Copy Link
Copy Source

Hi @hodlbod, I wanted to work on this issue. Can you please assign it to me?

Hi @hodlbod, I wanted to work on this issue. Can you please assign it to me?
arunimas23 was assigned by hodlbod 2026-04-10 17:41:50 +00:00
arunimas23 commented 2026-04-12 08:48:13 +00:00
Copy Link
Copy Source

Hi @hodlbod, I'm finalizing my research and moving into wireframes. Before I proceed, I wanted to validate my approach with you.

Based on the research, I'm leaning toward a tabbed feed structure with three sections:

  1. Home: A unified, chronologically sorted feed showing trending content, active spaces (with join CTAs), and active users. Fully interactive from this view.
  2. Spaces: Displays activity from spaces the user has joined, plus discovery of new spaces based on public conversations and activity levels.
  3. Following: Shows kind 1 posts from people the user follows (similar to X.com or Farcaster).

My question: Does this three-tab separation make sense for Flotilla's user base, or would a single unified feed (combining all content types with clear source context labels) be a better starting point?

I've identified the different use cases from the issue description, but I'm not sure whether they're meant to live in one unified feed or be separated into tabs. If you have insights on user behavior patterns or a preferred direction, I'd appreciate the guidance before diving deeper.

Here's my research if you'd like to review: Link to FigJam

Hi @hodlbod, I'm finalizing my research and moving into wireframes. Before I proceed, I wanted to validate my approach with you. Based on the research, I'm leaning toward a tabbed feed structure with three sections: 1. **Home**: A unified, chronologically sorted feed showing trending content, active spaces (with join CTAs), and active users. Fully interactive from this view. 2. **Spaces**: Displays activity from spaces the user has joined, plus discovery of new spaces based on public conversations and activity levels. 3. **Following**: Shows kind 1 posts from people the user follows (similar to X.com or Farcaster). **My question:** Does this three-tab separation make sense for Flotilla's user base, or would a single unified feed (combining all content types with clear source context labels) be a better starting point? I've identified the different use cases from the issue description, but I'm not sure whether they're meant to live in one unified feed or be separated into tabs. If you have insights on user behavior patterns or a preferred direction, I'd appreciate the guidance before diving deeper. Here's my research if you'd like to review: [Link to FigJam](https://www.figma.com/board/SbkRFoNdDBFF3TPB7XeZM4/issue-dissection?node-id=0-1&t=19fKzzGKFpqQHWo4-1)
hodlbod commented 2026-04-13 20:24:52 +00:00
Author
Owner
Copy Link
Copy Source

Part of the idea for this feature comes from various platforms' catch-up features, where the user can make quick work of stuff they missed while away. So while this will be an infinite-scroll format, it should hopefully have a "done" state, when the user has caught up on everything since last visit.

Given that Flotilla is primarily a chat app, I do want space activity to be front-and center, but summaries of trending content, kind 1 activity, and app-related action items I think fit within the "catch up" paradigm. My preference would be to start with a unified feed, with a definition of "done", and a way to weight content so that maintenance tasks don't overwhelm the reasons the user has to engage in the first place. In the future if that problem isn't solvable it might make sense to offload that kind of thing to other tabs.

Part of the idea for this feature comes from various platforms' catch-up features, where the user can make quick work of stuff they missed while away. So while this will be an infinite-scroll format, it should hopefully have a "done" state, when the user has caught up on everything since last visit. Given that Flotilla is primarily a chat app, I do want space activity to be front-and center, but summaries of trending content, kind 1 activity, and app-related action items I think fit within the "catch up" paradigm. My preference would be to start with a unified feed, with a definition of "done", and a way to weight content so that maintenance tasks don't overwhelm the reasons the user has to engage in the first place. In the future if that problem isn't solvable it might make sense to offload that kind of thing to other tabs.
arunimas23 was unassigned by hodlbod 2026-05-06 16:35:33 +00:00
hodlbod modified the milestone from Current to Next 2026-05-06 20:14:11 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
design
For issues related to design work. Development should be done in another issue and refer back to this one.
 dev
Issues related to development work
 easy
Issues that can be executed on by new contributors
 idea
For issues that aren't yet actionable
 priority
For issues related to high priority features and bugs
 usability
Issues that have to be validated with real live human beings.
No Label design
Milestone
No items
No Milestone Next
Projects
Clear projects
No project Microblogging
Assignees
Clear assignees
hodlbod (hodlbod) mplorentz (Matt Lorentz) sakshamjain (Saksham Jain) sondreb triesap userAdityaa (Aditya Chaudhary)
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coracle/flotilla#22
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?