3 ms·
>During that period, it was accessed 43 times by 32 unique IP addresses I find this an implausibly low number. It was all over Bluesky, X etc., not to mention
by M2Ys4U 10mo ago
>During that period, it was accessed 43 times by 32 unique IP addresses
I find this an implausibly low number. It was all over Bluesky, X etc., not to mention journo Signal and WhatsApp groups.
- jamesbelchamber 10mo agoPossibly copies of the document rather than the original URL?
- logicchains 10mo agoMaybe it was cached somewhere and most people were hitting the cache?
- m4tthumphrey 10mo agoEither that number was wrong like you say OR (and I am unfamiliar with Bluesky) the URL is loaded via Bluesky's browser (like X) and therefore Bluesky's own server IP was used (instead of the user's). Edit: Or (and more likely) cached/copies of the original.
- reddalo 10mo agoI feel like those 32 unique IP addresses may very well be Cloudflare or CloudFront ones.
- ZoneZealot 10mo agoI agree, and I also am familiar with how WP Engine's 'GES' (global edge security) works. obr.uk points to two IP addresses held in the name of WP Engine, but they're actually BYOIP with Cloudflare. Cloudflare act as a caching layer, DDOS mitigation and WAF. Note that GES works a bit different to traditional Cloudflare implementations, HTML requests are basically passed through to the WP Engine NGINX reverse proxy server that's in front of the WordPress site (as opposed to being heavily cached with Cloudflare). Static assets, like a PDF - would indeed be cached with GES.