<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 16, 2014 at 12:18 PM, Jon Heizer <span dir="ltr"><<a href="mailto:jheizer@gmail.com" target="_blank">jheizer@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Thu, Oct 16, 2014 at 11:06 AM, jedi <span dir="ltr"><<a href="mailto:jedi@mishnet.org" target="_blank">jedi@mishnet.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>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 block the use of<br>
> > this 'JSON' grabber because of the damage it may cause to the integrity of<br>
> > the MythTV database." Elaborate? How does it hurt a mythtv installation.<br>
> > Are you going to require packagers to include some sort of non-deletable<br>
> > binary to enforce this policy of actively blocking users from using their<br>
> > systems the way they want?<br>
> ><br>
> ><br>
> Do you want a non-MythTV executable modifying your database? Are you<br>
<br>
</span> I do this all the time actually.<br>
<br>
If I were more squeamish about this sort of thing, I would probably<br>
not be using Linux or MythTV.<br>
<span><br>
> going try to ask MythTV developers to support that in the future when<br>
> things break? I think your are taking it all a bit far.<br>
<br>
</span> You present a far too tempting target here.<br>
<br>
[deletia]<br><br></blockquote><div><br></div></span><div>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 worry about JSON or anything else. There have been way too many emails over a problem that is no longer a problem.</div><span class="HOEnZb"><font color="#888888"><div><br></div></font></span></div></div></div></blockquote><div><br></div><div>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.</div><div><br></div><div>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.</div></div><br></div></div>