[GH-ISSUE #190] Burnt after preview #114

New issue

Open

opened 2026-02-27 10:15:46 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 10:15:46 +03:00

Owner

Originally created by @listiges-kaenguru on GitHub (Dec 7, 2025).
Original GitHub issue: https://github.com/matze/wastebin/issues/190

Hi,

when sending links via Teams, WhatsApp, Signal,... the link is burnt before clicking it. I think it might be because of the loading preview.

Any idea for that?

Originally created by @listiges-kaenguru on GitHub (Dec 7, 2025). Original GitHub issue: https://github.com/matze/wastebin/issues/190 Hi, when sending links via Teams, WhatsApp, Signal,... the link is burnt before clicking it. I think it might be because of the loading preview. Any idea for that?

kerem commented

2026-02-27 10:15:47 +03:00

Author

Owner

@matze commented on GitHub (Dec 7, 2025):

I think it might be because of the loading preview.

Pretty much my suspicion as well. But there is hardly anything I could do. These services might send a query parameter with the request which I could use to prevent deleting the paste but it's a) playing whack-a-mole and b) technically the paste was read.

@matze commented on GitHub (Dec 7, 2025): > I think it might be because of the loading preview. Pretty much my suspicion as well. But there is hardly anything I could do. These services might send a query parameter with the request which I could use to prevent deleting the paste but it's a) playing whack-a-mole and b) technically the paste _was_ read.

kerem commented

2026-02-27 10:15:47 +03:00

Author

Owner

@monstermuffin commented on GitHub (Dec 23, 2025):

This seems to be working as designed and is very common when using burn after reading.

For example, sending someone a password push via teams will invalidate the link once it's crawled for preview.

The usual 'fix' is to wrap the URL with <> so that a preview will not be generated if the platform supports that. You can wrap in backticks otherwise to format as code, alternatively only allowing 2 reads of possible also works.

@monstermuffin commented on GitHub (Dec 23, 2025): This seems to be working as designed and is very common when using burn after reading. For example, sending someone a password push via teams will invalidate the link once it's crawled for preview. The usual 'fix' is to wrap the URL with `<>` so that a preview will not be generated if the platform supports that. You can wrap in backticks otherwise to format as code, alternatively only allowing 2 reads of possible also works.