pretty much the title.

  • comfy@lemmy.ml
    0·
    3 days 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.

  • brisk@aussie.zone
    0·
    3 days ago

    IndieWeb in general and the h-entry and WebMentions specifically.

    Collectively they promise a highly personalised web experience that maintains ownership of your own content while encouraging socialisation across platforms, while avoiding the sustainability and scale limitations of activitypub.

    I also want to see XMPP/OMEMO have a comeback.

    • Océane@jlai.luFrançais
      0·
      2 days ago

      Hi, does it have any advantage over greping your RSS feeds for your blog’s URL?

      • brisk@aussie.zone
        0·
        2 days ago

        What is “it”? Webmentions? Webmentions can be sent from anywhere, not just places you’re actively monitoring. They can be used for example to create a comments section on your blog which amalgamates comments from various syndication points.

        That is, you post to your blog, you post a link to your blog post to twitter/Facebook/lemmy etc, and comments or replies from any of those can show up on your blog itself if you so choose.

  • Mwa@lemm.eeEnglish
    0·
    3 days ago

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

    • khorovodoved@lemm.ee
      0·
      3 days ago

      I doubt it. Today there is a huge trend towards censorship in the world. And ECH is exactly what a censor would not want. It is already blocked in Russia after Cloudflare enabled it by default and I would expect it to be blocked in the west “for anti-piracy reasons” very soon.

      • Domi@lemmy.secnd.me
        0·
        3 days ago

        ECH is intended for privacy, not for circumventing censorship.

        If the next TLS version enforces ECH, plaintext SNI will die out at some point on its own.

    • sga@lemmings.worldEnglish
      0·
      4 days ago

      for me, currently the problem is over reliance on Cloudflare, which is yet another big tech company

        • sga@lemmings.worldEnglish
          0·
          3 days ago

          i may be wrong here, but if i remember correctly, in ech, essentially our first communication is done with some central server (which as of now is mostly cloudflare) and then they make some connection with target server, and then a channel is established between us and target. my google-fu brought me this , which is basically this only

          https://cf-assets.www.cloudflare.com/zkvhlag99gkb/3C9ceBTx5AQXu8tS0lgzdF/55ea89f5a56843db15296b2b47f7b1c2/image3-17.png (https://blog.cloudflare.com/encrypted-client-hello/)

          I am unfamiliar with QUIC, and quick search basically tells it is kinda like multilane highway for udp.

          If I have to compare, (not a network engineer or a person who has studied networking, to me anything beyond the simple protocols seems magic), QUIC seems like a techt which is only used after you have made connection with target, so its implementation is google independent (they seem to be lead developers for this). Whereas in ECH, cloudflare are the primary devs, but also the holder for the public keys (someone else can also be the holder, but i dont know of any other provider currently, maybe my lack of knowledge here)

          Essentially just an extension of your point that implementation is lacking

          • Domi@lemmy.secnd.me
            0·
            3 days ago

            essentially our first communication is done with some central server

            No, the first communication is made with your DNS server to fetch the key for encryption from an HTTPS record. If a record with key is found it is used to encrypt the Client Hello, otherwise it falls back to the unencrypted variant.

            Cloudflare is not involved, unless you are hosting your domain through Cloudflare of course.

            I am unfamiliar with QUIC, and quick search basically tells it is kinda like multilane highway for udp.

            QUIC is primarily used for HTTP/3. The protocol was engineered and proposed by Google, same as with ECH and Cloudflare.

  • Xavier@lemmy.ca
    0·
    4 days 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.worldEnglish
      0·
      4 days 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.

  • terraborra@lemmy.nz
    0·
    4 days ago

    VRR that works with multiple monitors connected. Unfortunately that’s an Nvidia driver issue rather than a missing Linux protocol, so could be waiting a while.