Skip to content
  • Categories
  • Recent
  • Popular
Skins
  • 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
Collapse

NodeBB-ActivityPub Bridge Test Instance

  1. Home
  2. Categories
  3. General Discussion
  4. AP Test (community.nodebb.org)
  5. FEP-7888 and the Add activity

FEP-7888 and the Add activity

Scheduled Pinned Locked Moved AP Test (community.nodebb.org)
activitypub7888fep
16 Posts 8 Posters 232 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • jupiter_rowland@hub.netzgemeinde.euJ This user is from outside of this forum
    jupiter_rowland@hub.netzgemeinde.euJ This user is from outside of this forum
    jupiter_rowland@hub.netzgemeinde.eu
    wrote on last edited by
    #6
    @julian @Emelia 👸🏻 It's also fair to mention that this has been the standard mode of operation for everything @Mike Macgirvin 🖥️ has ever created until this year, starting in 2010 with Mistpark which is Friendica today. Friendica still behaves like this, Hubzilla still behaves like this, and (streams) behaved like this until the move to Collections in 2023. Forte is the only exception, it started with Collections right away which, on the outside, don't feel much different.

    After all, they're more or less Facebook alternatives. And not the Twitter clone as which the Fediverse in its entirety is being perceived nowadays.

    The advantage of this is that everyone who participates in a conversation generally always receives all replies. Not only those that mention them.

    From a Mastodon point of view, this concept may appear either revolutionary or entirely unimaginable. But it has been around for 14 years.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla #Streams #(streams) #Forte #Conversations
    1 Reply Last reply
    0
    • silverpill@mitra.socialS This user is from outside of this forum
      silverpill@mitra.socialS This user is from outside of this forum
      silverpill@mitra.social
      wrote on last edited by
      #7

      @mikedev @trwnh @thisismissem @julian As far as I can tell, Containers not simply co-exist with FEP-7888 but fully satisfy its requirements.

      trwnh@mastodon.socialT 1 Reply Last reply
      0
      • silverpill@mitra.socialS silverpill@mitra.social

        @mikedev @trwnh @thisismissem @julian As far as I can tell, Containers not simply co-exist with FEP-7888 but fully satisfy its requirements.

        trwnh@mastodon.socialT This user is from outside of this forum
        trwnh@mastodon.socialT This user is from outside of this forum
        trwnh@mastodon.social
        wrote on last edited by
        #8

        @silverpill @thisismissem @mikedev @julian yeah, the only point of difference i recall when reading about comversation containers was a bit about using target.attributedTo (FEP-400e) instead, which i would personally discourage in favor of context.attributedTo so that there is only one source of truth. aside from that, FEP-7888 certainly covers this implementation in at least spirit if not fully in letter -- the core of it is as simple as "please use `context` for tracking the conversation".

        trwnh@mastodon.socialT silverpill@mitra.socialS 2 Replies Last reply
        0
        • trwnh@mastodon.socialT trwnh@mastodon.social

          @silverpill @thisismissem @mikedev @julian yeah, the only point of difference i recall when reading about comversation containers was a bit about using target.attributedTo (FEP-400e) instead, which i would personally discourage in favor of context.attributedTo so that there is only one source of truth. aside from that, FEP-7888 certainly covers this implementation in at least spirit if not fully in letter -- the core of it is as simple as "please use `context` for tracking the conversation".

          trwnh@mastodon.socialT This user is from outside of this forum
          trwnh@mastodon.socialT This user is from outside of this forum
          trwnh@mastodon.social
          wrote on last edited by
          #9

          @silverpill @thisismissem @mikedev @julian the rest of the stuff only really applies if the context happens to be 1) resolvable, 2) a Collection, and 3) owned by somebody. which i would recommend doing because it just makes sense, certainly more useful than an opaque URI.

          the bits about sending to only the context owner is also only really a courtesy, for cases where you want to recognize their authority and it really matters to you whether you're in the collection or not.

          trwnh@mastodon.socialT 1 Reply Last reply
          0
          • trwnh@mastodon.socialT trwnh@mastodon.social

            @silverpill @thisismissem @mikedev @julian the rest of the stuff only really applies if the context happens to be 1) resolvable, 2) a Collection, and 3) owned by somebody. which i would recommend doing because it just makes sense, certainly more useful than an opaque URI.

            the bits about sending to only the context owner is also only really a courtesy, for cases where you want to recognize their authority and it really matters to you whether you're in the collection or not.

            trwnh@mastodon.socialT This user is from outside of this forum
            trwnh@mastodon.socialT This user is from outside of this forum
            trwnh@mastodon.social
            wrote on last edited by
            #10

            @silverpill @thisismissem @mikedev @julian i think the most robust thing to do in an open world system is to treat properties like `inReplyTo` and `context` not as facts but as claims. if you want to verify those claims, resolve the collection and check for inclusion.

            i'd like to make that flow more efficient in the future with something like https://w3id.org/fep/0391 -- use an Add activity as a stamp of inclusion.

            1 Reply Last reply
            0
            • trwnh@mastodon.socialT trwnh@mastodon.social

              @silverpill @thisismissem @mikedev @julian yeah, the only point of difference i recall when reading about comversation containers was a bit about using target.attributedTo (FEP-400e) instead, which i would personally discourage in favor of context.attributedTo so that there is only one source of truth. aside from that, FEP-7888 certainly covers this implementation in at least spirit if not fully in letter -- the core of it is as simple as "please use `context` for tracking the conversation".

              silverpill@mitra.socialS This user is from outside of this forum
              silverpill@mitra.socialS This user is from outside of this forum
              silverpill@mitra.social
              wrote on last edited by
              #11

              @trwnh @thisismissem @mikedev @julian

              >In a constrained conversation, the target->id and the context are identical.

              So target.attributedTo and context.attributedTo would be identical too

              trwnh@mastodon.socialT 1 Reply Last reply
              0
              • silverpill@mitra.socialS silverpill@mitra.social

                @trwnh @thisismissem @mikedev @julian

                >In a constrained conversation, the target->id and the context are identical.

                So target.attributedTo and context.attributedTo would be identical too

                trwnh@mastodon.socialT This user is from outside of this forum
                trwnh@mastodon.socialT This user is from outside of this forum
                trwnh@mastodon.social
                wrote on last edited by
                #12

                @silverpill @thisismissem @mikedev @julian i understand that the producer can produce documents where the two are the same, but the very nature of their being two properties means that there is the possibility that they will not match.

                mikedev@fediversity.siteM 1 Reply Last reply
                0
                • trwnh@mastodon.socialT trwnh@mastodon.social

                  @silverpill @thisismissem @mikedev @julian i understand that the producer can produce documents where the two are the same, but the very nature of their being two properties means that there is the possibility that they will not match.

                  mikedev@fediversity.siteM This user is from outside of this forum
                  mikedev@fediversity.siteM This user is from outside of this forum
                  mikedev@fediversity.site
                  wrote on last edited by
                  #13
                  I would be happy to consolidate, but I think the chances of some large percentage of the fediverse choking badly on an array for the context element are pretty high. Same reason I don't use an array in an actor 'url' field. It's  a few years since I tried this, but 2/3 of the fediverse projects at the time couldn't deal with it and nobody bothered to fix it for years because "Mastodon doesn't do this, so you must be doing something wrong."

                  Anyway, I'm retired from the fediverse shit-show now. Y'all can do what you want. But please implement comment control. It isn't a "feature" - it's basic online security (except for some freespeech folks who still think everybody with an opinion or a dick has some God-given right to shove it in your face).

                  The fediverse you save might be your own.
                  1 Reply Last reply
                  0
                  • bs2@nomad.pepecyb.deB This user is from outside of this forum
                    bs2@nomad.pepecyb.deB This user is from outside of this forum
                    bs2@nomad.pepecyb.de
                    wrote on last edited by
                    #14
                    bsmall2 likes julian's status
                    1 Reply Last reply
                    0
                    • trwnh@mastodon.socialT This user is from outside of this forum
                      trwnh@mastodon.socialT This user is from outside of this forum
                      trwnh@mastodon.social
                      wrote on last edited by
                      #15

                      @mikedev Yeah, the way current fedi handles "conversations" is very poor: they basically don't.

                      it actually seems quite technically simple to handle them, but it does come at the cost of "efficiency" and "scale": realize we are building web browsers, and browse those collections directly. maybe cache those collections, maybe use Add/Remove as a rudimentary state sync or mechanism (or at least cache invalidation). but the basic idea is not to blindly make up whatever you *think* is in them.

                      1 Reply Last reply
                      1
                      0
                      • shlee@aus.socialS This user is from outside of this forum
                        shlee@aus.socialS This user is from outside of this forum
                        shlee@aus.social
                        wrote on last edited by
                        #16

                        @julian @thisismissem @trwnh makes sense as well for “followers only”… if you post a post with abuse and include someone..

                        It *could* reach the somebody and all of their followers as well boosted via their server (with controls. Opens the abuse vector slightly.

                        1 Reply Last reply
                        0
                        Reply
                        • Reply as topic
                        Log in to reply
                        • Oldest to Newest
                        • Newest to Oldest
                        • Most Votes


                        • Login

                        • Login or register to search.
                        Powered by NodeBB Contributors
                        • First post
                          Last post
                        0
                        • Categories
                        • Recent
                        • Popular