I treat social media as pure discussion platform to advance understanding or to know new stuff.

There had been something on my mind lately which I wanted to discuss as a way to improve the upvotes relevance to the quality of the post and the amount of discussion.

Let’s apply quality control on upvotes, so any post can get only 20 upvotes till it gets a specific amount of comments then the limit could be pumped up to 40 upvotes till it gets more comments, etc…

Why I am bringing this up, you might ask? The linked post by me is the peek proof of my point.

It’s pretty clear no one read the linked article and despite that, the post is the top post in the technology community. There is no comments discussing directly the story and from the face of it, There does not seem to be any indicator that any one benefited from this.

I skimmed over the story and shared it in the hopes to basically learn new stuff, get relevant recommendations or basically read some direct discussions.

In any way, I think my described system to handle upvotes would highly improve Lemmy, taking into consideration that numbers used are only for demonstration and the used numbers will need to be figured out separately.

Should this system be implemented into Lemmy?

  • Rimu@piefed.socialEnglish
    91·
    1 day ago

    Upvotes without reading do suck but comments without reading are worse. I’ve been considering adding a highlight/boost on comments where the author has clicked the link.

    Also we could weight the votes so votes after reading have 2x the effect.

    • Pro@suppo.fiEnglish
      3·
      1 day ago

      You can’t do that with different clients.

      Simply put, you can’t force all the clients which currently support piefed to respect that.

      You can control the server, you can’t control the clients.

      • Rimu@piefed.socialEnglish
        27·
        1 day ago

        If clients want the get into an adversarial relationship with the project they’re piggybacking off, they will lose.

      • mesa@piefed.socialEnglish
        2·
        1 day ago

        A quick js + db change boom done.

        But it may confuse users depending on the implementation. And federation would not be fun…

          • Rimu@piefed.socialEnglish
            4·
            1 day ago

            JavaScript. Attach a click handler event to the article link, save a cookie with the post id in it.

              • Rimu@piefed.socialEnglish
                2·
                1 day ago

                Federation, it’s magic.

                But yeah, this means Lemmy comments would never be boosted or highlighted because it wouldn’t be federating the new data. Bit of a problem!

                • SorteKanin@feddit.dkEnglish
                  8·
                  1 day ago

                  Wait, you’re going to federate whether a user clicked on a link between instances?

                  That seems kinda too far. I would not want other instances to know what I have or have not clicked. That’s a level of surveillance I’m not comfortable with and I fear how that data might be abused.

                  Tbh I wouldn’t even want my own instance to track what I click