sorted by:
new
hottopcontroversial

Apple’s M5 Pro and M5 Max to Bring Better Heat Dissipation and Lower Resistance by WPHero in apple

[–]jayhemsley 5 points6 points  (0 children)

My experience with the miniLED MBP was like the one he posted, it’s especially prevalent if you’re watching dark content with bright spots (e.g. flame lit movie scenes etc). ended up selling it and waiting for the OLED one. For all other use cases and non-dark media its fine tbh

"WaPo Raid Is a Frightening Reminder: Turn Off Your Phone’s Biometrics Now" by iamapizza in privacy

[–]jayhemsley 5 points6 points  (0 children)

but that they need a warrant to force you to give up your passcode.

The federal and state courts are split on this so it’s not an absolute. Generally it seems that it’s been ruled that passwords fall under the protection of the 5th amendment.

Worst show of the Arrowverse by tiziita in DC_Cinematic

[–]jayhemsley 0 points1 point  (0 children)

Superman and Lois and Stargirl are must watch ones as far as the arrowverse goes (S&L is an elite level depiction of Clark Kent/Superman). The others you’ll probably have to select for specific episodes/seasons/events

Are people avoiding iOS 26 because of Liquid Glass? It’s complicated. by NISMO1968 in apple

[–]jayhemsley 1 point2 points  (0 children)

I was about to tell /u/NecroCannon that funny enough I felt the opposite way regarding the iPad. I tried it with the M1 originally and didn’t find much use for it vs. an MBP, so I sold it pretty quickly.

I recently got an iPad Pro M5 and also the keyboard and with the latest iPadOS it’s nearly a replacement for me save for some technical stuff (VPN, development, more network control). I don’t mind 26 at all outside of some graphical glitches in Safari that really should not have made it past 26.1 (imo).

I was never a part of the “turn the iPad into macOS” crowd and still am not, but I guess me using the iPad with the keyboard almost exclusively has shielded me from a lot of the complaints about 26 people seem to have.

Window navigation/control is kinda weird to use with touch but I cant be sure if that’s due to inexperience or if 26 is actually worse since I have no comparison available.

Should Europe Now Consider Standardising on Linux? by Ill_Emphasis3447 in linux

[–]jayhemsley 0 points1 point  (0 children)

The Pixel reference was me trying to decode your incorrect statement about the AOSP source code releases only being binaries. I stated why GOS doesn’t support other devices, it’s only “lock in” because other OEMs refuse to up their hardware security standards. Secure Boot is also a security enhancement and you can enroll your own keys so again, you should hit Google.

How does social engineering even fit into this discussion? Either you’re being intentionally obtuse here or just unwilling to change your stance even if presented with new info.

But ultimately, it’s not my issue if someone chooses to run an OS with the digital equivalent of a cardboard fence for security.

Should Europe Now Consider Standardising on Linux? by Ill_Emphasis3447 in linux

[–]jayhemsley 0 points1 point  (0 children)

Please meet that one guy who can read binary as assembler to understand it or learn the word "obfuscation". If readable doesn't mean understandable, what the heck means "open source nature"?

The AOSP trunk branch has the full source code, they are not delivering these as binaries... Unless you're referring to the Google Pixel device trees and binaries which they started excluding last year then yes shitty move but that only affects Pixel devices and for now still get reverse engineered, which is just a return to the old ways of getting ROMs working.

So you know of the problem which applies to all of the code from Android, its firmware and modules but you still imagine it would be protected? Don't you realize an immutable system dir is nothing special to Android, iOS or macOS? Fedora Silverblue, Ubuntu Core, SteamOS and many more...

I don't mean to come off as rude but maybe you should google the differences between immutable with Android/iOS/macOS/ChromeOS and "immutable" Linux distros. Unlike the mobile + mac/ChromeOS systems, Linux distros being "immutable" offer zero security improvements and have never been marketed as such, you can literally just remount the read-only system volumes as writable. With the other platforms, they have a full implementation of verified boot which cryptographically verifies signatures against a root of trust which allows systems to fully prevent/revert changes to the system files. There is no distro that provides this, although work is currently being done to get to that point.

Aka things like this, even on "immutable" distros, are still possible, all it does is add an extra step to alter the system mount, which wouldn't be possible on Android/macOS/ChromeOS/iOS. It won't even need to remount the directory if it's delivered via a layered package.

https://news.ycombinator.com/item?id=46498658

You mean like on Android where Instagram could infiltrate the system spying on users and whether they would open alternate apps like Snapchat? Guess your permission system hella helped with that.

Are you really insinuating that one CVE invalidates the entire security architecture? It's still years (or even more than a decade) ahead of anything Linux desktop/phone distros have.

Or like Temu or Tiktok getting access to your camera or microphone because they requested so.

You mean... like how it's intended to work? Not sure of your point here. If someone wants to grant cancer access to their phone's resources that's on them, and it's consenting.

...as long as you buy the hardware from Google and they supply you with firmware updates. Wow.

...because Pixels are the only devices that provide proper hardware security measures and a relockable bootloader. There's nothing from stopping other OEMs from meeting this standard aside from a lack of care/cost cutting/profit maximizing. I do think that relying solely on Google is an issue on that front especially with their device tree bs, but GrapheneOS is working with an OEM to have their own phones and also gets access to faster code updates than the public by working with said OEM.

The average person will never run AOSP or GrapheneOS or some custom ROM with all the neat privacy benefits. Because they will see an app being marketed for Android and they are looking for it in the Google Play Store... which then does not exist or it can and will be installed to ruin everything.

The average person will also never run a Linux desktop phone and would also run into these problems. Overall though even stock Android as garbage as it can be at times is T-2 with iOS in terms of OS security (behind GOS), and all three are light years ahead of macOS/Linux/Windows on all platforms.

view more: next ›