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

Burn after read feature request (implement MSC1763) #1581

Open
0x00Finch opened this issue Sep 22, 2021 · 3 comments
Open

Burn after read feature request (implement MSC1763) #1581

0x00Finch opened this issue Sep 22, 2021 · 3 comments

Comments

@0x00Finch
Copy link

Your use case

What would you like to do?

I would like to send a message or certain message that will burn after certain time period or after read

Why would you like to do it?

privacy concerns

How would you like to achieve it?

user can either choose the time period they would like the message to stay or they can choose to let the message burn after read

Have you considered any alternatives?

No response

Additional context

No response

@germain-gg
Copy link

This looks like a feature that would benefit from existing in the matrix.org specification rather than being an Element feature

There is a process called MSC to propose changes to the Matrix spec, https:/matrix-org/matrix-doc/blob/main/CONTRIBUTING.rst

@ara4n
Copy link
Member

ara4n commented Sep 27, 2021

This is already proposed (and partially implemented in synapse) via MSC1763 (matrix-org/matrix-spec-proposals#1763)

@germain-gg germain-gg changed the title Burn after read feature request Burn after read feature request (implement MSC1763) Sep 28, 2021
@babolivier
Copy link

babolivier commented Nov 12, 2021

This looks more like MSC2228 (matrix-org/matrix-spec-proposals#2228) to me than MSC1763 fwiw, since it would act at a message level (not at a room one) and also leverage read receipts etc

@t3chguy t3chguy transferred this issue from element-hq/element-web May 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants