@SimonWoods Sounds like a bug. Was this served on Micro.blog? We might be missing the right content-type for the response.