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.
Discussion
Loading...
![gabboman the wafrn dev [SINGLE INSTANCE EDITION]](https://media.gabboman.xyz/1764776490819_e536f6b79c3beea6716621b8e437c4430a427641_processed.webp "gabboman the wafrn dev [SINGLE INSTANCE EDITION]")
@dansup@mastodon.social
I have to properly do it in wafrn, but its a good idea tbh. Its GTS interaction policies, more software should implement it! Me included
@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.
@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!
@dansup
Can't wait for this feature in pixelfed 🥰
@joergi Me too, and thanks to Loops it will be much easier, and quicker to implement 😉
@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.
@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
1 more replies (not shown)