Debating how to handle API usage with Loops, for the...

Debating how to handle API usage with Loops, for the FYP, its essential that the client handles reporting specific analytics to the backend to improve the algo (ie: watch time, if you opened comments, share)

3rd party clients may not report that data, and I considered implementing Device Attestation to enforce only official apps, but why?

I'd rather encourage 3rd party devs to consume the FYP apis like the official app, and publish API docs

I think that's the way to go, wdyt?

#loops

Like 22 November at 9:00 | Open on mastodon.social

7 comments

James Smith 💾

@dansup As lots of sensible people have said, "Make Things Open, It Makes Them Better". Someone may build a completely privacy-focused app that doesn't report anything or improve the algorithm, and that's a choice people should have! (Arguably, that should be a choice in the official app too)

22 November at 9:11 | Open on mastodon.me.uk

Anopka

@dansup Probably not everybody will use 3rd party apps for Loops, but I think for those who do and for those apps that don't report that data, I'd respect that decision of the app since it is some sensitive data and some people don't want to share that data.

And I think it's much healthier for the Fediverse when 3rd party apps are encouraged to be used and don't get locked out.

There might be other ways to improve the FYP algo without these analytics that would work on 3rd party apps as well.

22 November at 9:21 | Open on social.tchncs.de

Chee Aun 🤔

@dansup might open up to abuse too e.g. clients spamming the analytics and mess up the algo.

22 November at 9:31 | Open on mastodon.social

dansup

@cheeaun if clients do abuse this, it would only hurt their users, which could lead to them losing their userbase.

There is no incentive to "game" the algo, because these stats are only used for your own algo.

22 November at 10:38 | Open on mastodon.social

Mark

@dansup
I would not rely on clients. I don't think it is relevant how long a minute long video has been watched. Just count it on the server side. Same for comments I guess. Sharing could be tricky, but still one could just copy paste the link via browser. Maybe generating a utm link could work to add the counter into the link.

22 November at 9:37 | Open on chaos.social

toto

@dansup I would argue that having the option for 3rd party clients or alternative clients is a key element to any open platform. While closed platforms can innovate faster in certain aspects this is the key which allows innovation in an open system. Give 3rd party clients the option to play along. Maybe offer some „certification“ so clients can say „I’m a real good citizen“.

22 November at 10:32 | Open on social.mrtoto.net

dansup

@mrtoto Yeah, I'm not willing to limit access to APIs.

There is no valid reason to, we don't have funding or investors to satisfy, so why try to emulate the worst parts of platforms like these?

My best bet is to provide the docs and advice to 3rd party devs to report these stats for the best user experience.

It's not like the official app will have any edge, and it only benefits the users to provide these basic stats so they get shown more relevant content.

22 November at 10:36 | Open on mastodon.social