Conversation

Notices

1. Embed this notice
   feld (feld@bikeshed.party)'s status on Wednesday, 03-Jan-2024 04:29:48 JST feld
   New year, new network
   • Embed this notice
     lainy (lain@lain.com)'s status on Wednesday, 03-Jan-2024 04:55:14 JST lainy

     in reply to
     @feld will we get ipv7 this year?
   • Embed this notice
     clay vaulin (clayvaulin@freespeechextremist.com)'s status on Thursday, 04-Jan-2024 06:10:31 JST clay vaulin

     in reply to

     • lainy
     @lain
     straight to ipv8 and it wont be adopted for another 20 years
     @feld
   • Embed this notice
     feld (feld@bikeshed.party)'s status on Thursday, 04-Jan-2024 06:10:31 JST feld

     in reply to

     • lainy
     • clay vaulin
     @clayvaulin @lain ipv7 was drafted way back in 1993 lol
     
     https://datatracker.ietf.org/doc/html/rfc1475
   • Embed this notice
     feld (feld@bikeshed.party)'s status on Thursday, 04-Jan-2024 06:13:50 JST feld

     in reply to

     • lainy
     • clay vaulin
     @clayvaulin @lain also IPv8 was 1994 but for some reason they called it PIP in the draft and not IPv8 but everyone knows it was IPv8 and I don't know how they know that but I guess they were privy to some conversations I've never seen
     
     https://datatracker.ietf.org/doc/html/rfc1621
   • Embed this notice
     feld (feld@bikeshed.party)'s status on Thursday, 04-Jan-2024 06:42:14 JST feld

     in reply to

     • lainy
     • clay vaulin
     @clayvaulin @lain the whole point is discussion and experimentation, really. anyone can publish an RFC. Many of these were probably *really* good ideas, but getting hardware manufacturers and operating systems to implement them is tough.
   • Embed this notice
     clay vaulin (clayvaulin@freespeechextremist.com)'s status on Thursday, 04-Jan-2024 06:42:16 JST clay vaulin

     in reply to

     • lainy
     @feld
     why create so many draft standards when no one was using the current new ones?
     @lain