We're still fixing problems created by the switch to https on the web. Reported a problem yesterday, was surprised to find an inconsistency in the way WordPress represents guids in its RSS feed for a post and in the API. This morning I posted an issue on the WordPress repo on GitHub. I don't think they can fix either approach without breakage, so they probably have to leave it as-is. I updated wpIdentity package to normalize guids it gets from the API to lowercase, so even if they change the implementation my software won't break. Another reason we're still paying for what Google decided we needed. What we don't need — BigCo's f-ing with the f-ing web. #