pretty much the title.

  • TechnicallyColors@lemm.ee
    link
    fedilink
    English
    arrow-up
    19
    ·
    2 years ago

    Maybe HDR on linux? I’m fairly clueless about how it all works under the hood, but I’m currently on debian 12 and I’m hoping that by the time 13 comes around it will just work without me needing to do any manual system tweaks. As I understand it, it’s currently semi-working or fully-working in KDE6, but I’m still on KDE5 until debian 13 comes out.

  • Xavier@lemmy.ca
    link
    fedilink
    arrow-up
    13
    ·
    2 years ago

    The Solid protocol specification or anything similar (it doesn’t have to be that specific protocol).

    For example, registering to a website or service actually creates a local secure database/bucket/pod where that website/service organizes/sort/manipulates our data and stores all generated modified data/metadata within our local personnal server, every time we interact with that same external website/service it gets access to the database/bucket previously created. (Ideally) no personnal data should be stored on external servers/machines outside our control and without our explicit consent.

    • Feathercrown@lemmy.world
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      2
      ·
      2 years ago

      I hope this works out so much. Tim Berners-Lee even endorsed it! Unfortunately, a lot of these super cool ideas come with the limitation of needing a personal server. I think if we really want this stuff to happen, someone needs to start selling modem/router combos with a home server built in. You could add Solid, local media share, etc. by default, and it would be a great place to install Home Assistant or run a Minecraft server from.

    • Swedneck@discuss.tchncs.de
      link
      fedilink
      arrow-up
      1
      ·
      2 years ago

      My money is on IPFS, because it’s so simple (like, in principle, obviously it’s complex under the hood). It’s not fancy, it’s basically a better version of torrent and only handles static data, but it does that really fucking well.
      It takes any data you add to your node, splits it into small blocks, does a fancy hash of those blocks, and then builds a tree of pointers that point to pointers that point to the constituent blocks. This means that any identical blocks have the same address, and thus only need to be sent once! And the same goes for anything that ends up being identical in structure, it has the same address and only needs sending once, and if for example two people rip a copy of the same obscure DVD and host it on a node, they will both provide the data to downloaders despite never having interacted with each other at all!

      This is of course massively boner-inducing for anyone who cares about archiving stuff.

      In effect it does the same thing that HTTP or FTP or whatever does, but in a modern and fundamentally decentralized way. You don’t care where the data comes from, you just request the ID from whatever nodes you can see, if they don’t have it they forward the request to those they can see etc etc, if anyone has it they reply to you and start sending the data, and then you do some fancy math to verify that it’s correct.

  • comfy@lemmy.ml
    link
    fedilink
    arrow-up
    12
    ·
    2 years ago

    JPEG-XL (someone already mentioned it as .jxl below) image files.

    • competitive with AVIF compression levels
    • not recycling video compression, so you get benefits like progressive loading
    • JPEG transcoding - can take existing JPEG files (so much of the existing images online) and shrink their size by ~20% with literally no change to the presented image, and this is easily reverable. The amount of data this would shrink without risk of altering the data is HUGE.

    There are a ton of other benefits but those are the three I’m most excited about.

  • Read Bio@lemm.ee
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 years ago

    Wayland, has a bit of compatability issued but xorg is pretty aging ngl.

  • Swedneck@discuss.tchncs.de
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    2 years ago

    Basically everything from https://www.protocol.ai/work, bar the blockchain stuff which i can only assume they’re doing to milk investors to fund the actually good projects.

    libp2p abstracts away networking so you can simply point to a peer ID and the computer figures out how to connect to it (though you can of course specify how to connect if you wish), and it preserves connections across different networks among other stuff.

    IPFS is basically just torrent but better in every way, foremost in that you can just slap some data onto an IPFS node and if anyone else happens to be serving the same data then you’ll both automatically be valid providers, despite never having talked to each other in any way. No more needing to search out a magnet link, just seed whatever data you want and anyone requesting the data from the network will automatically find you.