2013-01-20, 03:15
You can't just zip it up and give it out because the keys involved are linked to my personal account.
Quote:P.S
Running Frodo RC3 on Windows 7 64b
(2012-12-24, 17:15)yabsie Wrote:since netflix now supports chrome-os (linux kernel) there is a standalone client that can play netflix streams in linux (however it doesnt run in the web browser). and i think it is only x86 (raspberry-pi runs on arm cpu).(2012-12-21, 09:27)kebone Wrote:(2012-12-21, 03:45)patseguin Wrote: Is there currently a Frodo version of the Netflix addon?
negative
(2012-12-24, 16:40)ktjensen Wrote: Is the plugin working well on a RASPBERRY PI Linux box yet?
From what I understand, unless some one figures out how to get MS silverlight working on that version of linux there is no hope of getting netflix to every play on it.
So you will be list, search, add things to yoru queue etc, but not play any movies. Which is somewhat less fun. somone hinted at that there may be a way a page or two ago, but then they went silent.
Quote:This is the process of making a protected request:For the majority of us struggling with having access to the general menu structure but not the queues, we are probably falling off the rails at about point 5. Because the information from step 4 is not being stored, it is not accessible to make the request in 5 then the tokens and user id are not received in step 6.
1. You send a signed request to the Netflix API that tells the API that you are about to send over a Netflix subscriber who wants to give your application permission to access his account.
2. The Netflix API verifies the signature on your request and sends your application a request token and a token secret.
3. Your application then creates a special one-time-only link for your subscriber to click, that includes the request token, your consumer key, your application's name, and where you want us to send your subscriber once he's signed in.
4. If the subscriber clicks this link, Netflix will show him a secure login page on its domain (this way, he only has to give his password to Netflix, never to a third-party. The login page will warns the subscriber that he is about to grant your application access to his Netflix account, lists some of the bad things that might happen if your application is hostile or broken, and gives instructions for how the subscriber can revoke this access. If the subscriber signs in and you've told us where to send him, we will send him to the callback page you specified in step 3. (If you haven't given us a callback, the subscriber will need to find his way back to your page himself.)
5. When the subscriber lands on your callback page, you'll make one last request, using your consumer key and consumer secret, and the request token and token secret you received in step 2.
6. If everything checks out, the Netflix API will send you an authorization token, an authorization token secret, and a user id. These, along with your existing consumer key and shared secret, are your keys to your subscriber's account. They will remain valid until such time as the subscriber revokes your access, so if you store these keys securely you won't have to go through this process again the next time the subscriber accesses your application.
(2013-01-22, 16:44)ktjensen Wrote: and still this does work with PLAYON to get access to NETFLIX and serve up movies. just not direct with the plugin discussed in this topicI wanted to use Playon - it seems like a much more elegant solution. But it downgrades every video to SD, which is just ridiculous in this day and age. I looked at their forum and they have been making excuses for not having HD since 2009
PLAYON emulates a web page in a browser. then restreams the browser connection. its difficult but functional.
(2013-01-22, 22:21)Revengeance Wrote: I wanted to use Playon - it seems like a much more elegant solution. But it downgrades every video to SD, which is just ridiculous in this day and age. I looked at their forum and they have been making excuses for not having HD since 2009And, you have to pay for it.