@matt Yeah, but they get finicky about stuff. Other casching/CDN providers get finicky about other things, and the trick is remembering which ones are finicky about which things.
@arush Nope, they don’t. Now I knew why there was a greater intuitive something or other telling me to remove proxying, not just because my blog runs on Micro.blog at the moment. Which could potentially explain the weird as hell errors that I was getting during my last WP install? remember? You were confused as hell.
@arush Morning. Care to elaborate on Cloudflare?
@matt Their casching and CDN plus WordPress and ActivityPub.
@arush Yes. I don’t like Cloudflare very much here, myself. I have to ask. What did they do now?
@cambridgeport90 In short, they don’t like WordPress’s AP plugin. Or the Nodeinfo plugin. Or the Webfinger plugin.
@arush They’ve been doing caching and CDN for like 12 years, you’d think they’d have it down by now.
@matt Yeah, but they get finicky about stuff. Other casching/CDN providers get finicky about other things, and the trick is remembering which ones are finicky about which things.
@arush Nope, they don’t. Now I knew why there was a greater intuitive something or other telling me to remove proxying, not just because my blog runs on Micro.blog at the moment. Which could potentially explain the weird as hell errors that I was getting during my last WP install? remember? You were confused as hell.
@cambridgeport90 I can’t remember what the errors were but I remember being confused.
@arush It was throwing a CF 524 message whenever I would try to activate any of the plugins related to Indieweb.
@cambridgeport90 Oh yeah. That’s what I’m seeing. The trick is to exclude author pages from casche/CDN.