Skip to content
  • Hjem
  • Seneste
  • Etiketter
  • Populære
  • Verden
  • Bruger
  • Grupper
Temaer
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Kollaps
FARVEL BIG TECH
  1. Forside
  2. Ikke-kategoriseret
  3. A question for #Fediverse devs: I'm thinking about better ways to document development of the #ActivityPub stack.

A question for #Fediverse devs: I'm thinking about better ways to document development of the #ActivityPub stack.

Planlagt Fastgjort Låst Flyttet Ikke-kategoriseret
activitypubfediverse
5 Indlæg 3 Posters 0 Visninger
  • Ældste til nyeste
  • Nyeste til ældste
  • Most Votes
Svar
  • Svar som emne
Login for at svare
Denne tråd er blevet slettet. Kun brugere med emne behandlings privilegier kan se den.
  • deadsuperhero@social.wedistribute.orgD This user is from outside of this forum
    deadsuperhero@social.wedistribute.orgD This user is from outside of this forum
    deadsuperhero@social.wedistribute.org
    wrote sidst redigeret af
    #1

    A question for #Fediverse devs: I’m thinking about better ways to document development of the #ActivityPub stack. This would include explanations, demo code, example snippets, and various sections explaining how to build a fully working Fediverse server, with consideration for all of the FEP documents as well.

    What do you, as a developer, feel is currently missing? What information would make your life a lot easier?

    deadsuperhero@social.wedistribute.orgD opinionatedgeek@mastodon.socialO julian@community.nodebb.orgJ 3 Replies Last reply
    0
    • deadsuperhero@social.wedistribute.orgD deadsuperhero@social.wedistribute.org

      A question for #Fediverse devs: I’m thinking about better ways to document development of the #ActivityPub stack. This would include explanations, demo code, example snippets, and various sections explaining how to build a fully working Fediverse server, with consideration for all of the FEP documents as well.

      What do you, as a developer, feel is currently missing? What information would make your life a lot easier?

      deadsuperhero@social.wedistribute.orgD This user is from outside of this forum
      deadsuperhero@social.wedistribute.orgD This user is from outside of this forum
      deadsuperhero@social.wedistribute.org
      wrote sidst redigeret af
      #2

      Maybe @j12t@j12t.social has some thoughts, given his involvement with FediDevs?

      1 Reply Last reply
      0
      • deadsuperhero@social.wedistribute.orgD deadsuperhero@social.wedistribute.org

        A question for #Fediverse devs: I’m thinking about better ways to document development of the #ActivityPub stack. This would include explanations, demo code, example snippets, and various sections explaining how to build a fully working Fediverse server, with consideration for all of the FEP documents as well.

        What do you, as a developer, feel is currently missing? What information would make your life a lot easier?

        opinionatedgeek@mastodon.socialO This user is from outside of this forum
        opinionatedgeek@mastodon.socialO This user is from outside of this forum
        opinionatedgeek@mastodon.social
        wrote sidst redigeret af
        #3

        @deadsuperhero More JSON examples!

        I've collected some of my own, but for every server something like:
        * this is what a regular Create-Note looks like
        * this is a reply
        * this is an Announce
        * this is a Like
        * this is a Follow
        * this has two hashtags
        * this has a link (and preview?)
        * this is a quote post
        * this has quote post protection
        * this has reply controls

        ActivityPub provides a lot of leeway so concrete, real examples help.

        deadsuperhero@social.wedistribute.orgD 1 Reply Last reply
        0
        • opinionatedgeek@mastodon.socialO opinionatedgeek@mastodon.social

          @deadsuperhero More JSON examples!

          I've collected some of my own, but for every server something like:
          * this is what a regular Create-Note looks like
          * this is a reply
          * this is an Announce
          * this is a Like
          * this is a Follow
          * this has two hashtags
          * this has a link (and preview?)
          * this is a quote post
          * this has quote post protection
          * this has reply controls

          ActivityPub provides a lot of leeway so concrete, real examples help.

          deadsuperhero@social.wedistribute.orgD This user is from outside of this forum
          deadsuperhero@social.wedistribute.orgD This user is from outside of this forum
          deadsuperhero@social.wedistribute.org
          wrote sidst redigeret af
          #4

          @OpinionatedGeek@mastodon.social Hey, this is great! Thank you!

          1 Reply Last reply
          0
          • deadsuperhero@social.wedistribute.orgD deadsuperhero@social.wedistribute.org

            A question for #Fediverse devs: I’m thinking about better ways to document development of the #ActivityPub stack. This would include explanations, demo code, example snippets, and various sections explaining how to build a fully working Fediverse server, with consideration for all of the FEP documents as well.

            What do you, as a developer, feel is currently missing? What information would make your life a lot easier?

            julian@community.nodebb.orgJ This user is from outside of this forum
            julian@community.nodebb.orgJ This user is from outside of this forum
            julian@community.nodebb.org
            wrote sidst redigeret af
            #5

            deadsuperhero@social.wedistribute.org I’m of the opinion that a solid collection of links is the easiest way to get there.

            FediDevs set out to do that but I think the best approach would be to update ActivityPub.rocks with the links and docs instead.

            Join the WG for it!! Led by evan@cosocial.ca and j12t@j12t.social

            1 Reply Last reply
            0
            Svar
            • Svar som emne
            Login for at svare
            • Ældste til nyeste
            • Nyeste til ældste
            • Most Votes


            • Log ind

            • Har du ikke en konto? Tilmeld

            • Login or register to search.
            Powered by NodeBB Contributors
            Graciously hosted by data.coop
            • First post
              Last post
            0
            • Hjem
            • Seneste
            • Etiketter
            • Populære
            • Verden
            • Bruger
            • Grupper