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

ekk

jesseplusplus@mastodon.socialJ

[email protected]

@[email protected]
About
Posts
6
Topics
1
Shares
0
Groups
0
Followers
0
Following
0

View Original

Posts

Recent Best Controversial

  • @frequency now fully supports FEP-7888 as of yesterday!
    jesseplusplus@mastodon.socialJ [email protected]

    🫶🏻 aw thanks @dansup!

    I’d love to collaborate on better compatibility with pixelfed! I’m super interested in trying to get stories in frequency like you have in pixelfed someday!

    I’m planning to be at FediCon, so I’d love to meet ya and scheme on what kinda cool stuff we can do 😎

    Uncategorized

  • @frequency now fully supports FEP-7888 as of yesterday!
    jesseplusplus@mastodon.socialJ [email protected]

    @silverpill awesome, thanks for testing and adding to the list!

    I'd love to use `OrderedCollection` here but fell back to following Mastodon's convention for the replies collection. (Mastodon doesn't currently index notes on creation time, so that kind of ordering isn't performant.)

    I do return them ordered by id to make it as nice as possible, but this isn't guaranteed to be the creation order depending on when my server saw different replies, so I'm still marking it as unordered.

    @julian

    Uncategorized

  • @frequency now fully supports FEP-7888 as of yesterday!
    jesseplusplus@mastodon.socialJ [email protected]

    @julian I think that makes sense. As the spec progresses, I can see you running into other use cases where ids are referenced in various collections, but you can’t access the object, either because it’s unavailable or due to lack of permissions.

    Uncategorized

  • @frequency now fully supports FEP-7888 as of yesterday!
    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.

    Uncategorized

  • @frequency now fully supports FEP-7888 as of yesterday!
    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 🤓

    Uncategorized

  • @frequency now fully supports FEP-7888 as of yesterday!
    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.)

    Link Preview Image
    Implement FEP-7888 - conversation context by jesseplusplus · Pull Request #188 · jesseplusplus/decodon

    This PR implements FEP-7888 by: generating a context property and including it in the ActivityPub json-ld for all Statuses consuming the context property on incoming objects and fetching all obje...

    favicon

    GitHub (github.com)

    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.

    Uncategorized
  • 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
  • World
  • Users
  • Groups