Salta al contenuto
0
  • Home
  • Piero Bosio
  • Blog
  • Mondo
  • Fediverso
  • News
  • Categorie
  • Old Web Site
  • Recenti
  • Popolare
  • Tag
  • Utenti
  • Home
  • Piero Bosio
  • Blog
  • Mondo
  • Fediverso
  • News
  • Categorie
  • Old Web Site
  • Recenti
  • Popolare
  • Tag
  • Utenti
Skin
  • Chiaro
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Scuro
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Predefinito (Cerulean)
  • Nessuna skin
Collassa

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone
  1. Home
  2. Categorie
  3. General Discussion
  4. Would you like to see full default interoperability between #ATproto and #ActivityPub without a bridge?

Would you like to see full default interoperability between #ATproto and #ActivityPub without a bridge?

Pianificato Fissato Bloccato Spostato General Discussion
atprotoactivitypub
47 Post 8 Autori 4.8k Visualizzazioni
  • Da Vecchi a Nuovi
  • Da Nuovi a Vecchi
  • Più Voti
Rispondi
  • Risposta alla discussione
Effettua l'accesso per rispondere
Questa discussione è stata eliminata. Solo gli utenti con diritti di gestione possono vederla.
  • evan@cosocial.caundefined evan@cosocial.ca

    @julian @wjmaggos I don't have the secret sauce for how to get there, though. Trying my best.

    trwnh@mastodon.socialundefined Questo utente è esterno a questo forum
    trwnh@mastodon.socialundefined Questo utente è esterno a questo forum
    trwnh@mastodon.social
    scritto su ultima modifica di
    #38

    @evan @julian @wjmaggos what would you consider to be the "application domain" of HTTP, and what needs to be built above it? ironically, i think if you look at the OSI model, then HTTP is already at the uppermost "layer 7", the application layer -- and attempts to build networks on top of HTTP are in effect virtualizing lower layers! so instead of a virtual 3-7 on top of HTTP's 7, why not use HTTP's 7 directly? how many nested virtualized app layers do we need?

    evan@cosocial.caundefined 1 Risposta Ultima Risposta
    0
    • trwnh@mastodon.socialundefined trwnh@mastodon.social

      @evan @julian @wjmaggos what would you consider to be the "application domain" of HTTP, and what needs to be built above it? ironically, i think if you look at the OSI model, then HTTP is already at the uppermost "layer 7", the application layer -- and attempts to build networks on top of HTTP are in effect virtualizing lower layers! so instead of a virtual 3-7 on top of HTTP's 7, why not use HTTP's 7 directly? how many nested virtualized app layers do we need?

      evan@cosocial.caundefined Questo utente è esterno a questo forum
      evan@cosocial.caundefined Questo utente è esterno a questo forum
      evan@cosocial.ca
      scritto su ultima modifica di
      #39

      @trwnh @julian @wjmaggos hypertext

      evan@cosocial.caundefined 1 Risposta Ultima Risposta
      0
      • evan@cosocial.caundefined evan@cosocial.ca

        @trwnh @julian @wjmaggos hypertext

        evan@cosocial.caundefined Questo utente è esterno a questo forum
        evan@cosocial.caundefined Questo utente è esterno a questo forum
        evan@cosocial.ca
        scritto su ultima modifica di
        #40

        @trwnh @julian @wjmaggos "The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems."

        https://datatracker.ietf.org/doc/html/rfc2616

        evan@cosocial.caundefined 1 Risposta Ultima Risposta
        0
        • evan@cosocial.caundefined evan@cosocial.ca

          @trwnh @julian @wjmaggos "The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems."

          https://datatracker.ietf.org/doc/html/rfc2616

          evan@cosocial.caundefined Questo utente è esterno a questo forum
          evan@cosocial.caundefined Questo utente è esterno a questo forum
          evan@cosocial.ca
          scritto su ultima modifica di
          #41

          @trwnh @julian @wjmaggos I am taking Computer Networks right now, and I asked the very same question. If we have application-layer protocols, what do we call the things like SOAP or ActivityPub that work on top of those protocols. The answer I got was that those are also layer 7. Once you get to layer 7, it's just 7 all the way up. Inverted turtle structure!

          1 Risposta Ultima Risposta
          0
          • evan@cosocial.caundefined evan@cosocial.ca

            @wjmaggos @chris @blaine one of my big problems with it too. I think @anewsocial are aware of that limitation and are working on some solutions.

            quillmatiq@mastodon.socialundefined Questo utente è esterno a questo forum
            quillmatiq@mastodon.socialundefined Questo utente è esterno a questo forum
            quillmatiq@mastodon.social
            scritto su ultima modifica di
            #42

            @evan @wjmaggos @chris @blaine @anewsocial

            Appreciate all the kind words in the thread! That said, I still strongly believe opt-in is a feature, not a bug. The right solution isn't to force people onto networks they don't want to be a part of; it's to clean up the rough edges of unbridged interactions and content so it makes less of a difference.

            quillmatiq@mastodon.socialundefined 1 Risposta Ultima Risposta
            0
            • quillmatiq@mastodon.socialundefined quillmatiq@mastodon.social

              @evan @wjmaggos @chris @blaine @anewsocial

              Appreciate all the kind words in the thread! That said, I still strongly believe opt-in is a feature, not a bug. The right solution isn't to force people onto networks they don't want to be a part of; it's to clean up the rough edges of unbridged interactions and content so it makes less of a difference.

              quillmatiq@mastodon.socialundefined Questo utente è esterno a questo forum
              quillmatiq@mastodon.socialundefined Questo utente è esterno a questo forum
              quillmatiq@mastodon.social
              scritto su ultima modifica di
              #43

              @evan @wjmaggos @chris @blaine @anewsocial

              I understand the instinct of "make these work together", but there are technical and cultural differences that make it more than just two standards talking to each other. A couple of simple examples are "I don't want to be in a public, auditable firehose" or "I had a bad experience there, I don't trust them with my safety."

              wjmaggos@liberal.cityundefined 1 Risposta Ultima Risposta
              0
              • quillmatiq@mastodon.socialundefined quillmatiq@mastodon.social

                @evan @wjmaggos @chris @blaine @anewsocial

                I understand the instinct of "make these work together", but there are technical and cultural differences that make it more than just two standards talking to each other. A couple of simple examples are "I don't want to be in a public, auditable firehose" or "I had a bad experience there, I don't trust them with my safety."

                wjmaggos@liberal.cityundefined Questo utente è esterno a questo forum
                wjmaggos@liberal.cityundefined Questo utente è esterno a questo forum
                wjmaggos@liberal.city
                scritto su ultima modifica di
                #44

                @quillmatiq @evan @chris @blaine @anewsocial

                I understand if you don't want to have the conversation but these are public systems like blogging with your email address available, we just don't think of them like that. it's old school twitter, not even your network of friends and family on facebook. not having algos/ads doesn't mean everything isn't boostable to the world by default. maybe people want to use something designed to be inherently private, but that's not fedi etc. IMHO

                quillmatiq@mastodon.socialundefined 1 Risposta Ultima Risposta
                0
                • wjmaggos@liberal.cityundefined wjmaggos@liberal.city

                  @quillmatiq @evan @chris @blaine @anewsocial

                  I understand if you don't want to have the conversation but these are public systems like blogging with your email address available, we just don't think of them like that. it's old school twitter, not even your network of friends and family on facebook. not having algos/ads doesn't mean everything isn't boostable to the world by default. maybe people want to use something designed to be inherently private, but that's not fedi etc. IMHO

                  quillmatiq@mastodon.socialundefined Questo utente è esterno a questo forum
                  quillmatiq@mastodon.socialundefined Questo utente è esterno a questo forum
                  quillmatiq@mastodon.social
                  scritto su ultima modifica di
                  #45

                  @wjmaggos @evan @chris @blaine @anewsocial

                  I agree with you there! But often it's not about *how* public things are, it's more about *where* they're public. In other words, many users I've spoken to who are either not bridged or are straight-up anti-bridge have chosen that route because they don't (yet) trust the entities on the other side to have that much ownership over their data. There's also a cohort who don't want to have to depend on *us* to bridge them either.

                  It's a lot more complex!

                  wjmaggos@liberal.cityundefined 1 Risposta Ultima Risposta
                  0
                  • quillmatiq@mastodon.socialundefined quillmatiq@mastodon.social

                    @wjmaggos @evan @chris @blaine @anewsocial

                    I agree with you there! But often it's not about *how* public things are, it's more about *where* they're public. In other words, many users I've spoken to who are either not bridged or are straight-up anti-bridge have chosen that route because they don't (yet) trust the entities on the other side to have that much ownership over their data. There's also a cohort who don't want to have to depend on *us* to bridge them either.

                    It's a lot more complex!

                    wjmaggos@liberal.cityundefined Questo utente è esterno a questo forum
                    wjmaggos@liberal.cityundefined Questo utente è esterno a questo forum
                    wjmaggos@liberal.city
                    scritto su ultima modifica di
                    #46

                    @quillmatiq @evan @chris @blaine @anewsocial

                    they're public on the internet! screenshots?

                    I think the complexity is mostly about having so few people here and thinking it will stay that way. that being here is safety through obscurity. that a fedi server is a community instead of much more a portal to a possibly universal social media network. they built and maintained this place (huge kudos!) to get away, but actually made the best network not to.

                    they need a fork that's default opt in.

                    quillmatiq@mastodon.socialundefined 1 Risposta Ultima Risposta
                    0
                    • wjmaggos@liberal.cityundefined wjmaggos@liberal.city

                      @quillmatiq @evan @chris @blaine @anewsocial

                      they're public on the internet! screenshots?

                      I think the complexity is mostly about having so few people here and thinking it will stay that way. that being here is safety through obscurity. that a fedi server is a community instead of much more a portal to a possibly universal social media network. they built and maintained this place (huge kudos!) to get away, but actually made the best network not to.

                      they need a fork that's default opt in.

                      quillmatiq@mastodon.socialundefined Questo utente è esterno a questo forum
                      quillmatiq@mastodon.socialundefined Questo utente è esterno a questo forum
                      quillmatiq@mastodon.social
                      scritto su ultima modifica di
                      #47

                      @wjmaggos @evan @chris @blaine @anewsocial

                      Huge difference between screenshotting vs always being a part of another network and another organization's infrastructure by default.

                      To be clear, I don't agree with Fediverse platforms depending on a blocklists, I much prefer approve-lists, but I don't think that's a popular opinion either.

                      1 Risposta Ultima Risposta
                      0
                      • Sistema ha condiviso questa discussione su

                      Ciao! Sembra che tu sia interessato a questa conversazione, ma non hai ancora un account.

                      Stanco di dover scorrere gli stessi post a ogni visita? Quando registri un account, tornerai sempre esattamente dove eri rimasto e potrai scegliere di essere avvisato delle nuove risposte (tramite email o notifica push). Potrai anche salvare segnalibri e votare i post per mostrare il tuo apprezzamento agli altri membri della comunità.

                      Con il tuo contributo, questo post potrebbe essere ancora migliore 💗

                      Registrati Accedi
                      Rispondi
                      • Risposta alla discussione
                      Effettua l'accesso per rispondere
                      • Da Vecchi a Nuovi
                      • Da Nuovi a Vecchi
                      • Più Voti


                      • 1
                      • 2
                      • 3
                      Feed RSS
                      Would you like to see full default interoperability between #ATproto and #ActivityPub without a bridge?
                      @pierobosio@soc.bosio.info
                      V4.10.1 Contributors
                      • Accedi

                      • Accedi o registrati per effettuare la ricerca.
                      • Primo post
                        Ultimo post