Context Navigation

Changes between Version 1 and Version 2 of Ticket #61941, comment 49

v1	v2
1	1	We invested several cycles ensuring as we spun up new back end infrastructure. This was to keep our existing Screencast functioning on a newer tech stack. A great amount of attention went towards keeping original content working. We didn't want to spin up a subdomain but determined that was the only way to tackle a graceful transition. As such we custom built a proxy that will translate original screencast.com links to app.screencast.com targets.
2	2
3		We have several customers complaining that we "broke" functionality in WordPress. However, every other application(or web service) that unfurls or embeds content is still functioning. The content has not changed, just merely the DNS resolution for the content is pointing at a subdomain of the original domain. Not supporting this new subdomain of the original service is taking away actively used embeds from existing customer implimentations.
	3	We have several customers complaining that we "broke" functionality in WordPress. However, every other application(or web service) that unfurls or embeds content is still functioning. The content has not changed, just merely the DNS resolution for the content is pointing at a subdomain of the original domain. Not supporting this new subdomain of the original service is taking away actively used embeds from existing customer implementations.