• 17 Posts
  • 1K Comments
Joined 1 year ago
cake
Cake day: June 16th, 2023

help-circle






  • It gets worse - because ISPs are choosing NATs over IPv6,

    Yes, because they’re mostly pieces of shit, technically inept and unable to properly deploy IPv6 at a large scale.

    Either way IPv6 doesn’t fix everything as you’ll still need a real IPv4 to access a large part of the internet or some translation (MAP-T/MAP-E). Even if your ISP provided dual stack with a real public IPv6 + CGNAT / MAP-T IPv4 it would still be annoying as you wouldn’t be able to do port forwarding on the IPv4 and won’t be able to access your self-hosted services from a LOT of networks that are IPv4 only.

    There are two versions of MAP – translated (MAP-T) and encapsulated (MAP-E). In MAP-E IPv4 traffic is encapsulated into IPv6 using a v6 header before it is sent over the v6 network. At the network operator’s boundary router, the IPv6 header is then stripped, and the IPv4 traffic is forwarded to the v4 Internet. In MAP-T, the IPv4 packet header is mapped to the IPv6 header and back. The difference between the two options is evident in their names. MAP-E uses IPv6 to encapsulate and de-encapsulate IPv4 traffic, whereas MAP-T uses NAT64 to translate IPv4 to IPv6 and back.








  • It depends. They’re simply the most annoying drives out there because Seagate on their wisdom decided to remove half of the SMART data from reports and they won’t let you change the power settings like other drives. Those drives will never spin down, they’ll even report to the system they’re spun down while in fact they’ll be still running at a lower speed. They also make a LOT of noise.



  • not really for casual browsing use cases when pretty much 99% of all the major players in the browsing industry maintain a Linux port.

    Those users couldn’t care less about if Windows is supported or not. They wont send their 240 million computers to the landfill, they’ll just keep using them.

    Either way, Windows 10 22H2 EOL is set to 14 Oct 2025 and Enterprise LTS to 12 Jan 2027. I’m sure Microsoft will cave around January 2026 whenever the first 0-day for Windows 10 22H2 Pro goes into the wild and extends support for the Pro version to 2027 as well for no extra cost. For them this makes way more business sense than having 240M machines infected giving a poor image of Windows.




  • TCB13@lemmy.worldtoLinux@lemmy.mlLXD now re-licensed and under a CLA
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    11 months ago

    But it may never see much progress on the WebUI for instance while Canonical has paying customers pushing and asking for it. They may appear inactive and it seems there aren’t many people working on the project but who knows? Maybe they’re setting up their own image server, repacking images etc.

    Again, I’m all in favor of this change and I’ve a couple of systems running on both and will obviously migrate everything to Incus but I can’t ignore the fact that enterprise money pushes Canonical todevelop things.