It seems like all RSS feed validators are, well, seriously broken when it comes to talking to modern TLS, like feeds hosted via @CloudFlare.
-
-
Replying to @sindarina
Not
@CloudFlare's fault, of course. Even@Flipboard's implementation is broken, you'd think they would be a bit more current, but nooooo.1 reply 0 retweets 0 likes -
Replying to @sindarina
Of course we've poked
@Flipboard about updating it's UA string several times now, and it probably still isn't done
1 reply 0 retweets 0 likes -
Replying to @sindarina
@sindarina@Flipboard most likely cause if it happens with TLS only is a lack of client support for SNI - assuming it's a Free plan1 reply 0 retweets 1 like -
Replying to @Cloudflare
@sindarina@Flipboard 2/2: Write to us with some more detail however if you want some more guidance1 reply 0 retweets 0 likes -
Replying to @Cloudflare
@CloudFlare Aye, free plan, some kind of SSL error. Totally blaming@Flipboard for not keeping their client current. Thanks!1 reply 0 retweets 0 likes -
Replying to @sindarina
@CloudFlare If there's anything that points towards you I will of course open a ticket
1 reply 0 retweets 0 likes
@sindarina No problem. Pro plan does not require SNI, but moving forward more and more services will support it in any case.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.