I'm not nearly as salty about SMS because of the following differences from the WhatsApp scenario. Signal-SMS was only supported on Android, call it half of Signal users whereas a potential WhatsApp integration (or lack thereof) would affect nearly all Signal users. Then the Android users who have to reach others over SMS already have a built-in system app that does this, so they don't have to install third party app that exists to vacuum data. So the downgrade for the Android Signal user is in ease of use, not in overall security.
avidamoeba
In a statement to the publication, Signal president Meredith Whittaker says, “Our privacy standards are extremely high and not only will we not lower them, we want to keep raising them. Currently, working with Facebook Messenger, iMessage, WhatsApp, or even a Matrix service would mean a deterioration of our data protection standards.”
Ugh, okay Meredith, let's pretend it's impossible to handle this with user experience that makes the user acknowledge their conversation with a WhatsApp user is not secure. Meanwhile if the only viable way for this conversion to occur is to have WhatsApp on both ends, the situation less secure. So according to Meredith, the choice is between less overall security or not having conversations with people who don't use Signal. That could makes sense for her salary but it surely is a net negative for Signal users some of which will have to install WhatsApp since they won't be able to afford not to have those conversations.
Energy lost as heat during the power transmission. It's what makes the phones warm during wireless charging. That heat decreases the lifespan of the battery and makes the phone uncomfortable to use, which is why wireless charging speed is limited once the phone reaches a certain temperature. I specifically avoid using wireless charging on my Pixel to extend its battery lifespan since it will live for 7 years and battery replacement is expensive. New wireless charging standards could probably play with frequency and other parameters in order to reduce energy lost as heat, similar to how increasing the voltage in a circuit decreases loss to heat for the same cables.
Yeah, I was listening and found myself nodding many of the design choices. Yes I want 60Hz default, yes I don't want SIM slot on the side, yes I want the phone to be thicker and heavier to accommodate the durability and repairability and features... I'm clearly the target demographic for this device and Linus'es review felt like it completely missed the point. "It's not much more difficult to replace the Galaxy Note's battery" say what buddy?
but half the battery life in video decode means charging your phone twice as often even if you don't watch Youtube all day
Most of the power goes into the screen. The Pixel 8 has a ridiculously power efficient screen. I have one. It also costs $300 to replace. The Fairphone's is $100.
other phones have sliders or slots that will let you live swap either card without even taking the back off
Slots and sliders inevitably weaken the phone frame making it easier to break. They also cost more to machine.
even the fairest phone is environmentally costlier than rescuing an old second hand phone.
Replacing a battery to rescue a Pixel will run you $100-200.
Many design choices make a lot of sense when looked through the repairability, durability and cost of repairability lenses.
Their paycheques depend on it.
So you've listed some important cons. I don't see the why outweighing those cons. If the why is "I really wanna play with this." then perhaps that outweighs the cons.
BTW on production servers we often don't do updates at all. That's because updates could break, beyond what's expected. Instead we apply updates on the base OS in a preproduction environment, then we build an image out of it, test it and send that image to the data centers where our production servers are. Test it some more in a staging environment. Then the update becomes - spin up new VMs in the production environment from the new image and destroy the old VMs.
Standard, capitalist, non-unionized corporation. The exec layer and the major shareholders decide what to do with the revenue. Unsurprisingly they often decide to take as much as possible. Customers, users, employees have no leverage in the matter. Works as intended. 👌
One answer that's proven to work is by involving a lot of people's labor in the editorial/curation process. Similar to how posting/commenting/voting/moderation work on Lemmy, how it's worked on Reddit and other human-driven platforms. Corporations have proven on multiple occasions that paying for this labor is not feasible and so a system that depends on it should be corpo-resistant or capital-resistant.
Yeah, decentralized ownership or democratic ownership would be another way to achieve this. A federated system even if possible would almost certainly be less efficient resource-wise.
I guess airflow especially between the phone and the pad could mitigate the heat. I see some charging pads integrate this now.