nextcloud / nextcloud/talk-android

Separate message history and activity log

Open
#857 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature: chat 🗨️
Dominant language
Kotlin
Stars
739
Forks
321
Avg merge
14h 59m
Merged PRs (30d)
151

Description

Meta data in chat history is important. No doubt. But I find myself getting distracted quite a lot by chat activity entries. They take up a lot of space and therefore a lot of my attention (see https://raw.githubusercontent.com/nextcloud/talk-android/master/fastlane/metadata/android/en-US/phoneScreenshots/receive_gifs.jpg). If I try to call someone quite often without success, my history will be spammed by those activity logs. And even still normal usage results in many entries (started, entered, left, duration).

What if we separate the chat messages from the activity log? I know that other messenger like Signal or WhatsApp do as well show these activities, but even there I think they distract me from the message chat.

The idea is a bit the same as phone and sms. I have my phone history and aside the sms messages. The activity log could be gathered in the context menu on right top corner. Then no matter how "active" I am in chat, my message flow is not flooded by meta data.

Contributor guide

Open the contributing guide

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.

Research direction

The issue does not name any files, tests, or entry points. Start by locating the Android chat-history UI and how activity entries are rendered, then trace the existing context-menu navigation. Done means message history no longer includes activity entries and those entries remain accessible separately.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.