VLC is a great way to work with AppleTV, if you are willing to trade a few more clicks and less meta data for being free. It is by far the gold standard of being able to play anything.
The file format issue, plus the simple interface (especially for older less technically inclined) makes infuse worth the $100 lifetime cost (especially with family sharing).
What hardware are you using for your LibreELEC? Pi 3,4,5? With an external drive?
Self-hosted is not a way to make things free. Just lower cost than subscriptions overall. Using the full *Arr suite, with Usenet, your own hardware, and client boxes gives the users better control of the content they watch, but requires a nominal input of users time (plus some technical expertise), as well as an investment of some money both one time and annually.
Infuse’s lifetime time cost, when viewed in light of the total reduction of subscription cost (and an improved control of content) is worth it. I would definitely not pay a monthly amount to infuse, although it’s possible.
So far as Jellyfin’s app… As its free, I have low expectations. They fact that the developers have paid Apple for the SDK and put it as a free app on Apple TV and iOS is incredibly kind of them. They have a fair amount of code to look after and open source developers rarely get enough love or money.
I realize most will say kodi or android TV, but I have to say that Apple TV with Infuse (or Jellyfin) is really simple and reliable. I say that with the assumption that you mean a client, not the server. I would definitely put it on a NAS at minimum.
Some relevant quotes to summarize:
But the videos weren’t clear enough to identify the exact make or model of the dark four-door sedan. The detectives quickly obtained what are known as tower dump warrants, which required the major phone networks to provide the numbers of all cellular devices in the vicinity of 5312 Truckee during the arson. And they slung a series of so-called geofence warrants at Google, asking the company to identify all devices within a defined area just before the fire. (At the time, Google collected and retained location data if someone had an Android device or any Google applications on their cell phone.)
…
There were 1,471 devices registered to T-Mobile within a mile of the house when it ignited. Using software that visualizes how long it takes a signal to bounce from a cell tower to a phone and back again, Sonnendecker narrowed the list down to the 100 devices nearest to the house. One evening toward the end of August, detectives roamed the area around 5312 Truckee with a cell-phone-tower simulator that captured the IDs of all devices within range. That night, there were 723. Sonnendecker cross-referenced these with the 100 from earlier, eliminating the 67 that showed up on both lists and likely belonged to neighborhood residents who could be ruled out. That left 33 T-Mobile subscribers whose presence in Green Valley Ranch in the early hours of August 5 couldn’t easily be explained.
…
That’s when another detective wondered if the perpetrators had Googled the address before heading there. Perhaps Google had a record of that search?
… birth dates, and physical addresses for all users who’d searched variations of 5312 Truckee Street in the 15 days before the fire.
Google denied the request. According to court documents, the company uses a staged process when responding to reverse keyword warrants to protect user privacy: First, it provides an anonymized list of matching searches, and if law enforcement concludes that any of those results are relevant, Google will identify the users’ IP addresses if prompted by the warrant to do so. DPD’s warrant had gone too far in asking for protected user information right away, and it took another failed warrant 20 days later and two calls with Google’s outside legal counsel before the detectives came up with language the search giant would accept.
Finally, the day before Thanksgiving 2020, Sonnendecker received a list of 61 devices and associated IP addresses that had searched for the house in the weeks before the fire. Five of those IP addresses were in Colorado, and three of them had searched for the Truckee Street house multiple times, including for details of its interior. “It was like the heavens opened up,” says Baker.
In early December, DPD served another warrant to Google for those five users’ subscriber information, including their names and email addresses. One turned out to be a relative of the Diols; another belonged to a delivery service. But there was one surname they recognized—a name that also appeared on the list of 33 T-Mobile subscribers they’d identified earlier in the investigation as being in the vicinity of the fire. Bui.
…
Seymour’s defense argued that, in asking Google to comb through billions of users’ private search history, investigators had cast an unconstitutional “digital dragnet.” It was, they said, the equivalent of police ransacking every home in America. The Fourth Amendment required police to show probable cause for suspecting an individual before getting a warrant to search their information. In this case, police had no reason to suspect Seymour before seeing the warrant’s results. But the judge sided with law enforcement. He likened the search to looking for a needle in a haystack: “The fact that the haystack may be big, the fact that the haystack may have a lot of misinformation in it doesn’t mean that a targeted search in that haystack somehow implicates overbreadth,” he said
…
After a five-month wait that Sandoval remembers as “gut-wrenching,” the court finally ruled in October 2023. In a majority verdict, four judges decided the reverse keyword search warrant was legal—potentially opening the door to wider use in Colorado and beyond. The judges argued that the narrow search parameters and the performance of the search by a computer rather than a human minimized any invasion of privacy. But they also agreed the warrant lacked individualized probable cause—the police had no reason to suspect Seymour before they accessed his search history—rendering it “constitutionally defective.”
Because of the ruling’s ambiguity, some agencies remain leery. The ATF’s Denver office says it would only consider using a keyword warrant again if the search terms could be sufficiently narrowed, like in this case: to an address that few would have reason to search and a highly delimited time period. The crime would also have to be serious enough to justify the level of scrutiny that would follow, the ATF says.
…
Meanwhile, another case—in which a keyword-search warrant was used to identify a serial rapist—is now before the Pennsylvania Supreme Court. If the warrant is upheld, as it was in Colorado, their use could accelerate nationwide. “Keyword warrants are dangerous tools tailor-made for political repression,” says Crocker. It’s easy to envision Immigrations and Customs Enforcement requesting a list of everyone who searched “immigration lawyer” in a given area, for instance.
Hugging face is repository and Machine learning hub. https://huggingface.co/huggingface
As an old IT guy I empathize with the control of data. I have my array of self-hosted servers and love my CLI.
With that said, the older I get the less patience I have for hacking it together and supporting it. I still prefer privacy, and indeed Firecore Infuse is “Private by design” by their own statement. It’s not open source and I am not clear if it’s audited, but for as long as it lasts I’m happy friends and family less technically inclined have a simple easy familiar interface which I don’t have to support.
I will say I’m impressed A Pi4 works so well for jellyfin streaming. I guess it’s not transcoding, so it’s just a database and file share.