Condense burn + burnBatch functions?

[0xTranqui]

@iainnash any reason we cant condense burn + burnBatch functions so that you are always passing in array of inputs, similar to what we did with the addListings function?

burning functionality is present on lines 231-242 of curator.sol

[iainnash]

The reason we keep both functions and the name of burn is a user can remove a listing from zora marketplace / opensea just by burning the NFT.

[0xTranqui]

are you saying burnBatch doesn't achieve the same thing?

[iainnash]

marketplaces look for burn(uint) as the function signature to call for burn. just keeping w/ the informal standard for allowing standard uis to work as expected with both functions.

[iainnash]

Upon reading more of the README do we want to do burn(uint) and removeListings(uint[])

[0xTranqui]

I think we should keep it just as burn so as to lean into the fact that you can use indexers to find all active listings at any point