Related to #17
Problem:
The shared database system is vulnerable to malicious --replace submissions.
A user could intentionally submit incorrect matches (e.g., rickrolls, memes, or unrelated songs) and sabotage the database.
Possible Solution:
Before accepting a --replace into the global database, the server performs a lightweight plausibility check to determine if the proposed YouTube link could reasonably be a match for the given Spotify track.
Note:
The client answers the question:
"Which song on YouTube is the PERFECT match for this song on Spotify?"
The server, on the other hand, must answer the question:
"Is this song on YouTube a PLAUSIBLE match for this song on Spotify?"
Related to #17
Problem:
The shared database system is vulnerable to malicious
--replacesubmissions.A user could intentionally submit incorrect matches (e.g., rickrolls, memes, or unrelated songs) and sabotage the database.
Possible Solution:
Before accepting a
--replaceinto the global database, the server performs a lightweight plausibility check to determine if the proposed YouTube link could reasonably be a match for the given Spotify track.Note:
The client answers the question:
"Which song on YouTube is the PERFECT match for this song on Spotify?"
The server, on the other hand, must answer the question:
"Is this song on YouTube a PLAUSIBLE match for this song on Spotify?"