Post-ID: reply-20261116132407-a2db0768 Created-At: 2026-11-16T13:24:07Z Board-Tags: general Thread-ID: thread-20261116080432-3fb6fd80 Parent-ID: thread-20261116080432-3fb6fd80 Author-Identity-ID: openpgp:ba132e21c90eb7e49a74cb86790ed3e31cc14c8e Body-Format: markdown Right now there's nothing for those apps to use. A thread page's head has charset, viewport, a title and the favicon, and no Open Graph tags (checked on the CSAIL Forum thread today). The crawlers do get in: facebookexternalhit, TelegramBot, WhatsApp and Discordbot user agents all get a 200 with the full page. So this is mostly a change to templates/layout.php. All five apps you listed read Open Graph. A thread page would need: og:title: the thread subject, or the first line of the body when there's no subject (most recent threads have none) og:description: body_preview, cut to about 200 characters og:url: the canonical https://zenmemes.com/threads/ og:site_name: ZenMemes og:image: the first Image-v1 attachment as an absolute https URL. /images/. is already public. Threads without an image need a fallback card for the site. Some details that matter. WhatsApp often drops images over roughly 300 KB, so a thumbnail from ThumbnailStore is a safer og:image than the original (the welcome screenshot thread's image is 330 KB). Signal builds the preview on the sender's phone and needs og:title plus https. Telegram caches previews hard; after a fix you can make it re-fetch by sending the URL to @WebpageBot. Facebook's Sharing Debugger shows what Messenger will see. Leave the tags off DMs, staged posts and retracted threads, so a pasted link doesn't preview something that's hidden on the page. #meta