7
1
Fork
You've already forked interop
0

Purchase protocol exploration #16

Open
txels wants to merge 1 commit from purchase-proto into main
pull from: purchase-proto
merge into: fairplayer:main
fairplayer:main
fairplayer:discovery-tiers
fairplayer:smaller-ci-image
fairplayer:js-restructure
fairplayer:repo-info
fairplayer:ci-image-optimisation
fairplayer:ci
fairplayer:add-essays
fairplayer:use-mdbook
fairplayer:consent-first-notes
fairplayer:canimus-pydantic-schema
fairplayer:streaming-spec
fairplayer:nlnet-app
fairplayer:rough-initial-plan
Owner
Copy link

Conversation originally raised in a private space with Mirlo and Fairplayer participants, transcribed here for visibility and to continue driving this towards a publishable protocol.

Conversation originally raised in a private space with Mirlo and Fairplayer participants, transcribed here for visibility and to continue driving this towards a publishable protocol.
Purchase protocol exploration
All checks were successful
ci/woodpecker/pr/publish Pipeline was successful
1aaf126f41
txels 2026年06月18日 16:17:03 +02:00
txels force-pushed purchase-proto from 1aaf126f41
All checks were successful
ci/woodpecker/pr/publish Pipeline was successful
to 81b5590ac1
All checks were successful
ci/woodpecker/pr/publish Pipeline was successful
2026年06月18日 16:18:03 +02:00
Compare
@ -0,0 +16,4 @@
> Simon (Mirlo): Yeah adding a redirect url to the purchase response is on my very long todo list. It'd be very useful for other things too. FWIW I'm working on simplifying the purchase endpoint, though I'm not actually sure whether what I'm doing here is desirable to FP. The idea is there would be one endpoint for all purchases in a standardized way (basically a cart). This is very desirable for us, but it feels like actually might be an issue for FP who probably want a "buy this specific album" URL in the Canimus spec.
> Carles (Fairplayer): This may actually make a lot of sense for us in the long run, since what we aim to do can be expressed as "create listener communities where it's easy to support artists" and one way we can make that easy is by pooling payments, so you can support multiple artists with a single transaction. This could apply maybe not so much to album purchases but to things like "support the artists you've enjoyed this last month (or those you manually choose to) with a single payment".
Author
Owner
Copy link

Maybe after considering the "shopping cart scenario" a better solution rather than to think about this as a "redirect" is a callback notification (aka webhook) that may happen sometime in the future. I.e. after the user has finally made the payment, maybe long after putting the item in a shopping cart.

Maybe after considering the "shopping cart scenario" a better solution rather than to think about this as a "redirect" is a callback notification (aka webhook) that may happen sometime in the future. I.e. after the user has finally made the payment, maybe long after putting the item in a shopping cart.
All checks were successful
ci/woodpecker/pr/publish Pipeline was successful
This pull request has changes conflicting with the target branch.
  • docs/SUMMARY.md
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin purchase-proto:purchase-proto
git switch purchase-proto

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff purchase-proto
git switch purchase-proto
git rebase main
git switch main
git merge --ff-only purchase-proto
git switch purchase-proto
git rebase main
git switch main
git merge --no-ff purchase-proto
git switch main
git merge --squash purchase-proto
git switch main
git merge --ff-only purchase-proto
git switch main
git merge purchase-proto
git push origin main
Sign in to join this conversation.
No reviewers
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
fairplayer/interop!16
Reference in a new issue
fairplayer/interop
No description provided.
Delete branch "purchase-proto"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?