The v 8 bullshit is still circulating as serious alternative 🤦

[jima@mspsocial.net]

@tschaefer @ghostinthenet It's on its third iteration...

[litchralee_v6@ipv6.social]

@jima @tschaefer @ghostinthenet Do IETF proposals get their TTL extended when there's a revision?

I would support additional meowing in the only proposal that's worth talking about, just to make sure it sticks around.

[jima@mspsocial.net]

@litchralee_v6 @tschaefer @ghostinthenet You tell me.

https://author-tools.ietf.org/iddiff?url1=draft-thain-ipv8-00&url2=draft-thain-ipv8-02&difftype=--hwdiff

[litchralee_v6@ipv6.social]

@jima @tschaefer @ghostinthenet The thing is, I'd prefer to never have to see that dismal document ever again. Its very existence exudes categorical error.

[jima@mspsocial.net]

@litchralee_v6 @tschaefer @ghostinthenet Can I make matters worse by providing his rationale? 🤭

archive.is

(archive.is)

[litchralee_v6@ipv6.social]

@jima @tschaefer @ghostinthenet For different reasons, I no longer use archive\.is links or visit them

[jima@mspsocial.net]

@litchralee_v6 @tschaefer @ghostinthenet It wasn't my first choice, but the Wayback Machine can't scrape LinkedIn posts, apparently.

Got a better alternative? I'm game.

[litchralee_v6@ipv6.social]

@jima @tschaefer @ghostinthenet In some ways, I think it's perfect that LinkedIn content stays wholly contained within that platform lol

[kasperd@westergaard.social]

It's also missing IPv6 support, which is my primary reason for using archive.is.

[kasperd@westergaard.social]

That's utter BS. Here are some of the lies I spotted in that document:

• IPv8 the new IP protocol that reduces risk, and complexity
• IPv6 requires you to run two networks forever