Comment on Basic recommendation video algorithm for peertube
asudox@lemmy.asudox.dev 1 week ago
Looks cool. It’s pretty similar to how I thought of doing this as well. Do you have a prototype? You might be able to adjust the algorithm if you receive feedback from some PeerTube veterans.
Cattail@lemmy.world 1 week ago
i havent made anything yet i just wanted to articulate that a basic algorythm can be done ethically where either instance/watcher/fediverse in general can make a vector to define a video and that could be shared via activity hub and the user can have a vector for themselves and even their own algorithm to sift through videos.
im just starting and right now i have to figure out how to format the video vector do i want .json .csv .xml
asudox@lemmy.asudox.dev 1 week ago
Why would the video vectors be federated though? Let alone stored on the instance? These things can be calculated instantly on the device.
Cattail@lemmy.world 1 week ago
be better to store the video vector on an instance so that watchers can retrieve, just logistics. video vector (element) can be calculated anywhere just communicated to an instance, the idea is to be flexible. activityhub protocol has made the decisions easy the video vector has to be a .json element in a video json data.
it would be better to store the results of a calculation to avoid repeated calculations. im looking into music classifications, and like the entire video can be sent to parse to see if its music or not, the tempo, genra, id assume that would be fairly costly to calculate or instance can send the video vector that states all that information