Originally posted by @woolfg in #90 (comment)
see https://github.com/openpodcast/anchor-connector/pull/5#issuecomment-3239196595
as it is the same format as spotify we could use the same table as spotify and just adapt the API or even split the payload and send it to the spotify api? we hast have to think how to handle the different ids ... but I have seen that even the spotify ids are used sometimes in anchor, so i guess they move towards the spotify echosystem anyways. we could rely on the spotify ids for this part already. we just need a mapping table (if not already present).
Originally posted by @woolfg in #90 (comment)
see https://github.com/openpodcast/anchor-connector/pull/5#issuecomment-3239196595
as it is the same format as spotify we could use the same table as spotify and just adapt the API or even split the payload and send it to the spotify api? we hast have to think how to handle the different ids ... but I have seen that even the spotify ids are used sometimes in anchor, so i guess they move towards the spotify echosystem anyways. we could rely on the spotify ids for this part already. we just need a mapping table (if not already present).