Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Mark files that have been deleted on the server. #639

Closed
YamatoRyou opened this issue Sep 15, 2022 · 1 comment
Closed

Mark files that have been deleted on the server. #639

YamatoRyou opened this issue Sep 15, 2022 · 1 comment

Comments

@YamatoRyou
Copy link

Your use case

What would you like to do?

If a file is deleted on the server, but still exists in the room's stream, use a flag to inform the user that the file no longer exists on the server.
When the user tries to download the file, somehow inform the user that the file cannot be downloaded, instead of popping up a select path dialog.
{843A582B-5758-7C8A-2188-7E0C3D8EA33A}

Why would you like to do it?

The current handling of such files is somewhat ugly: even if the file has been deleted by the server, the user can still download the file forcibly, and the file just contains JSON like this:
{"errcode":"M_NOT_FOUND","error":"Not found [b'*******************.com', b'EfbkyHNJEXrwRFAzxHjnbIhJ']"}

{9000A931-BCA6-79B9-7AA6-089E58A96C6F}

How would you like to achieve it?

n/a

Have you considered any alternatives?

Use another external file transfer service, such as Jirafeau or PsiTrasnfer. An external file transfer service can solve the following problems:

  1. Synapse fails to upload large files inexplicably (Weirdly large file upload failed. matrix-org/synapse#12937);
  2. An additional note can be attached to inform the user of the expiration date of the document;
  3. Batch download;
  4. The size of the remaining disk space will affect the download of large files. element-web#22369

Additional context

n/a

@t3chguy
Copy link
Member

t3chguy commented Sep 15, 2022

This would require a HEAD request to each and every bit of media to check if it is still present, which would be a significant privacy leak as then your server would know exactly where your client is scrolling

@t3chguy t3chguy transferred this issue from element-hq/element-web Sep 15, 2022
@element-hq element-hq locked and limited conversation to collaborators Sep 15, 2022
@t3chguy t3chguy converted this issue into discussion #640 Sep 15, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Projects
None yet
Development

No branches or pull requests

2 participants