Redirecting to /news/conversation-about-legacy-encode-and-what-comes-next-0