![]() I may spin up a quick DNS server for people to use, but I understand there's a lot of trust involved in using someone else's DNS server, so you may want to run your own. The biggest barrier to using my public server is that you'll need to be running your own DNS server. I'll know more as I get logging and metrics in. And it's sitting on a very small instance type on AWS, so unsure what kind of traffic it can handle just yet. Quick warning that i'm not considering this a "production" server yet, as i'm sure i'll be tweaking things. I'll open source my code soon, but for now the server is live and able to be used by the public. It fixes the "no internet connection" errors, gets login working (for any username and password) and gets the Netflix app loading again. My personal implementation is only meant to get the Boxee box in a working state again. I'm not 100% sure whether the project is tested and working, if they're around they can speak to it. u/st4rl has been working on an implementation of the cloned server and also a DNS server in one codebase. This project isn't public yet, and i'm not sure if theres any plans to host a public server, but i'm sure when the codebase is in a better state, he'll share that work with us. His project is aiming to be a full featured replacement. He was kind enough to share his code, which enabled me to build out my simple version of a cloned server. u/cigamit has had a working implementation of this for years. Happy to say that as of today there are multiple implementations out there, and that my public hosted version of this is online and available to use. Several people have been working on cloning the servers since they were taken down, in an effort to restore functionality to everyone's Boxee Boxes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |