GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE

  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Conversation

Notices

  1. Embed this notice
    feld (feld@bikeshed.party)'s status on Wednesday, 03-Jan-2024 04:29:48 JST feld feld
    New year, new network
    In conversation about 11 months ago from bikeshed.party permalink
    • Embed this notice
      on-lain ✔ᵛᵉʳᶦᶠᶦᵉᵈ (lain@lain.com)'s status on Wednesday, 03-Jan-2024 04:55:14 JST on-lain ✔ᵛᵉʳᶦᶠᶦᵉᵈ on-lain ✔ᵛᵉʳᶦᶠᶦᵉᵈ
      in reply to
      @feld will we get ipv7 this year?
      In conversation about 11 months ago permalink
    • Embed this notice
      clay vaulin (clayvaulin@freespeechextremist.com)'s status on Thursday, 04-Jan-2024 06:10:31 JST clay vaulin clay vaulin
      in reply to
      • on-lain ✔ᵛᵉʳᶦᶠᶦᵉᵈ
      @lain
      straight to ipv8 and it wont be adopted for another 20 years
      @feld
      In conversation about 11 months ago permalink
    • Embed this notice
      feld (feld@bikeshed.party)'s status on Thursday, 04-Jan-2024 06:10:31 JST feld feld
      in reply to
      • on-lain ✔ᵛᵉʳᶦᶠᶦᵉᵈ
      • clay vaulin
      @clayvaulin @lain ipv7 was drafted way back in 1993 lol

      https://datatracker.ietf.org/doc/html/rfc1475
      In conversation about 11 months ago permalink

      Attachments

      1. Domain not in remote thumbnail source whitelist: www.ietf.org
        RFC 1475: TP/IX: The Next Internet
        from Robert L. Ullmann
        This memo presents the specification for version 7 of the Internet Protocol, as well as version 7 of the TCP and the user datagram protocol. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard.
    • Embed this notice
      feld (feld@bikeshed.party)'s status on Thursday, 04-Jan-2024 06:13:50 JST feld feld
      in reply to
      • on-lain ✔ᵛᵉʳᶦᶠᶦᵉᵈ
      • 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
      In conversation about 11 months ago permalink

      Attachments

      1. Domain not in remote thumbnail source whitelist: www.ietf.org
        RFC 1621: Pip Near-term Architecture
        from Paul Francis
        The purpose of this RFC and the companion RFC "Pip Header Processing" are to record the ideas (good and bad) of Pip. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
    • Embed this notice
      feld (feld@bikeshed.party)'s status on Thursday, 04-Jan-2024 06:42:14 JST feld feld
      in reply to
      • on-lain ✔ᵛᵉʳᶦᶠᶦᵉᵈ
      • 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.
      In conversation about 11 months ago permalink
    • Embed this notice
      clay vaulin (clayvaulin@freespeechextremist.com)'s status on Thursday, 04-Jan-2024 06:42:16 JST clay vaulin clay vaulin
      in reply to
      • on-lain ✔ᵛᵉʳᶦᶠᶦᵉᵈ
      @feld
      why create so many draft standards when no one was using the current new ones?
      @lain
      In conversation about 11 months ago permalink

Feeds

  • Activity Streams
  • RSS 2.0
  • Atom
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.