Huh, you’re right. But a few weeks ago I was definitely able to download via Fido. Maybe try that.
Huh, you’re right. But a few weeks ago I was definitely able to download via Fido. Maybe try that.
Never had an issue getting an iso from them via Mullvad.
Mattermost does not have E2EE to my knowledge.
Not E2EE though, or at least not fully.
XMPP only does it with certain client extensions. And Matrix only does it when the rooms are set up this way. SimpleX does what you want, but is kind of unintuitive for the average user.
I say go with Signal, it does what you want and is idiot-proof.
I didn’t have much luck with Bottles in the past, but this is entirely anecdotal.
Consumer CPUs were lacking ECC reporting, so you never really knew if ECC was correcting errors or not.
Shit, this kinda screws with my plans to use the A380 as a transcoding card for my server.
There’s a way to run the client on Linux now? Awesome!
Our data includes anonymized API calls to traditional search indexes like Google, Yandex, Mojeek and Brave, specialized search engines like Marginalia, and sources of vertical information like Wolfram Alpha, Apple, Wikipedia, Open Meteo, Yelp, TripAdvisor and other APIs
I don’t want to be that guy, but technically they said they are using traditional indexes like Google, not that they are in fact using Google. But I guess that is splitting hairs.
Also, maybe they just dropped Google from their indexes? And what’s more: Why does it matter if they are using Google at all, when the results are satisfying?
Knowing which indexes they are using exactly would be nice to know, though.
I don’t see how this is relevant to this at all.
Old smartphones, old CPUs/GPUs, some SBCs.
Depending on your jurisdiction. Big asterisk.
You’re right, I forgot about the on-the-fly transcoding abilities of Jellyfin for a moment. But still, the server should be able to handle whatever codec they choose in hardware.
Keep in mind at least your server should be able to decode whatever you choose in hardware, so AV1 might still not be a good idea depending on your current hardware and upgrade plans.
With current hardware support I would advise against using AV1 or even H.265.
I’d recommend to experiment with H.264 and low CRF values to see what quality loss and file size OP is comfortable with: https://trac.ffmpeg.org/wiki/Encode/H.264
Yes, the only real drawback is the single channel memory connection, but that’s rarely a bottleneck.
I’d recommend to go with some form of mini PC. If you don’t need much CPU power there are some very cheap N100 ones where you can upgrade the RAM.
Does this support other targets like twitch VODs?