[–] 4 points 2 weeks ago (3 children)

There are plenty of XMPP clients out there that work great... finding one that supports all the features you actually care about...now that's the hard part. XMPP has too many opt in extensions and it's very hit and miss with clients

  • source
  • parent
  • context
  • [–] 1 point 1 month ago (4 children)

    We're not comparing to C, we're comparing to a theoretical java that has primitive unsigned ints since that was your original complaint. Ofc C is faster, java is faster to write than C though. I write both, there are different tools for different jobs

  • source
  • parent
  • context
  •  

    I've been using duckduckgo for years ever since I degoogled but I'm increasingly annoyed by its complete lack of IPv6 connectivity. I use NAT64 and so it works fine but it bothers me to use services that don't have v6. Does someone have a good non-google IPv6 search engine that's privacy respecting?

     

    I'm curious about something so I'm going to throw this thought experiment out here. For some background I run a pure IPv6 network and dove into v6 ignoring any v4 baggage so this is more of a devils advocate question than anything I genuinely believe.

    Onto the question, why should I run a /64 subnet and waste all those addresses as opposed to running a /96 or even a /112?

    1. It breaks SLAAC and Android

    let's assume I don't care for whatever reason and I'm content with DHCP, maybe android actually supports DHCP in this alternate universe

    1. It breaks RFC3306 aka Unicast-prefix-based multicast groups

    No applications I care about are impacted by this breakage

    1. It violates the purity of the spec

    I don't care

    What advantages does running a /64 provide over smaller subnets? Especially subnets like a /96 where address count still far exceeds usage so filling subnets remains impossible.

    view more: next ›