GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Conversation

Notices

  1. Embed this notice
    Chee Aun 🤔 (cheeaun@mastodon.social)'s status on Friday, 22-Nov-2024 18:32:02 JST Chee Aun 🤔 Chee Aun 🤔
    • Daniel Supernault

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

    In conversation about 7 months ago from mastodon.social permalink
    • Embed this notice
      CyberFrog (froge@social.glitched.systems)'s status on Friday, 22-Nov-2024 19:06:20 JST CyberFrog CyberFrog
      • Daniel Supernault

      @dansup@mastodon.social in general I would say release API docs and let 3rd party apps implement things correctly, but also, it's likely possible to implement very good FYP algos using mostly backend related data too (eg comment viewing, share related API calls) so maybe it might be worth implementing from a backend-first perspective and looking at if the client analytics even end up causing a significant difference in the future... then maybe it can just be generally avoided 😛

      In conversation about 7 months ago permalink
    • Embed this notice
      CyberFrog (froge@social.glitched.systems)'s status on Friday, 22-Nov-2024 19:16:22 JST CyberFrog CyberFrog
      • Daniel Supernault

      @dansup@mastodon.social I mean I'm not super knowledgeable on the value of analytics data, so I'm not sure how important knowing if the user hit the "read more" button (or similar) actually is for an effective FYP algo, but I can see how it might be useful at some point to have that kind of data coming in

      Mostly I think even if you did want to force reporting of that data, it's better to work with the 3rd party clients, rather than leaving the only 3rd partys be those that break things until their tools run

      In conversation about 7 months ago permalink
    • Embed this notice
      toto (mrtoto@social.mrtoto.net)'s status on Friday, 22-Nov-2024 19:36:26 JST toto toto
      • Daniel Supernault

      @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“.

      In conversation about 7 months ago permalink
    • Embed this notice
      Pixel Light (pixellight@pony.social)'s status on Sunday, 24-Nov-2024 16:03:32 JST Pixel Light Pixel Light
      • Daniel Supernault

      @dansup api docs would be fine. If a client were to not implement you can fall back to follows and likes as a baseline. Also just my 2 cents, I'm not against algorithms being fed with data like this but I hate how hidden the signals are in apps like tiktok. People figured out that sharing impacted the algorithm for example but that info is not shared anywhere. I'd love to see something more visible. Maybe I'll play around with these ideas when implementing these.

      In conversation about 6 months ago permalink
    • Embed this notice
      Pixel Light (pixellight@pony.social)'s status on Sunday, 24-Nov-2024 16:48:22 JST Pixel Light Pixel Light
      • Daniel Supernault

      @dansup ooh I like that

      In conversation about 6 months ago permalink

Feeds

  • Activity Streams
  • RSS 2.0
  • Atom
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.