• 0 Posts
  • 16 Comments
Joined 1 year ago
cake
Cake day: July 9th, 2023

help-circle






  • Maybe yeah. Also got the sense from the strong opinions that this is a preexisting debate, presumably in the context of continuous workloads or cached arrays with minimal spindown intervals. In that context it’s true that rotational disks still often win in energy efficiency and robustness (assuming we’re comparing them to consumer SSDs and not the latest enterprise u.2 stuff that’s rated for continuous work).


  • Not sure what everyone is arguing about here. Clearly SSD is better for intermittent r/w, whereas HDD can be more efficient at continuous r/w (especially in terms of watts/TB)

    Just looking at specs should be enough to see that. SSDs can idle in ready state at close to 0 draw (~0.05w) whereas HDD requires continued rotation to remain ready. So consider an extreme case of writing for 1 minute then maintaining ready state for the rest of the day. For that the SSD will be far more efficient, obviously.




  • Thank you for your service.

    There’s an element of privacy fatalists around here who require no evidence for their claims and will doggedly ignore any evidence to the contrary. While I think zero-trust is a proper approach to security problems, propagandizing the technical aspect with hearsay and falsehood is useless.

    Many tolerate it thinking we share a common enemy, but they’re wrong. Ignorance is the enemy, and tolerating it is why the community of privacy advocates is being swallowed by the much much larger community of online conspiracy brokers. Anyway, thank you for not tolerating it and doing your part.








  • Septimaeus@infosec.pubtoPrivacy Guides@lemmy.one*deleted by creator*
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    8 months ago

    Agreed, though I might add that a number of manufacturers have been known to dabble in data brokerage as well.

    It might sound paranoid, but Android is built around data collection, and in practice it’s just a feeding frenzy. The carrier, the manufacturer, the ad platforms, the advertisers, the app developers, everyone gets pieces of you and none take responsibility for the pieces the others take, since it’s outside the scope of their offering.

    The best bet is a clean flash, Lineage or the like, and strictly open source apps. I’d encourage any user who can’t or won’t go through that process to stick to iOS. It’s not perfect but it has the best default privacy protections by a significant margin and the refurb market has many affordable units. Factory Android these days is a privacy nightmare.


  • Septimaeus@infosec.pubtoPrivacy Guides@lemmy.one*deleted by creator*
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    8 months ago

    Yeah they skipped past some likely questions. I can try to fill in a little.

    Apple users are assigned an advertising ID, but the user can reset (not disable IIRC) the ID whenever they want, so it might not be as useful to the carrier for profiling purposes. All that would give them is fragments of profiles that, without other identifiers like phone or email, might be impossible to associate with their customer.

    Android users tend to have numerous and more persistent identifiers available for profiling, and manufacturers have been permissive with carrier partners re: daemons, kernel extensions, and custom telecom apps. I think that’s what the article meant was unique to Android. Carrier tracking can just be more deeply embedded in these systems, beyond the obvious bloatware apps and widgets.

    Interestingly, Apple sells similar tracking functionality for custom provisioned commercial devices IIRC, complete with the uninstallable apps, enhanced telemetry, etc. So it’s not like they can’t or won’t track users as a paid service, they just have no reason to let carriers do it on their equipment.