• 2 Posts
  • 73 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle




    • Larger, OLED screen
    • Hall effect sensor sticks
    • Better rumble
    • Support for 2242 m.2 drives
    • Second SD card reader
    • Better cooling (I’d gladly have a lump in the back middle if it allowed for a quieter/better fan)
    • Better accessory connection options (eg a standard for attaching stuff like extra batteries to the back) - I would prefer this to adding more battery (ie weight) to the unit itself.
    • Tweaks to the back buttons so they work no matter where on the button you press
    • Some sort of charging dock connection standard to avoid the manual usb connection. Maybe just a usb-c on the bottom
    • Small case design change to prevent sd cards being snapped when opening (I haven’t done it, but only by luck)
    • Replace the carry case with a plastic cover to protect screen/sticks like dbrand’s (or at least make it a lot smaller)

    Better performance/more ram would be good too I guess but honestly having a unified platform with fixed specs to target has a lot of benefits.





  • dan@lemm.eetoProgrammer Humor@programming.devOrder
    link
    fedilink
    English
    arrow-up
    34
    ·
    edit-2
    1 year ago

    Lossless compression algorithms aren’t magical, they can’t make everything smaller (otherwise it would be possible to have two different bits of input data that compress to the same output). So they all make some data bigger and some data smaller, the trick is that the stuff they make smaller happens to match common patterns. Given truly random data, basically every lossless compression algorithm will make the data larger.

    A good encryption algorithm will output data that’s effectively indistinguishable from randomness. It’s not the only consideration, but often the more random the output looks, the better the algorithm.

    Put those two facts together and it’s pretty easy to see why you should compress first then encrypt.



  • They collect:

    The categories of websites you visit, but not the URL itself

    The information collected includes categorized web browsing history that shows how long and how often you visited specific categories of sites (i.e. social media, personal finance, or news). All site visits are classified into one of 30 categories. We do not collect URLs, web pages titles, or user-specific content without explicit permission from you.

    Software usage: for example, frequency and duration of application usage such as Intel® Driver & Support Assistant, but not the application content itself such as specific actions or keyboard input.

    Feature usage: for example, how much RAM you usually use or your laptop’s average battery life.

    Other devices in your computing environment

    Includes universal plug and play devices and devices that broadcast information to your computer on a local area network: for example, smart TV model and vendor information, and video streaming devices.

    (the emphasis is mine, as is the minor reordering to not hide the browsing behaviour stuff at the bottom)

    Yeah that’ll be a no from me there, bud.









  • I mean. Sorta.

    When you use some service you have some expectation that they’ll treat you fairly and predictably. Sure their Eula let’s them do whatever the fuck they want legally but that doesn’t change the fact that if they opt take certain actions (like arbitrary taking people’s usernames) then they risk losing user trust.

    If the admin just took your username one day would you just quietly accept it? What if they edited or deleted your comments? Would you just shrug and say “well it’s their site they can do what they want” and just walk away?

    Look what happened when Spez got caught editing posts on Reddit, for example. Massive user outcry.

    Dude’s allowed to be annoyed about it.



  • This. Websites should use standard mechanisms by default, and optionally layer user preference stuff on top.

    Every time you override some default browser behaviour you risk breaking workflows, harming interoperability and accessibility, etc.

    OP would be better served with a grease/tamper/violentmonkey script to alter links (or inject a base target tag, whatever) than lobbying developers to change things. (Or, yknow, learning to use the middle mouse button).