<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <br>
    <div class="moz-cite-prefix">On 23/10/2014 2:03 PM, William Jacoby
      wrote:<br>
    </div>
    <blockquote cite="mid:54494305.6090305@gmail.com" type="cite">
      <meta content="text/html; charset=ISO-8859-1"
        http-equiv="Content-Type">
      <div class="moz-cite-prefix">On 10/23/2014 11:55 AM, Jon Heizer
        wrote:<br>
      </div>
      <blockquote
cite="mid:CAF7qfvndBOd5Hw2Nw5YCo6WRzoei22gWsHir+zTZnfwmiE2YHQ@mail.gmail.com"
        type="cite">
        <div dir="ltr"><br>
          <div class="gmail_extra"><br>
            <div class="gmail_quote">On Thu, Oct 23, 2014 at 11:26 AM,
              Brian J. Murrell <span dir="ltr">&lt;<a
                  moz-do-not-send="true"
                  href="mailto:brian@interlinx.bc.ca" target="_blank">brian@interlinx.bc.ca</a>&gt;</span>
              wrote:<br>
              <blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span
                  class="">On Thu, 2014-10-23 at 08:53 -0500, Jon Heizer
                  wrote:<br>
                  &gt;<br>
                  &gt; As far as the chromecast, all the loop holes
                  getting closed you may have<br>
                  &gt; heard stories about<br>
                  <br>
                </span>No, I have not heard any stories.&nbsp; Could you
                expand on those?&nbsp; What<br>
                exactly are the details and problems?<br>
                <span class=""><br>
                  &gt; kept shutting me down too.<br>
                  <br>
                </span>So are you saying that your using Chromecast was
                only possible due to<br>
                loopholes?&nbsp; Surely nobody wants a technology solution
                based on loopholes<br>
                do they?&nbsp; Loopholes get closed, I guess as you have
                seen.<br>
                <br>
                Why do you need loopholes?<br>
                <span class=""><font color="#888888"><br>
                    b.<br>
                    <br>
                  </font></span></blockquote>
              <div><br>
              </div>
              <div>At first there was a general default video play on
                the chromecast that anyone could use without an API
                key.&nbsp; Some of the first released Chromecast apps used
                this. Ex: <a moz-do-not-send="true"
href="http://www.droid-life.com/2013/08/26/google-responds-to-third-party-apps-breaking-after-latest-chromecast-update/">http://www.droid-life.com/2013/08/26/google-responds-to-third-party-apps-breaking-after-latest-chromecast-update/</a>
                &nbsp; One of the first updates to the device removed that
                ability and required you to have your own key.&nbsp; Ok
                fine.&nbsp; Then when the final SDK was released they will
                only issue you a key if you are using their official
                SDK, which I was not in the slightest.&nbsp; I'm a website,
                not a Java/obj-c app.&nbsp; So I'd have to have apps acting
                as a middle man to get anything to work.&nbsp; After having
                to start over a few times I just haven't touched it
                since.</div>
              <div><br>
              </div>
              <div>I'm not saying Myth and chromecasts are a dead end,
                just from a website they are basically.</div>
              <div><br>
              </div>
              <div>Jon</div>
            </div>
          </div>
        </div>
        <br>
        <fieldset class="mimeAttachmentHeader"></fieldset>
        <br>
        <pre wrap="">_______________________________________________
mythtv-users mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.mythtv.org/mailman/listinfo/mythtv-users">http://www.mythtv.org/mailman/listinfo/mythtv-users</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://wiki.mythtv.org/Mailing_List_etiquette">http://wiki.mythtv.org/Mailing_List_etiquette</a>
MythTV Forums: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://forum.mythtv.org">https://forum.mythtv.org</a>
</pre>
      </blockquote>
      Not sure if you've heard of Matchstick, but it maybe a better
      alternative, unencumbered with the draconian restrictions of the
      Chromecast.&nbsp; It's well surpassed it's initial goals.<br>
      <br>
      <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://www.kickstarter.com/projects/matchstick/matchstick-the-streaming-stick-built-on-firefox-os">https://www.kickstarter.com/projects/matchstick/matchstick-the-streaming-stick-built-on-firefox-os</a><br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
    </blockquote>
    Are you guys sure that the generic player is dead?&nbsp;&nbsp; It is still in
    the documentation as not requiring an API key.&nbsp; You can't change or
    annotate it, but it will play video.&nbsp; <br>
    <br>
  </body>
</html>