Also note their persistent refusal to implement TLS for their web access.
This attitude alone tells me never to trust this project ever, even when they finally should use TLS.
Sadly there is no other FOSS out there that combines remote support with good NAT traversal.
Existing remote access tools such e.g. VNC all do not offer NAT traversal and are incredibly hard to setup.
All FOSS web/phone conference tools offering screen sharing refuse to implement transferring Cursor/Keyboard control.
Probably because it is not so easy, but mostly, I guess, out if fear for diffuse security problems.
Too bad people then will be compelled to use this absolute mess...
They often fuck it up on purpose even. Like back then their legendary "mp3" players that wouldn't actually play mp3 files. Currently their ridiculously short security update available. 3 years only for their 1600$ phone. at least somewhat increase from the 2 years they offered previously.
it's a 2nd sealed chamber and shares some sensor parts. Some parts are different, so it's not perfect of course, but much better as the requirement of regular manual calibration. Sensirion SCD30 for example, where you can even see the Y shape of the gas chambers.
But that's the whole point? That you can user your own device as a general-purpose computing device, not only as a media-consumption device limited by arbitrary restrictions the vendor of the device can pose on you?
It does not grant root by default, quote: "Whitelist access control
Only App that is granted root permission can access `su`, other apps cannot perceive su."
I highly recommend Dual-NDIR sensors that bring their own volume of calibration gas. Auto calibration is not practical in any serious indoor monitoring use case.
Audiobooks are usually mono, so 700 kbit/s for uncompressed CD quality. To me parent's numbers sounds like uncompressed. I suspect something went wrong with de-drm/decoding.
Should be more like 48 kbit/s for basically transparent mono voice with opus. At this rate, 9 solid months will fit into 142 GB...
That makes it even worse. They apparently do not even try to make it secure and willingly exclude some patches.
Reminds me of "security by management risk acceptance"
Yes. The main culprit is bloat and the demise of shared libraries. Application devs are getting lazy. Everybody just packages up their whole dependency tree and slaps on a virtual machine with their own memory management. This would be fine if you had only one app ever running, just like those devs on their high-end maxhine. But no. Soon as you have multiple browser, electron and java apps running, snaps, rust, nodejs, you name it, each is gobbling up memory like crazy, and eve 32 GB are exhausted in no time.
Android 10 itself is technically still supported with security updates, so nothing wrong with it, if the device manifacturers support the kernel, drivers and firmware blobs... You not caring about those security fixes means you don't use video hardware acceleration, no Bluetooth, cellular, wifi, or any kernel features? It totally agree, of course those old^H^H^H quite new phones shouldn't be scrapped, they should be supported by the manufacturers for, like, 10 years. Instead of buying deprecated-by-design electronic waste, we should just boycott them in the first place and support decent manufacturers instead. In the case of Sony, this will solve itself as it looks like they will give up making phones any time soon.
Nope. Not a great choice at all, specifically not last year's model: Sony only promised 2 years of security (!) updates. That means you'll get about one year maximum of supported use, after that you should scrap it. Much too expensive ans wasteful. Pixel 6 has a 5 year promise which is not great but the best you'll currently get for an Android phone.
That's the story of Sony in general. They had great tech but their content division always forced the consumer electronics division to gimp that tech in random ways, which led to the tech failing on the market.
But all those hipster bicycles don't have a rack and people use backpacks instead, even carry their bike locks like a sash, just. because racks apparently look uncool.
If they wouldn't stop publishing security uogrades exactly 3 years after each phone's first market introduction in Japan, I would have bought one...
Oh, and they cripple the camera permanently when you root the phone.
Just have a separate work phone and leave that at home. It's better for a lot of other reasons too regarding you controlling your phone instead of your employer.
Nah, they really dropped the ball with updates. 2 years of security updates for a 1200€ phone?? Note the clock starts ticking as soon as they announce the phone, and it takes ages before it is actually available, resulting in about 1.5 years of security updates. This is laughable for a flagship and should result in a boycott.
Why did you buy a device that's patronizing you in the first place? You bought a device that is even advertised as not being fully under your control, then it turns out it's actually not under your control. Meh. Put Linux on it and next time buy an normal PC.
Unreliable for use as medical sensors, at least that's what the study says. About your general sentiment: I am sorry that you feel you don't have reliable humans in your life.
Who would profit? Dog nutters. Currently they go to great lengths to introduce dogs everywhere, they even fake ESA doctor's letters to illicitly profit from service animal laws. Surely they would fake studies or write overly positive articles about studies.
It seems many people build their identity on liking dogs. So if you say anything remotely negative about dogs, these people feel personally attacked and act accordingly.
One who does not like dogs is at least weird to them, if not outright evil. I hear it is the worst in the US, but it gets increasingly common here as well.
Some of them will try everything to get more dogs involved, including: classroom pets, pets in offices, fake emotional support animals. I wonder if they also manipulate studies like in TFA...
Yes, it is mathematically ensured that the coin issuer cannot link the actual coin to the account you are buying it with. No blind trust needed, check the math yourself: https://en.m.wikipedia.org/wiki/Blind_signature
For the specific implementation, you can check the taler source code.
Is is possible to trace back a gift card to the store that sold it? Maybe even the date and time? Then get the surveillance tape... If you pay with the same gift card more than once, all those transactions can be linked.
If you buy a coin, you have the bank sign it blindly, that means, after you unblind it, it is mathematically not possible to deeive any correlation between the coin and what the bank saw. The bank only knows the value of the coin(s) you bought, not the identity, and, apparently this seems enough to fulfill those regulations? If you draw cash from an ATM, the bank also has an exact record from that ATM. And in addition might have recorded serial numbers of the banknotes...
The exchange gets information about the merchant, but not about the purchaser (at least from the coin. The merchant might submit info about the purchaser such as the shipping address, but that is independent of the payment mechanism). That's strictly less than any credit card transaction.
In addition to the huge advantage of not needing to get cash from an ATM and physically carry it to the card vendor:
Transactions made on the same eGift card wallet are tied together. With Taler you have a wallet with coins you can spend separately, and which cannot be correlated, neither by your bank nor the merchant.
What makes you believe anyone (except maybe the purchaser themselves) needs to maintain records about the purchaser? As far as I understood it, their claim is that exactly this is not necessary.