WelcomeWEFreedomWindsorEssexCounty-ActionCommunicationsRalliesResourcesSocialEventsWednesdayNightMeetings-ActivismAgoraAgorismCanadaCommonLawCommunityDataCentersDataCentresDoocracyFarmersMarketIntroductionsNaturalLawNewslettersOntarioOrganizingOutreachProjexProjexWikiRalliesResistanceAnalysisSoireesSoiréesWikiSpooksWindsorElectionsTop Subs
5
MatrixDev - - (+4|-0)
I added some upvote and downvote buttons to gvid(self)
2 commentsbyx0x7

https://gvid.tv/v/TWbI5W5p

In the pre-tailwind version of the front end there was an upvote button. All it did was add a video to a liked playlist. Now there is both upvote and downvote and also upvote and downvote on thumbnails. It recommends and or disrecomends the video against your history in both directions.

In a way a thumbnail upvote functions a bit like youtube's watch later, and it will behave more like that once I modify the way history works. So if you see more than one video you want to watch upvote the thumbnails and then watch one of them.

The next step I want to take is change the way I handle history so it has a scalar value associated with it. Then a downvote can live in your history and continue to disassociate with history going forward and an upvote will be able to more significantly impact recommendations.

I think doing this plus the recent clamping of magnitudes in both rows and columns of the suggestion matrix, plus log clamping which is some math I won't go into, plus the addition of a few random videos to all suggestions; I think this is going to make gvid suggestions really good.

The column clamping means that a video can only become so recommendable and beyond a certain point will get recommended harder within its own ecosystem instead of everywhere.

The row clamping means, and this is the one I did more aggressively, that no one video can over drive your recommendations.

The log clamping without showing too much math basically besides setting hard limits on some of the row and column magnitudes also tones down their distribution.

But really the upvotes and downvotes should do a lot instead of just rewarding click through. No shame in downvoting something. These aren't reddit downvotes. All a downvote does is kick something back into its own ecosystem.

Comment preview

[-]JasonCarswell1(+1|0)

Neato!!!

I'd like a way to mark what I've seen, not positive nor negative, just seen. I don't want to support meh stuff, and I also don't want to be negative toward it - especially if it may be good to others.

Also...
MetaVote™ : neutral center + 4 corners of main extremes + 5x5 grid of 25 options + max 4 degrees of separation.

  1. Brilliant 2) Clever 3) Witty 4) Funny 5) Fun
  2. Wise 7) Insightful 8) Charming 9) Like 10) Good
  3. Bland 12) Typical 13) Okay 14) Meh 15) Weak
  4. Lacking 17) Daft 18) Shame 19) Dislike 20) Bad
  5. Bored 22) Waste 23) Regret 24) Hate 25) Repulsed

Beside the ToS and Donate in bottom right you might add a link to "Markdown tips" (so I could do a better table).

parentlinkreply
[-]x0x70(0|0)

I agree on highlighting unseen comments. That is a goal. Metavote would just be UI clutter. Also it would add substantial technical debt and complexity to all layers of the stack while not yielding any non-ambiguous impact on front end algorithms. This would slow down agility in any future development because new complexity always multiplies against existing complexity.

I decided being more honest is a good thing. This is pretty much the worst suggestion possible. I get that you want to have specific intention behind your vote but without a way to carry out that specific intention in a way that is coupled to the specific outcome sought it's really pretty pointless. If you can develop the concept complete from end to end then I might be interested. But if it's just extra UI that doesn't do anything why even think about it? I want to say this as firmly as possible. No. Flat rejection.

Adding Markdown tips to the footer or even a general help with links within basically a table of context is a good idea.

parentlinkreply