Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • Whisperfish - Signal on Sailfish OS Whisperfish - Signal on Sailfish OS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 234
    • Issues 234
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • WhisperfishWhisperfish
  • Whisperfish - Signal on Sailfish OSWhisperfish - Signal on Sailfish OS
  • Merge requests
  • !53

Draft: Display session and message identifiers

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Markus Törnqvist requested to merge display-session-message-ids into master Nov 21, 2020
  • Overview 1
  • Commits 2
  • Pipelines 3
  • Changes 13

This is basically nerdy debug info, but as I mentioned on IRC, it could also be useful as an interim #99 .

My thinking is that we could decode and store reactions in a format maybe like @ MSGID REACTION which would be human readable as a reaction when you see the MSGIDs referred to, and machine-readable when the database is aware of reactions and a data migration can be made.

This also allows us to postpone (likely to be very annoying) QML work into the future.


A wishlist item would be log-parsing to retroactively store these reactions into the database already now. It seems the log contains almost everything, although the target message id seems to be needed to looked up by timestamp.

Edited Dec 21, 2020 by Ruben De Smet
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: display-session-message-ids