I mean, with the fediscovery project, people can make centralised applications from fediverse data (people who opt in) this makes indexing and other stuff that works better centralised possible.
If I understand correctly, that only works with data publicly available (or at least available to 3rd party instances). But there are going to be metrics that fediverse platforms simply don’t make public or even track.
for example: i dont imagine that peertube (or even loops) makes public who viewed which videos, when, for how long. and it’d be a huge privacy issue if they did. Even tracking things like who-liked-what are the kinds of things that a 3rd party probably shouldn’t be able to just check.
without these kinds of insights, it’d be hard to make a good recommendation algorithm, because you can’t really tell how an individual is interacting with content.
The client doesn’t have access to all the videos, it’ll have to query the (distributed???) platform to find matching videos.
And the platform is gonna need to serve up some kind of metadata for the client to track (are hashtags enough???)
And the platform is gonna need to be keeping stats on the videos for the client to match against
And what would that query even look like? A gargantuan weighted map of hashtags? I can’t imagine hashtags alone would be enough.
A centralised app, like an ATproto appview is what I meant by client. It could use a fediscovery api to index videos and then it could save a users like/watch history.
I mean, with the fediscovery project, people can make centralised applications from fediverse data (people who opt in) this makes indexing and other stuff that works better centralised possible.
If I understand correctly, that only works with data publicly available (or at least available to 3rd party instances). But there are going to be metrics that fediverse platforms simply don’t make public or even track.
for example: i dont imagine that peertube (or even loops) makes public who viewed which videos, when, for how long. and it’d be a huge privacy issue if they did. Even tracking things like who-liked-what are the kinds of things that a 3rd party probably shouldn’t be able to just check.
without these kinds of insights, it’d be hard to make a good recommendation algorithm, because you can’t really tell how an individual is interacting with content.
A client could be made on one, that tracks those things, and then suggests videos from that.
I don’t think it could.
The client doesn’t have access to all the videos, it’ll have to query the (distributed???) platform to find matching videos.
And the platform is gonna need to serve up some kind of metadata for the client to track (are hashtags enough???)
And the platform is gonna need to be keeping stats on the videos for the client to match against
And what would that query even look like? A gargantuan weighted map of hashtags? I can’t imagine hashtags alone would be enough.
A centralised app, like an ATproto appview is what I meant by client. It could use a fediscovery api to index videos and then it could save a users like/watch history.