Conversation

Notices

1. Embed this notice
   Daniel Supernault (dansup@mastodon.social)'s status on Thursday, 15-Jan-2026 19:19:14 JST Daniel Supernault

   Implementing QuotePosts in Loops is taking a tad longer than expected.

   I don't understand why they require a QuoteRequest handshake if the interactionPolicy is public, seems overengineered and wasteful to me.

   #ActivityPub #QuotePosts #FEP044f

   • Embed this notice
     Daniel Supernault (dansup@mastodon.social)'s status on Thursday, 15-Jan-2026 21:13:13 JST Daniel Supernault

     in reply to

     • Jörgi (chaos.social)

     @joergi Me too, and thanks to Loops it will be much easier, and quicker to implement 😉

   • Embed this notice
     Jörgi (chaos.social) (joergi@chaos.social)'s status on Thursday, 15-Jan-2026 21:13:14 JST Jörgi (chaos.social)

     in reply to

     @dansup
     Can't wait for this feature in pixelfed 🥰

   • Embed this notice
     Daniel Supernault (dansup@mastodon.social)'s status on Thursday, 15-Jan-2026 22:30:53 JST Daniel Supernault

     in reply to

     • David Roetzel

     @dave oh yeah, that does make sense. Giving users the ability to have fine-grained controls over this is very clever, albeit Loops defaults to public for public Loops posts, but we will allow users to opt-out in the future.

     Btw, love your work on Mastodon, and hope to chat with you soon regarding FASP 😉

     Take care!

   • Embed this notice
     David Roetzel (dave@upp2.com)'s status on Thursday, 15-Jan-2026 22:30:54 JST David Roetzel

     in reply to

     @dansup interactionPolicies are there so that you can set the right expectations in your UI (e.g. not offer to quote someone who never ever wants to be quoted).

     The quoteAuthorization part is necessary, so that implementations can (in theory) offer manual approval on a per-post basis and (quite practically) to allow revocation of consent after the fact.

     It tends to confuse me as well every now and then, but it makes sense when you think about it some more.

   • Embed this notice
     Daniel Supernault (dansup@mastodon.social)'s status on Saturday, 17-Jan-2026 08:42:23 JST Daniel Supernault

     in reply to

     • :PUA: Shlee booped around &
     • Jörgi (chaos.social)

     @shlee @joergi we can likely abstract the federation code, but the two platforms are structurally very different, Loops has a videos table/model with one media src, Pixelfed has a polymorphic statuses table and media table that can also be replies/boosts and text only posts.

   • Embed this notice
     :PUA: Shlee booped around & (shlee@aus.social)'s status on Saturday, 17-Jan-2026 08:42:24 JST :PUA: Shlee booped around &

     in reply to

     • Jörgi (chaos.social)

     @joergi @dansup I’ve been meaning to ask if it’s worth having one backend (loops mode or Pixelfed mode) and two front ends / two mobile apps.

   • Embed this notice
     Jörgi (chaos.social) (joergi@chaos.social)'s status on Saturday, 17-Jan-2026 08:42:25 JST Jörgi (chaos.social)

     in reply to

     @dansup
     if you make now (as far as I understood) pixelfed the same tech stack as loops, does it make sense to move duplicate/similar code to an extra library? In theory it's only backend functionality, which can be tested with unit tests. You then need just frontend tests in pixelfed/loops for it to see if it works.
     But maybe it's too complex to keep it working for both? Especially if you have (at one point hopefully) different separate teams to take care of loops and pixelfed. Just an idea.

   • Embed this notice
     Daniel Supernault (dansup@mastodon.social)'s status on Saturday, 17-Jan-2026 17:48:39 JST Daniel Supernault

     in reply to

     • :PUA: Shlee booped around &
     • Jörgi (chaos.social)

     @joergi @shlee Yeah true, I do want to abstract the Loops federation logic into a Laravel Package that Pixelfed could eventually use, along with other projects!

     The way I wrote Loops ActivityPub logic is really clever, that's how I was able to add support for QuotePosts in just a few hours the other night!

   • Embed this notice
     Jörgi (chaos.social) (joergi@chaos.social)'s status on Saturday, 17-Jan-2026 17:48:40 JST Jörgi (chaos.social)

     in reply to

     • :PUA: Shlee booped around &

     @dansup
     But making the federation code in an extra library can also help others for building a new project. So they can focus on the building of the project , without needing to have too much idea of the protocol.

     In theory, it's also great for running integration tests against testcontainers with Lemmy, Mastodon, loops, pixelfed peertube and so on. To ensure it's working against all of them.
     But I guess it's a lot of work
     @shlee