Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
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

Darkscribes Community

  1. Home
  2. Uncategorized
  3. @frequency now fully supports FEP-7888 as of yesterday!

@frequency now fully supports FEP-7888 as of yesterday!

Scheduled Pinned Locked Moved Uncategorized
6 Posts 2 Posters 0 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.
  • jesseplusplus@mastodon.socialJ This user is from outside of this forum
    jesseplusplus@mastodon.socialJ This user is from outside of this forum
    [email protected]
    wrote last edited by
    #1

    @frequency now fully supports FEP-7888 as of yesterday! (It has been generating outbound context since the beginning of the year, but I just finished fetching all remote replies from the context as well.)

    https://github.com/jesseplusplus/decodon/pull/188

    I'll hold off on trying to upstream this to Mastodon until after the 4.4.0 release to make sure I'm not conflicting with anything they changed.

    julian@community.nodebb.orgJ 1 Reply Last reply
    1
    0
    • jesseplusplus@mastodon.socialJ [email protected]

      @frequency now fully supports FEP-7888 as of yesterday! (It has been generating outbound context since the beginning of the year, but I just finished fetching all remote replies from the context as well.)

      https://github.com/jesseplusplus/decodon/pull/188

      I'll hold off on trying to upstream this to Mastodon until after the 4.4.0 release to make sure I'm not conflicting with anything they changed.

      julian@community.nodebb.orgJ This user is from outside of this forum
      julian@community.nodebb.orgJ This user is from outside of this forum
      [email protected]
      wrote last edited by
      #2

      [email protected] this is awesome!!

      I have to give this a spin against NodeBB tomorrow!!

      1 Reply Last reply
      0
      • julian@community.nodebb.orgJ [email protected] shared this topic
      • jesseplusplus@mastodon.socialJ This user is from outside of this forum
        jesseplusplus@mastodon.socialJ This user is from outside of this forum
        [email protected]
        wrote last edited by
        #3

        @julian woohoo! Yes, please. Let me know if you see any issues with it. I was using one of your NodeBB threads as my test case for fetching context 🤓

        julian@community.nodebb.orgJ 1 Reply Last reply
        0
        • jesseplusplus@mastodon.socialJ [email protected]

          @julian woohoo! Yes, please. Let me know if you see any issues with it. I was using one of your NodeBB threads as my test case for fetching context 🤓

          julian@community.nodebb.orgJ This user is from outside of this forum
          julian@community.nodebb.orgJ This user is from outside of this forum
          [email protected]
          wrote last edited by
          #4

          [email protected] one technical issue I came across was that a context could potentially provide object ids that temporarily or permanently do not resolve.

          That caused issues because internal NodeBB logic required that every inReplyTo referenced a valid id... So everything following that branch didn't end up making it in.

          Not sure if you experienced anything similar.

          1 Reply Last reply
          0
          • jesseplusplus@mastodon.socialJ This user is from outside of this forum
            jesseplusplus@mastodon.socialJ This user is from outside of this forum
            [email protected]
            wrote last edited by
            #5

            @julian I haven’t seen that issue so far, but I’ll look into it. I tried to reuse the existing mastodon code for reply fetching as much as possible.. not sure how much more they handle that besides trying the fetch again later in case it’s temporarily not resolving. I don’t think they have as strict of a requirement for valid inReplyTo ids though.

            julian@community.nodebb.orgJ 1 Reply Last reply
            0
            • jesseplusplus@mastodon.socialJ [email protected]

              @julian I haven’t seen that issue so far, but I’ll look into it. I tried to reuse the existing mastodon code for reply fetching as much as possible.. not sure how much more they handle that besides trying the fetch again later in case it’s temporarily not resolving. I don’t think they have as strict of a requirement for valid inReplyTo ids though.

              julian@community.nodebb.orgJ This user is from outside of this forum
              julian@community.nodebb.orgJ This user is from outside of this forum
              [email protected]
              wrote last edited by
              #6

              [email protected] yeah that's the thing. I think the solution for me is to loosen the restriction and handle cases where the object isn't represented locally.

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


              • Login

              • Don't have an account? Register

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