<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 16, 2014 at 12:06 PM, Paul Harrison <span dir="ltr"><<a href="mailto:mythtv@sky.com" target="_blank">mythtv@sky.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 16/10/14 17:35, Joseph Fry wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
<br>
<br>
On Thu, Oct 16, 2014 at 12:18 PM, Jon Heizer <<a href="mailto:jheizer@gmail.com" target="_blank">jheizer@gmail.com</a> <mailto:<a href="mailto:jheizer@gmail.com" target="_blank">jheizer@gmail.com</a>>> wrote:<br>
<br>
<br>
<br>
On Thu, Oct 16, 2014 at 11:06 AM, jedi <<a href="mailto:jedi@mishnet.org" target="_blank">jedi@mishnet.org</a><br></span><div><div class="h5">
<mailto:<a href="mailto:jedi@mishnet.org" target="_blank">jedi@mishnet.org</a>>> wrote:<br>
<br>
On Wed, Oct 15, 2014 at 05:09:41PM -0500, Jon Heizer wrote:<br>
> ><br>
> ><br>
> >><br>
> >> From that "Actions may be taken in future to actively<br>
block the use of<br>
> > this 'JSON' grabber because of the damage it may cause to<br>
the integrity of<br>
> > the MythTV database." Elaborate? How does it hurt a<br>
mythtv installation.<br>
> > Are you going to require packagers to include some sort of<br>
non-deletable<br>
> > binary to enforce this policy of actively blocking users<br>
from using their<br>
> > systems the way they want?<br>
> ><br>
> ><br>
> Do you want a non-MythTV executable modifying your<br>
database? Are you<br>
<br>
I do this all the time actually.<br>
<br>
If I were more squeamish about this sort of thing, I would<br>
probably<br>
not be using Linux or MythTV.<br>
<br>
> going try to ask MythTV developers to support that in the<br>
future when<br>
> things break? I think your are taking it all a bit far.<br>
<br>
You present a far too tempting target here.<br>
<br>
[deletia]<br>
<br>
<br>
All I am trying to say is everyone needs to stop panicking. Upgrade to .27.4 or make a DNS change and life goes on. Don't<br>
worry about JSON or anything else. There have been way too many<br>
emails over a problem that is no longer a problem.<br>
<br>
<br>
The problem is that you think we are panicking. This JSON upgrade to SD is something to celebrate, not fear. For existing SD users it provides more data, and potentially more flexibility than the existing XML solution. For folks in the rest of the world it might finally provide them accurate and reliable guide data where they may not have had it before.<br>
<br>
I think anyone talking about the JSON service is wondering why the community pushed for the workaround that keeps using the old XML data rather than going straight to JSON. The proof of concept provided by SD works, it could just use some refinement... I think the community could have focused on that and taken a step forward rather than maintaining the status quo.<br>
<br>
<br>
</div></div></blockquote>
<br>
If we had been given enough time and a US dev could find time to work on it then things would have been done differently. The 1st Nov deadline was a surprise to all including SD themselves.<br>
<br>
Since there is a working solution that only requires users to update to 0.27.4 the heat is off. A solution that uses a grabber in XMLTV that uses the JSON service is still considered the way to go so we don't have to maintain two different ways to grab EPG data.<br>
<br>
I really don't understand what all the fuss is about.<br>
<br>
Paul H.<div class="HOEnZb"><div class="h5"><br></div></div></blockquote><div><br></div><div>Paul,<br><br></div><div>Robert K announced alpha testing of the JSON grabber on the developer's mailing list almost a year ago, and has posted occasional updates on status since then. When I read the notice on the mythtv front page that said that the JSON grabber had been developed without consulting the myth development team, (and the general tone of that statement) I thought it must be a joke.<br><br></div><div>I think it is great that Robert E developed a replacement on the Schedules direct side of things that made a simple change possible. I also think that the work that Robert K and schedules direct are doing to provide even better listing data is great, and I have been surprised over the last year that no myth developers have jumped on the bandwagon. I realize that the developers have little free time, and have their own itches to scratch, so I can understand the lack of interest, but it still seems surprising.<br><br></div><div>I've been using mythtv long enough to remember the bad old days of using xmltv and its scrapers to get listing data, with the frequent breakage, having to install a new version of xmltv to fix that, and maybe having to update mythtv to account for the xmltv changes that had happened between versions. I was happy with the zap2it service, but it seemed to break occasionally. The schedules direct service has been very reliable, and I am happy to see that they are working to keep things going smoothly. <br><br></div><div>I am assuming that with a quality listings source like schedules direct, the xmltv data can be made as reliable as the current data-direct grabber.<br><br></div><div>Bill <br></div></div></div></div>