Skip to content
  • Hjem
  • Seneste
  • Etiketter
  • Populære
  • Verden
  • Bruger
  • Grupper
Temaer
  • Light
  • Brite
  • 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. I love #activitypub but seeing how slow its development is compared to #atproto makes it hard to be excited about it.

I love #activitypub but seeing how slow its development is compared to #atproto makes it hard to be excited about it.

Planlagt Fastgjort Låst Flyttet Ikke-kategoriseret
activitypubatproto
8 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.
  • res260@infosec.exchangeR This user is from outside of this forum
    res260@infosec.exchangeR This user is from outside of this forum
    res260@infosec.exchange
    wrote sidst redigeret af
    #1

    I love #activitypub but seeing how slow its development is compared to #atproto makes it hard to be excited about it. This goes for both protocol development and ecosystem development.

    ATproto has many cool projects popping up every month, the vision is clear and platforms integrate with each other.

    I don't see this excitement and work on the ActivityPub side 😞

    res260@infosec.exchangeR evan@cosocial.caE 2 Replies Last reply
    0
    • res260@infosec.exchangeR res260@infosec.exchange

      I love #activitypub but seeing how slow its development is compared to #atproto makes it hard to be excited about it. This goes for both protocol development and ecosystem development.

      ATproto has many cool projects popping up every month, the vision is clear and platforms integrate with each other.

      I don't see this excitement and work on the ActivityPub side 😞

      res260@infosec.exchangeR This user is from outside of this forum
      res260@infosec.exchangeR This user is from outside of this forum
      res260@infosec.exchange
      wrote sidst redigeret af
      #2

      Is it because of money? Perhaps. #bluesky having money helps a ton for sure, but there is a big amount of work done from other unpaid folks as well. Idk the attitude just seems way different.

      1 Reply Last reply
      0
      • res260@infosec.exchangeR res260@infosec.exchange

        I love #activitypub but seeing how slow its development is compared to #atproto makes it hard to be excited about it. This goes for both protocol development and ecosystem development.

        ATproto has many cool projects popping up every month, the vision is clear and platforms integrate with each other.

        I don't see this excitement and work on the ActivityPub side 😞

        evan@cosocial.caE This user is from outside of this forum
        evan@cosocial.caE This user is from outside of this forum
        evan@cosocial.ca
        wrote sidst redigeret af
        #3

        @res260 I think part of that is the API.

        In our ecosystem, we've normalized that you have to build the whole server side, with data storage and network interoperability and so on, for every single new kind of app.

        It'd be great if you could use a standard API to make cool apps, and leave all the plumbing to a general-purpose server.

        That's what we're doing in the ActivityPub API task force at w3c.

        https://github.com/swicg/activitypub-api/

        res260@infosec.exchangeR julian@activitypub.spaceJ 2 Replies Last reply
        0
        • evan@cosocial.caE evan@cosocial.ca

          @res260 I think part of that is the API.

          In our ecosystem, we've normalized that you have to build the whole server side, with data storage and network interoperability and so on, for every single new kind of app.

          It'd be great if you could use a standard API to make cool apps, and leave all the plumbing to a general-purpose server.

          That's what we're doing in the ActivityPub API task force at w3c.

          https://github.com/swicg/activitypub-api/

          res260@infosec.exchangeR This user is from outside of this forum
          res260@infosec.exchangeR This user is from outside of this forum
          res260@infosec.exchange
          wrote sidst redigeret af
          #4

          @evan That would make sense. For ATProto, not being required to think about the PDS and the relays implementations must help a ton to get projects off the ground quickly. Hope the Social API changes that 🙏

          evan@cosocial.caE 1 Reply Last reply
          0
          • res260@infosec.exchangeR res260@infosec.exchange

            @evan That would make sense. For ATProto, not being required to think about the PDS and the relays implementations must help a ton to get projects off the ground quickly. Hope the Social API changes that 🙏

            evan@cosocial.caE This user is from outside of this forum
            evan@cosocial.caE This user is from outside of this forum
            evan@cosocial.ca
            wrote sidst redigeret af
            #5

            @res260 you and me both!

            1 Reply Last reply
            0
            • evan@cosocial.caE evan@cosocial.ca

              @res260 I think part of that is the API.

              In our ecosystem, we've normalized that you have to build the whole server side, with data storage and network interoperability and so on, for every single new kind of app.

              It'd be great if you could use a standard API to make cool apps, and leave all the plumbing to a general-purpose server.

              That's what we're doing in the ActivityPub API task force at w3c.

              https://github.com/swicg/activitypub-api/

              julian@activitypub.spaceJ This user is from outside of this forum
              julian@activitypub.spaceJ This user is from outside of this forum
              julian@activitypub.space
              wrote sidst redigeret af
              #6

              @evan@cosocial.ca 100% agreed on the heavy(-ier) lift that is AP development.

              However that’s how standalone apps have always been developed, and there is a reason why.

              When you rely on someone else’s tech, then when they sunset the tech or it otherwise becomes unfavourable, you’re fucked (pardon my french)

              I’ve seen entire businesses jump head first into building “Facebook apps” after Farmville exploded. None of them are around now and Zynga is currently worth $8 on the NASDAQ.

              cc @res260@infosec.exchange

              res260@infosec.exchangeR 1 Reply Last reply
              1
              0
              • julian@activitypub.spaceJ julian@activitypub.space

                @evan@cosocial.ca 100% agreed on the heavy(-ier) lift that is AP development.

                However that’s how standalone apps have always been developed, and there is a reason why.

                When you rely on someone else’s tech, then when they sunset the tech or it otherwise becomes unfavourable, you’re fucked (pardon my french)

                I’ve seen entire businesses jump head first into building “Facebook apps” after Farmville exploded. None of them are around now and Zynga is currently worth $8 on the NASDAQ.

                cc @res260@infosec.exchange

                res260@infosec.exchangeR This user is from outside of this forum
                res260@infosec.exchangeR This user is from outside of this forum
                res260@infosec.exchange
                wrote sidst redigeret af
                #7

                @julian @evan I think it's a great perk of ATProto. Once you shipped your app and have seen some success, then you can start thinking about making it resilient by removing dependencies. Right now, it looks to me like this model is superior to foster an ecosystem.

                julian@activitypub.spaceJ 1 Reply Last reply
                0
                • res260@infosec.exchangeR res260@infosec.exchange

                  @julian @evan I think it's a great perk of ATProto. Once you shipped your app and have seen some success, then you can start thinking about making it resilient by removing dependencies. Right now, it looks to me like this model is superior to foster an ecosystem.

                  julian@activitypub.spaceJ This user is from outside of this forum
                  julian@activitypub.spaceJ This user is from outside of this forum
                  julian@activitypub.space
                  wrote sidst redigeret af
                  #8

                  @res260@infosec.exchange on that we agree. There is lot of momentum in the ATProto space and I can sense that all the way over here (I am not plugged in to that side, at all.)

                  The apps that are coming out are really interesting and the ease of development does foster that kind of environment.

                  1 Reply Last reply
                  0
                  • nodebb@fosstodon.orgN nodebb@fosstodon.org shared this topic
                  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