Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Feed Topic Summary (AI-powered, like X)

Open
  • Is something wrong?
#2 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
dart, flutter
Domain
ai, mobile

Research direction

Start by reading docs/graphrag.md and tracing how NoteModel.tTags, eTagRefs, and rootEventId are used to fetch and expand notes. Then investigate the Flutter feed/thread views and the on-device Shiv/Gemma integration mentioned in the issue. Done means eligible feeds and threads show a collapsible, streaming summary with regeneration, without a cloud API call.

Written by the indexing model from the issue text.

Description

enhancement

Summary
When multiple notes share the same topic tag (tTag) or are in the same reply thread, show a 2–3 line AI-generated summary at the top of the topic feed or thread view. Powered entirely on-device by Shiv (Gemma via flutter_gemma) — no cloud API call.

Flow

  1. User opens a topic feed (e.g. #bitcoin) or a long reply thread
  2. App fetches top N notes from Isar filtered by tTag or rootEventId
  3. Notes are BFS-expanded via eTagRefs (GraphRAG — see docs/graphrag.md)
  4. Subgraph is verbalized into a prompt and sent to Gemma
  5. Summary streams token-by-token at the top of the feed/thread

User experience

  • Collapsed by default — tap to expand
  • Regenerate button to re-summarize with latest notes
  • Only appears when there are 5+ notes on the same topic

Data layer impact
None. NoteModel.tTags and NoteModel.eTagRefs are already in place for graph traversal.

When to build
Shiv AI phase (last major feature).

Dominant language
Dart
Stars
2
Forks
2
Avg merge
1d 35m
Merged PRs (30d)
36

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from basictech01/uniun

All issues in basictech01/uniun

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.