Thomas SchäferGerade eine Datei "kaputt.txt" auf meinem Rechner wiederentdeckt.
https://www.haw-kiel.de/
https://www.hs-merseburg.de
sind wohl immer noch kaputt.
#Konfigurationsfehler , die durch #HappyEyeballs verdeckt werden
Anderson Silva@kmj Neither #WireGuard clients know #HappyEyeballs exists: In a Dual-stack endpoint, they first try an obsolete address and if it gets connected, then that’s it -_-‘
Petr Menšík 
@bagder I think #HappyEyeballs in curl should be mentioned. Very useful on lacking IPv6 connectivity. Https DNS record support is not it WGet, is it?
Dan Wing"Analysing the state of Happy Eyeballs implementations" by Patrick Sattler for APNIC, https://blog.apnic.net/2025/10/07/analysing-the-state-of-happy-eyeballs-implementations concludes with the observation "that slow A queries also slow down IPv6, even when IPv6 is not the cause of slower responses. This may contribute to negative perceptions of IPv6 and adversely affect IPv6 deployment."
Analysing the state of Happy Eyeballs implementations | APNIC Blog
Guest Post: The Happy Eyeballs algorithm supports IPv6 deployment by giving clients the ability to prefer IPv6, quickly fall back to IPv4 when necessary, and protect the user experience in either case. But how widely is it implemented?
Erik Nygren 
Cool set of tools linked to today in a presentation in the #IETF #HAPPYWG session:
https://www.happy-eyeballs.net/
It allows you to characterize the Happy Eyeballs behavior of a client, such as to see how much of a delay in DNS resolution or TCP connection response triggers a failback from IPv6 to IPv4.
See more details in Dave Plonka's talk:
asmwToday, when looking into #ipv4/#ipv6 issues, I learned about #happyeyeballs (https://en.wikipedia.org/wiki/Happy_Eyeballs).
Such a pretty name for such an annoying problem.
T_X
postmodernTIL "Happy Eyeballs" (aka RFC8305).
https://datatracker.ietf.org/doc/html/rfc8305
#happyeyeballs #rfc8305
https://datatracker.ietf.org/doc/html/rfc8305
#happyeyeballs #rfc8305
RFC 8305: Happy Eyeballs Version 2: Better Connectivity Using Concurrency
Many communication protocols operating over the modern Internet use hostnames. These often resolve to multiple IP addresses, each of which may have different performance and connectivity characteristics. Since specific addresses or address families (IPv4 or IPv6) may be blocked, broken, or sub-optimal on a network, clients that attempt multiple connections in parallel have a chance of establishing a connection more quickly. This document specifies requirements for algorithms that reduce this user-visible delay and provides an example algorithm, referred to as "Happy Eyeballs". This document obsoletes the original algorithm description in RFC 6555.
John KristoffWeekend Reads:
* DNSSEC measured https://www.potaroo.net/ispcol/2023-09/dnssec-queries.html
* Flow distribution with ECMP https://dipsingh.github.io/Flow-Distribution-Across-ECMP/
* DNS resolver fuzzing https://publications.cispa.saarland/4033/
* Adaptive address family selection https://arxiv.org/abs/2309.05369
* US DoD cybersecurity strategy https://media.defense.gov/2023/Sep/12/2003299076/-1/-1/1/2023_DOD_Cyber_Strategy_Summary.PDF
Alex @ Maths PlayMultiplication Fact Enlightment👀✨️🛼
We were over the moon to discover the mathematical beauty of multiplication from a Mathologer video.
Learn how to create multiplicative designs like this and so much more: https://youtu.be/qhbuKbxJsk8
#MathsPlay #HappyEyeballs #VeryMaths #Pattern #TimesTable #PlayItForward #Maths #MTBoS
