Replying to Avatar BITwise šŸ³ >>= RIGHTish

The use case is as follows. Real life example: uploaded a track. Turns out, there was a minor error in the mix and uploaded finalv2 instead of finalv2forreal. Everything's been published and suddenly we find this error. Now we need a new audio file.

Another scenario - feed is published. New band member joins. As part of their deal, they get a minor cut of back catalog. Now we need to update splits (presumably this metadata is saved in the kind zero?).
Avatar
mrclownworld 0mo ago

Hmmm these are cases I wasnā€™t thinking of. Iā€™m thinking as publishing video content, like a film. A canonical publication seems ideal.

An even simpler solution to resiliency would just be a ā€œmirrorā€ note kind. This offers an alternative link to the shared media. If the original note has the hash, this can prevent mismatched mirrors.

Does RSS handle mirrors? I donā€™t know enough about it

Reply to this note

Please Login to reply.

Discussion

Avatar
BITwise šŸ³ >>= RIGHTish 0mo ago

So RSS is simplicity in action. RsS is literally a huge text file full of metadata. It contains tags, which can be created at whim. The only pseudo-requirement is consensus. If other ppl use it, its a thing. If youre the only one, then it isnt. Sorta like publishing a kind, but easy like making up a hashtag. When you hear someone say PC2.0, it really refers to the generally accepted namespace. A tag can be anything like "artist" or "splits".

To answer your question... since all you're doing is putting the source location of the audio file next to the appropriate tag, id imagine that if its a printable address, it can be permalinked in the feed. If you need to change the link, thats a quick change in your txt file.