fsebugoutzone.org:9999

       Posts by noipv6@hachyderm.io
 (DIR) Post #AW3kR5VIfr5PizeAOu by noipv6@hachyderm.io
       2023-05-26T21:34:19Z
       
       0 likes, 0 repeats
       
       @stanford quite remarkable happenstance! 😇
       
 (DIR) Post #AWePOhoiiud3LfL6xM by noipv6@hachyderm.io
       2023-06-13T14:03:00Z
       
       0 likes, 0 repeats
       
       @lamp weird, no disruption in my region 🤔(given that i’ve made the perhaps bold choice to go v6-only for oci, i’d likely notice 😅)
       
 (DIR) Post #AWePTqLKS3f9Et2dvs by noipv6@hachyderm.io
       2023-06-13T14:03:54Z
       
       0 likes, 0 repeats
       
       @tschaefer “completes” 😒
       
 (DIR) Post #AY8vXaJHVnPSbhHTQu by noipv6@hachyderm.io
       2023-07-28T05:16:34Z
       
       0 likes, 0 repeats
       
       @lamp
       
 (DIR) Post #AYGGWDvyg3w241ICHo by noipv6@hachyderm.io
       2023-07-31T18:14:34Z
       
       0 likes, 0 repeats
       
       @tschaefer as i noted, uh, elsewhere: about 34-44% of internet users have #ipv6, so for 20% of malicious ip’s to be ipv6…that actually shows that cybercriminals are using it less than the general population are. 🤔original text from https://www.cybersecuritydive.com/press-release/20230727-crowdsecs-new-cybersecurity-majority-report-highlights-the-rise-of-ipv6-in-2/
       
 (DIR) Post #AYGj81bHmPCLX3QYWu by noipv6@hachyderm.io
       2023-07-31T18:04:02Z
       
       0 likes, 0 repeats
       
       when someone tries to do a bigotry on the hellsite but accidentally produces some surprisingly effective pro-#ipv6 propaganda 🏳️‍🌈🫡#lgbtq #gay #pride #gaypride 😘
       
 (DIR) Post #AYI2CbkPQ6Hf5OYNKy by noipv6@hachyderm.io
       2023-08-01T14:43:34Z
       
       0 likes, 0 repeats
       
       @tschaefer okay okay okay 🤣
       
 (DIR) Post #AYnxQFlN9WCAAZtMC8 by noipv6@hachyderm.io
       2023-08-17T00:20:45Z
       
       0 likes, 0 repeats
       
       @tschaefer this image sums up my reactionhttps://social.treehouse.systems/@hugo/110826909667207051
       
 (DIR) Post #AZBtr2cyMT71E6WFl2 by noipv6@hachyderm.io
       2023-08-28T13:33:04Z
       
       0 likes, 0 repeats
       
       @tschaefer there’s nat64, so i’m not sure your point? 🤔
       
 (DIR) Post #AZCT05vgx1jgT9KM9g by noipv6@hachyderm.io
       2023-08-28T20:07:39Z
       
       0 likes, 0 repeats
       
       @tschaefer the fixed wireless side of that “100 million user” example uses 464xlat, so clatd, so… 🤷🏻
       
 (DIR) Post #AZCUbCLKAWtf1qZa6q by noipv6@hachyderm.io
       2023-08-28T20:25:37Z
       
       0 likes, 0 repeats
       
       @tschaefer where exactly was “server side” stipulated? 🤨
       
 (DIR) Post #AZDvPLvnaNgnDCAa1Y by noipv6@hachyderm.io
       2023-08-29T13:00:43Z
       
       0 likes, 0 repeats
       
       @tschaefer a) i still don’t see how that blurb inherently says anything about server-side; i read it as “client-side SUPPORT exists, clearly, but who’s actually IMPLEMENTED it?”&amp; b) maybe a “duh” take on my part, but i hadn’t seen “ipv6-mostly” as intrinsically linked w/ dhcpv4 option 104, interpreting it more as a generic acquiescence of the whiners’ age-old outcry of “it’s OBVIOUSLY not an ‘#ipv6-only network’ if you still provide connectivity to [legacy ip] networks 🥴”
       
 (DIR) Post #Aa1uF9crMNTgh8sPPU by noipv6@hachyderm.io
       2023-09-22T14:45:54Z
       
       0 likes, 0 repeats
       
       new cve for people who disable #ipv6 dns resolution via glibc 🤦🏻https://nvd.nist.gov/vuln/detail/CVE-2023-4527
       
 (DIR) Post #Aa1uRg6SR4Esteh0HQ by noipv6@hachyderm.io
       2023-09-22T15:45:27Z
       
       0 likes, 0 repeats
       
       @tschaefer https://mail.gnu.org/archive/html/info-gnu/2022-08/msg00000.html
       
 (DIR) Post #Aa1z5tuGvwX76iQbGS by noipv6@hachyderm.io
       2023-09-22T16:37:35Z
       
       0 likes, 0 repeats
       
       @tschaefer no problem!the whole of how much nonsense like that exists is probably unknowable 😳
       
 (DIR) Post #AdLx9y8x8LW32fN0Vc by noipv6@hachyderm.io
       2023-12-31T00:56:07Z
       
       0 likes, 0 repeats
       
       @lucasmz @vees you’re enough of one 😃as noted elsewhere, the latter is technically “illegal” 👀
       
 (DIR) Post #AihxlGeuZi7pvqF7jM by noipv6@hachyderm.io
       2024-05-29T16:14:38Z
       
       0 likes, 0 repeats
       
       @cy @bluknight “finished in 1998” tells me you don’t know shit about actual deployment*, &amp; should probably sit this discussion out &amp; let the grown-ups do their work* or standards development, for that matter, given how many highly relevant rfc’s came out in the 2000’s &amp; 2010’s
       
 (DIR) Post #AiieKmVkKylCviZZlA by noipv6@hachyderm.io
       2024-06-08T05:38:31Z
       
       0 likes, 0 repeats
       
       @kramse @cy @bluknight what does “fully functional” mean to you? 🤔because “barely available from any isp’s” doesn’t feel very functional 😑
       
 (DIR) Post #AiieKoD21WykCFpero by noipv6@hachyderm.io
       2024-06-08T06:55:27Z
       
       0 likes, 0 repeats
       
       @kramse @cy @bluknight what running code was there for ipv6 in windows in 1998?what was there in mac os?bsd, linux, greatwhat was their market share in 1998?what network operating systems supported it in 1998?that’s…not “fully functional”. 😑2011? not gunna dispute that year - it was pretty functional then.
       
 (DIR) Post #AiuN42ig0RvqWHij4a by noipv6@hachyderm.io
       2024-06-13T20:53:55Z
       
       0 likes, 0 repeats
       
       @kramse @cy @bluknight good thing i forgot about this until thursday 😃“ipv6 was running in the late 1990s” is a minimally technically accurate but completely fucking worthless statementeven by the time ppl started publishing stats in 2008-2011, ipv6 adoption was &lt; 0.3% of the internetif you think the average organisation could fully adopt ipv6 in 1998, i would hazard a guess that what you don’t understand about networking exceeds what you do 🥴