Depends on the server you are using to host your media sever from. If you're using a Raspberry Pi, then you might not be able to support transcoding at all, definitely not for a 4K AV1 video and a lot of modern formats. So even if Apple TV can play it, the Plex app won't attempt it and will force transcoding from the server.
Even if your server can support transcoding, all transcoding results in quality loss, so if you want to enjoy your media in the best formats then you want to direct play. Just depends on the media you are playing and how much you care about the quality.
The official Plex app hasn't been updated to take advantage of all the hardware decoding support available on the Apple TV. I moved to Infuse, a paid third-app, which I use to stream my Plex media content.
Jellyfin official apps are sporadic though, so Infuse is popular for Jellyfin users because it is well maintained and allows you to direct stream content without transcoding as often as possible.
--
I'm also the developer of Aviato Media Server (https://aviato.media), which I just released publicly last week and is available only as a beta, and I am an ex-Plex employee.
> and it's "better for the environment" because every year you don't buy a new phone, the environment is happy.
This seems wrong. I am still on an iPhone Xs Max from 2018 and it still gets software updates. It looks like the last software update on the G6 was in 2020. The lack of even security patches limits the life of the phone for many people.
The primary reason I'll eventually need to upgrade is because of 5G support. Coverage is getting worse as 3G has been shutdown and all new towers are focusing on 5G. My battery life sucks now too, but that can solved easily.
PatientPal | Full-Stack/Angular Engineers | Boston, MA based | Fully Remote (US or Canada) | Full-time
PatientPal.com is automating the administration for medical offices, adding price transparency to the US healthcare industry. From appointment scheduling, confirmations, insurance verification, benefits analysis, out of pocket cost estimation, post-appointment review requests, providing patients their results/reports. From clipboard to claim.
We're growing and we're looking for senior and junior angular / full-stack developers to join our team.
I used Grammarly in the past and I stopped because the privacy issues were concerning. I switched to https://www.antidote.info/en, which works entirely on-device, without sending your data to a cloud service. They now do offer a fairly minimal web application that can be used if you have their subscription, but they offer a one-time purchase for the desktop application.
Similar to Grammarly, the growing use of AI-based pair programming tools, like Github Copilot and similar, poses similar serious privacy risks. While the intelligent autocomplete is helpful, it uploads large parts (or all) of your source code; which most companies should be very concerned about.
Actually, SSO is usually a requirement for even basic security audits. So SSO is essentially required for companies operating in specific sectors, regardless of their size. Healthcare and military contracts are two obvious ones, but any company dealing with sensitive information, going through SOC compliance, or similar will likely need to enforce SSO to enforce and audit access policies.
Besides, SSO is a major convenience. Assuming that SSO = large company is a flawed perspective, although, I understand the reasoning you're conveying. I believe, however, that only very small companies (less than four people) can easily avoid SSO, because it is complicated to deal with on/off-boarding employees, SSO helps.
And I agree with OP in most regards, for most services, advanced security controls should be available. I think it is far more likely that most companies segregating their security features are not secure by design, so the functionality they're offering is poorly implemented, and by restricting access they limit the amount of support they need to provide to those features.
Help build the perfect medical front desk automation. We’re a growing SaaS company, focused on adding price transparency and automation to outpatient medical practices. We offer services from collecting medical intake, appointment reminders and confirmations, appointment scheduling and rescheduling, and work in multiple specialties.
Looking for candidates who are experienced with production software and architecting systems are required. Looking for a capable engineer who can take a business requirement and help build the final product with a lot of autonomy. Experience with product management is helpful. Full-stack position.
Experience with Node.js, JavaScript, angular, rpa, serverless, lambda, dynamodb, Docker, aws, hl7, x12, fhir, production environments are all helpful.
This has been annoying for me. I build a healthcare EMR software, and the browser trying to autofill the employee's information into every patient field is often a problem. By accident we end up with patient's phone numbers, addresses, and emails being set to employee's information. Since its software, I don't have control over those employees, but we have had to put in recommendations to disable autofill in browsers being used to cut it down.
We've spent countless developer hours trying to work around password managers. I agree that sites shouldn't attempt to disable password management for login and sign up pages, but it's annoying how often these password managers do the wrong thing and break the user experience for pages… like Safari is doing for livewire-ui/spotlight.
I agree entirely. I've tried zsh and other replacements, but I keep coming back to Fish. It's intelligent, loaded with features, and ohmyfish adds a lot.
No other machine I connect to has fish, but for my own machines, it's my top choice. Still, I write a lot of utility scripts in bash for the compatibility and it can be annoying when I copy a command and I know it won't work because it uses some unsupported syntax in fish. Every now and then, and it is rare, I switch to bash locally to run something.
No one wants used products for "new" prices, but plenty of people would be willing to buy open-box items at discounted prices. It's a huge thing for appliances.
In most situations, however, things are simply repackaged and sold as new. Clothing, for example, is commonly returned; then hopefully re-washed before selling again as new. In most situations this applies to electronics as well, although electronics can be different. There are stories out there of people buying new SD cards that had photos on them. Most companies have a return center that processes returns, inspects them, resets them, and repackages them to be sold again as new.
Exceptions are when returns are sent to stores… like Amazon or Best Buy handle returns differently than returns going back to the manufacturer.
I don't think most stores would offer returns, except it is often forced on them buy credit card companies to protect their consumers.
American Express, Visa, and Mastercard all have some kind of requirement that the merchant allows returns (usually 14 days minimum). Otherwise the consumer can file a chargeback and the resolution will go to the consumer in most situations.
Years ago, there was a failed gaming device called a Stinky Board, it's a D-PAD controlled with your feet. I got one at a gaming convention and have never put it to good use. Now I have a reason to pull it out of storage.
Maybe I am missing something, but iOS 14 has had beta versions out for developers for months; I had been running iOS14 and Big Sur for testing for weeks. Apple has always had developer previews and at some point, when mostly stable, they often release public previews to get a few interested users involved in testing as well.
They've been working with developers for a long time on the new App Clips functionality and that's been open for developers to start working.
So I am not following what is this article is saying? It seems like they're suggesting that Apple should release iOS a few days after announcing, but, that isn't enough time for most developers to test and release updates for a major iOS update; but Apple never intended those few days to be the only time developers had.
Blockchains are meant as a data store. Archival, verifiable. But not easily searchable. There is no design on blockchain for advanced query languages/logic.
It seems like the OP is going after something like blockchain that adds querying. But I don't think blockchain syncing is designed well enough for client-side use, and the OP seems to want to use this database client-side in JavaScript. I think it would be possible to implement blockchain syncing with WebRTC, but WebRTC has some security risks for users (IP leakage mostly) so I am not sure I would start off with that as a primary communication channel.
I think this comes down to price. They are constantly buying drives and to avoid supply issues, it is acceptable to have a hard drive that fails to a certain degree, if the price is balanced.
It would be interesting if these reports included prices, but that might be a problem for Backblaze to reveal so much about their business operational costs.
I also posted to the github gist, this the sed command here is not cross-plataform friendly. You can accomplish the same thing with an awk command though:
Right. Firefox and Safari (iOS and desktop) haven't implemented the Clipboard.read functionality yet either, only Chrome has and it's only available on use action such as a click or keydown (and not available on touch or scroll events).
But they can copy to your clipboard for you, a lot of services use "Click to copy" features. But reading is much harder.
iOS before 14.0 appears to have allowed apps to read clipboard contents without making that clear to users. Now that you get a notification whenever an app reads the clipboard, it has become fairly clear a lot of apps are reading clipboards constantly. For what… we all wonder.
As a privacy-first company, for them to make any decision that is for performance but adds additional privacy risk shows they make the wrong decisions.
They also left this for over a year after being told about it and part of the only reason it was caught was that their browser app is open-source. What about all their closed-source services, like their favicon service their browser apparently relies on.
We shouldn't blindly trust any company and a privacy-first company should be willing to assume we don't trust them and therefore it is up to them to prove everything they do.
I get a few of the responses on their Github page are now non-helpful, but the big point here is that by DuckDuckGo taking this series of actions (implementing the browser like this, ignoring a valid bug report about it, and only reopening the issue after massive push from users) it shows that DuckDuckGo isn't as privacy-focused as I thought, nor many others.
I've been using DuckDuckGo as my sole search provider for several years now, on all my devices, but I'm concerned about what else they may have done in the sake of "performance" over privacy.
Even if your server can support transcoding, all transcoding results in quality loss, so if you want to enjoy your media in the best formats then you want to direct play. Just depends on the media you are playing and how much you care about the quality.