Post by @mboelen
So what would happen if I share a #BSD related post on here? Testing if it pull in the meta-data, especially since I blocked all agents that do not support content encoding (read: compression).
https://bsd-audit.com/self-hosting/running-your-own-mailserver/
@mboelen
Look at that, #littlefedi does that correctly and announces itself also clearly. 👍
2026-08-10T13:04:01+00:00 200 XYZ "GET /self-hosting/running-your-own-mailserver/ HTTP/1.1" 35603 "-" "littleFedi/26.08.09 (link preview)" TLSv1.3/TLS_AES_128_GCM_SHA256 0.000 .
2026-08-10T13:04:01+00:00 200 XYZ "GET /opengraph/background_hu_e4b2de6594c40996.png HTTP/2.0" 78766 "-" "littleFedi/26.08.09 (media proxy)" TLSv1.3/TLS_AES_128_GCM_SHA256 0.001 .
It looks like littleFedi is supporting gzip, but not Brotli yet (gzip=35603 bytes, brotli=24350 bytes). Both Brotli and Go developed by Google, I will list this on the "nice to have" in my feedback to @stefano 😄
Nice example of the opposite: Pleroma does not support compression at all (so it would like the version with 132715 bytes, uncompressed). So that software simply wastes a lot of bandwidth, especially if you consider how much links are shared. So yes, I block those requests and return a 406
2026-08-10T13:04:08+00:00 406 1.2.3.4 "HEAD /self-hosting/running-your-own-mailserver/ HTTP/1.1" 0 "-" "Pleroma 2.10.2; https://xyz <xyz@xyz>; Bot" TLSv1.3/TLS_AES_256_GCM_SHA384 0.000 .
