All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Discord Privacy Bug: How OpenGraph Image Proxy Reveals Message Read Information

By

pauxel

1mo ago· 6 min readenInsight

Summary

The article reveals a privacy bug in Discord's platform where read receipts can be inferred despite Discord's deliberate design choice to not include them. The bug occurs in Discord's OpenGraph image proxy system - when a user views a message containing a link, Discord fetches the OG image through its proxy server, and this proxy request reveals not only when the message was viewed, but also how frequently and for how long. This creates a privacy vulnerability that contradicts Discord's stated privacy principles of not tracking message reads.

Key quotes

· 4 pulled
Discord deliberately does not have read receipts. It's one of the platform's unwritten privacy promises.
When you paste a URL into a message, the backend fetches the page, parses the OpenGraph meta tags, and shows a preview embed with whatever og:image the page declared.
The image itself never loads from the original server in a user's client. Discord proxies it through images-ext-1.di
A bug in the OG image proxy reveals not only when a message was viewed, but also how often and for how long.
Snippet from the RSS feed
Discord does not have read receipts by design. However, a bug in the OG image proxy reveals not only when a message was viewed, but also how often and for how long.

You might also wanna read