Litchralee_v6
litchralee_v6@ipv6.social
<p>Hello (IPv6) world!</p><p>This is my sub-account for <a href="https://ipv6.social/tags/IPv6" class="mention hashtag" rel="tag">#<span>IPv6</span></a> and related things. My main account is <span class="h-card" translate="no"><a href="https://defcon.social/@litchralee" class="u-url mention">@<span>litchralee</span></a></span></p>
Posts
-
Post #1966199
@nuintari I couldn&#39;t make it through more than two minutes of reading the sheer contradictions. I wish to give it no further consideration, except as an excellent example of how an onslaught of truly insane, possibly LLM generated slop is sufficient to tire out the BS-meters from anyone that still has a working one. I wonder if anyone has ever done fondue cheese with popcorn.
-
Post #1966198
@nuintari Honestly, it&#39;s somewhat surprising they didn&#39;t reintroduce classful networking. Considering the trainwreck before us, they might as well have defined Class D, Class E, and Class F networks to be /96, /84, and /72, for no obvious reason whatsoever and in stark contravention to anything learned in the last 30 years. Probably the worst part is that people who don&#39;t know better will think that 8 &gt; 6 and therefore ask their network admins to implement this. G...
-
Post #1454634
Some while ago -- I think it was an @azonenberg post -- I learned of a company that sells a fast-drying, mil-spec hand lotion for use in cleanrooms, that comes in an ESD-safe bottle and sold in gallon (3.78 L) amounts. Would this be overkill for my work-from-home desk job? Yes. Did I find a good deal online? Yes. And I can say that so far, I like it. https://rrlotion.com/product/ic-lotion-fragrance-free/
-
Post #1454632
@jana @Bluewall @loos The proposal is entirely unserious. In only two minutes, I came across grossly incompatible statements like: &gt; The suite is 100% backward compatible. And: &gt; Organisations assign internal zone prefixes (127.1.0.0, 127.2.0.0 etc) to network zones and regions. More than once in my career, I have had to point to the 1993 RFC that reserves the entire 127.0.0.0/8 subnet for solely loopback. And this nonsense is still happening in 2026??