Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ability to 'star' messages in order to easily find them again later #319

Open
uhoreg opened this issue Jan 12, 2017 · 18 comments
Open
Labels
A-Room-View O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience T-Enhancement T-Epic Issue is at Epic level X-Needs-Product More input needed from the Product team

Comments

@uhoreg
Copy link
Member

uhoreg commented Jan 12, 2017

No description provided.

@ara4n
Copy link
Member

ara4n commented Feb 19, 2017

I can't believe we don't have a bug already for this. Totally agreed.

@uhoreg
Copy link
Member Author

uhoreg commented Jun 27, 2017

Perhaps include the ability to add different (customizable?) annotations (e.g. star, todo, etc.)

@ara4n
Copy link
Member

ara4n commented Oct 29, 2017

This is very similar to the new idea of pinned messages, except we'd probably just track a list of the starred messages in our room account_data. (We might find ourselves needing a way to paginate the list of starred messages, but we can probably do that in future). The UI for browsing them could be another tab similar to NotifPanel in RightPanel, or possibly a special fake-room or fake-search-results-view which gives an overview of starred messages. (This might need a dedicated server API to work sensibly, but using /context would probably be good enough as a first cut).

@status-open-bounty
Copy link

status-open-bounty commented Dec 12, 2017

Current balance: 0.0 ETH
Tokens: SNT: 8000.00
Contract address: 0x209ac9b3e335783fde1eec51be8d7d20d0fd9b14
QR Code
Network: Mainnet
To claim this bounty sign up at https://openbounty.status.im and make sure to update your Ethereum address in My Payment Details so that the bounty is correctly allocated.
To fund it, send ETH or ERC20/ERC223 tokens to the contract address.

@qnnguyen17
Copy link

qnnguyen17 commented Dec 14, 2017

Hi, if you are open to PRs for this, I would be interested in working on this issue.
If so, I wanted to ask -- would this feature require any changes outside of this repo? From poking around a bit it seems like the answer is no, but I wasn't sure.
Thanks!

Edit: actually -- seems like it would have to be changes in both riot-web and matrix-react-sdk?

@t3chguy
Copy link
Member

t3chguy commented Dec 14, 2017

Most of the changes would likely be in the matrix-react-sdk repo

@r4dh4l
Copy link

r4dh4l commented Dec 21, 2018

Perhaps include the ability to add different (customizable?) annotations (e.g. star, todo, etc.)

To emphasize this: a "convert to todo / tasklist" option would be fantastic for flooded chat rooms at work.

@DJCrashdummy
Copy link

DJCrashdummy commented May 17, 2020

IMHO the essential work is done with the reactions (e.g. i use ⭐, 🔲 and ☑️ to mark them)... now at the search there is "just" a filter for reactions needed (somehow an addition to #908).

@t3chguy
Copy link
Member

t3chguy commented May 17, 2020

What if someone wanted to star something without publicising that fact?

@DJCrashdummy
Copy link

DJCrashdummy commented May 17, 2020

well... in that case it also must be distinguished, if you want to pin a message for all members or just for yourself (if pinning gets implemented at all). 😑

@uhoreg
Copy link
Member Author

uhoreg commented May 18, 2020

Pinning for all users is a separate feature that already exists as a labs feature, but need some work before being released. This feature request is about marking messages for your own use.

@progserega
Copy link

May be also add tab for bookmarked messages as for events now:
1
For example:
2

@t3chguy
Copy link
Member

t3chguy commented Mar 1, 2022

element-hq/element-web#5108 expressed desire in exposing some quick actions on the starred messages, e.g quote & forward.

@t3chguy
Copy link
Member

t3chguy commented Mar 1, 2022

Related to #1762

@mcg-matrix
Copy link

desire in exposing some quick actions on the starred messages, e.g quote & forward.

A comment above mentions "convert to todo / tasklist". Maybe "export" (to a file?) or "copy" (to clipboard?) could be a step in that direction.

If any of that will be possible to be done with "starred" messages, it would be cool if it also could be done with messages with other properties, e.g. carrying some other indicator/annotation (other than a "star"), or having a certain status (e.g. having been marked as unread (#4406), or received certain reactions).

@SimonBrandner SimonBrandner added O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience X-Needs-Product More input needed from the Product team and removed P2 labels Mar 1, 2022
@t3chguy t3chguy transferred this issue from element-hq/element-web May 23, 2022
@hnykda
Copy link

hnykda commented Jul 31, 2022

Hey. Is there any progress on this or anything I could catch up on or help with? This, together with "Mark as unread" and "Remind me", is probably the main blocker for my clients to migrate to matrix :-( .

@aaronraimist
Copy link

@hnykda Element Web has an intern working on implementing it this summer, see element-hq/element-web#22453

@Tanner85
Copy link

Tanner85 commented Sep 7, 2022

Hello to everybody,
I'm also looking for a "put a star on the message" feature and a relative listing function to read messages that I marked as important to me. Is this being developed? I feel it's a very awaited feature.

@kittykat kittykat added T-Epic Issue is at Epic level and removed Meta labels Feb 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Room-View O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience T-Enhancement T-Epic Issue is at Epic level X-Needs-Product More input needed from the Product team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

17 participants