deluge is probably the best for native gui. It doesnt have the amount of integrations as qb and it struggles with many thousands of torrents (or at least it did 10yrs ago), but otherwise a great client.
Otherwise there’s qui for qb which, while still a webui, is great.
I currently use the official Web UI in an isolated Chromium instance and made an automatic log in page so that I don't have to type in the password every single time I open it.
I add torrents to the qBittorrent instance using a Firefox addon. It's all a bit jank.
I started some work to make my own qBittorrent client for desktop; I don't care about mobile that much.
Qobuz always shows me the following message after purchasing (downloads are DRM-free FLACs):
> Certain works may be withdrawn from the service for legal reasons, such as a revocation of rights. The titles purchased will then no longer be available for re-download. Download your purchases quickly.
> I wonder how they use these feeds if that's only internal.
Perhaps they don't, it could be that the interface was written to a more flexible spec to allow for ongoing changes, and close to release they decided which features would be officially supported. In that case the method being used here is either deliberately kept around for potential future use, or is a bit of their tech debt.
It may also be something that is internally supported still because it is used in legacy apps that are still out there (some smart TVs have ancient apps and no upgrade path) but they don't want it used by new code as it will eventuality be removed.
In any of those cases, there is no guarantee it'll still be there tomorrow.
Fair point. TBH from Google I might trust a now-unofficial (or always-was-unofficial) API kept alive by some big legacy contract a little more than an actively published & encouraged one, unless the latter is also similarly protected!
(a little bit of self-promo but) If anyone is looking for an RSS reader that splits out shorts from videos automatically, I made my open source reader Serial in part for exactly this
On the "Space" sidebar I used to have a button list rooms outside of any "Space" and a button to list only DMs.
Now I still have the button to list rooms outside of any "Space" but now instead of a DM button I have "Home" which mixes both DMs and rooms outside of any "Space" so I need to click on that and then the "People" filter (which doesn't save so I can't just click it once and be done) to get rid off the rooms that I already have a dedicated button for.
You sure succeeded in removing duplication. Two buttons that did two different things caused so much duplication!
Now I will have to create a "Space" to add those "space-less" rooms so that they don't show up in Home.
Oh and on upgrade I had no button to view DMs at all as I disabled "Home" before but you didn't force re-enable it for people upgrading.
Message search on Element X Android when?
EDIT: Also the filters hide under another button when your sidebar is too small and if you expand it then it can take up even 6 lines.
EDIT: And now also noticed that favourites don't stay at the top, truly useless, thanks.
EDIT: Why is room sorting method global now… I used to have spaces with different sorting… the location of the button to change the sorting hasn't even changed so it still feels like if it was local to the space. Good UX.
EDIT: Since I ended up complaining so much, might as well say that the sidebar having the same colour as the chat panel is pretty ugly and makes the whole application blend in more when the chat should be the main focus. Also expanding the spaces is still terrible as it expands the space part of the sidebar and it is annoying to have to toggle the sidebar back, I don't want the sidebar to take 1/3 of my screen.
From what I found in UK banks will let 16 year olds to open an account independently.
You could also mail cash (Mullvad), buy a VPN gift card in a physical store or online or get something like a prepaid Visa/Mastercard or a paysafecard.
Even if that is not an option, it's not like age restrictions have prevented everyone underage from alcohol or smoking, people will find a some shady VPN provider or a friend to buy them one.
And also, the transaction can have a very useless business name.
I think Canon makes at least some of their sensors, and Nikon designs theirs and makes it at a third party I forget the name of that isn't Sony or Samsung but they still do use Sony stuff in a lot of their cameras.
I don't know about Pentax, Panasonic or OMD (formerly Olympus)
I think folks here have some idea how expensive chip fabs are. That's why only Canon is able to make their own sensors.
Sony makes sensors for pretty much everyone else. But it's well known that other folks e.g. Nikon have been able to get better signal-to-noise with Sony-made sensors than Sony themselves. I think Panasonic used to make their own sensors but with some recent re-org, that got spun out.
It's been widely rumored that Leica uses Sony sensors, but this gets repeatedly denied by people claiming inside information. We know that Leica was getting 24MP CMOS sensors from CMOSIS in the 2012 timeframe, but CMOSIS has since been acquired by OSRAM, and there hasn't been any verifiable information since then, whether confirming or denying a continued business relationship.
GPU video encoding is pretty much always optimised for real-time encoding, meaning that it can't run certain optimisations as it would increase the time to encode.
Compare x264 veryfast and veryslow presets. There is a quality difference at the same bitrate.
Additionally, GPU encoders don't have as many psychovisual options as CPU encoders as they would need to be included in the hardware and adding extra options to CPU encoders is much faster, easier and cheaper.
You could build a non-realtime GPU encoder, but there is not much point.
