Skyhook does not rely on legacy SSL connections to TVDB, so no not related.
The issue is/was TVDB’s API is returning incomplete/invalid data for series.
For example, 30 Rock (TVDB ID 79488) returns this:
<?xml version="1.0" encoding="UTF-8"?>
<Data>
<Series>
<id>0</id>
<Actors></Actors>
<Airs_DayOfWeek></Airs_DayOfWeek>
<Airs_Time></Airs_Time>
<ContentRating></ContentRating>
<FirstAired></FirstAired>
<Genre></Genre>
<IMDB_ID></IMDB_ID>
<Language></Language>
<Network></Network>
<NetworkID></NetworkID>
<Overview></Overview>
<Rating>0</Rating>
<RatingCount>0</RatingCount>
<Runtime></Runtime>
<SeriesID></SeriesID>
<SeriesName></SeriesName>
<Status></Status>
<added></added>
<addedBy></addedBy>
<banner></banner>
<fanart></fanart>
<lastupdated>0</lastupdated>
<poster></poster>
<zap2it_id></zap2it_id>
</Series>
<Actors></Actors>
<Banners></Banners>
</Data>
When we fetch directly from their v1 API. It does that whether we request https://thetvdb.com/api/API_KEY/series/79488/all/en.xml
or https://thetvdb.com/api/API_KEY/series/79488/en.xml
.
It returns the same empty result (instead of an error for some mind boggling reason) when the series is legitimately removed (or the ID never existed). If there was some sort of failure to load instead of returning garbage Skyhook would actually keep on going, though things would be out of date due to updates on the site.
Changes to Skyhook will now wait a week between a deletion and Skyhook returning it’s been deleted, that won’t solve the underlying TVDB issues, but it’ll make it less noisy.