I highly recommend following the official tutorial to create a browser extension for your preferred browser, and just making any changes to websites there instead of installing extensions made by someone else. For example, removing youtube shorts is like five lines of code in my personal extension. The rate at which published browser extensions turn into malware has escalated from “oh that’s concerning” to “How many times do I have to teach you this lesson old man”
"Return YouTube Dislike" Chrome Extension Injecting Ads
31–40 of 53 posts
Re: "Return YouTube Dislike" Chrome Extension Injecting Ads
#32Earlier quoted context omitted.
I'm skeptical that it's of any use considering it's only going to be installed by people who specifically want to dislike. It seems more likely that the like/dislike ratio is going to be heavily skewed towards dislikes just by the stated purpose of the plugin and who it appeals to.
I don't think the extension is installed by people that wanna dislike, rather by people that wanna see the dislike count. I used to have it since it's very useful to see if something like a tutorial is a scam. Also if I remember correctly, the extension was created before youtube completely removed the count, and it scraped the actual value from youtube to add it to the db while the count still was available
> I don't think the extension is installed by people that wanna dislike, rather by people that wanna see the dislike count.
Yes but the corollary is that the dislikes you see are an estimate extrapolated from dislikes from people who use the extension.
In other words if people want their dislike to be seen, they need the extension.
Re: "Return YouTube Dislike" Chrome Extension Injecting Ads
#33I highly recommend following the official tutorial to create a browser extension for your preferred browser, and just making any changes to websites there instead of installing extensions made by someone else. For example, removing youtube shorts is like five lines of code in my personal extension. The rate at which published browser extensions turn into malware has escalated from “oh that’s concerning” to “How many…
You don't even need to make your own extension, which requires a bunch of boilerplate and docs. Userscripts (eg. greasemoney) or userstyles (eg. stylus) is often all you need, and much more straightforward to make.
Re: "Return YouTube Dislike" Chrome Extension Injecting Ads
#34Earlier quoted context omitted.
> the extension requires quite a large database (~15TB) Maybe I am missing something but how does a database which just needs to store video ID and a number become 15TB in size?
Also a user ID, which seems to be 36 base64 characters (can't have one user count for multiple votes). Round up to 500 raw bytes per row (perhaps including time/ip and other random garbage, plus indexes), 3x replication/redundancy or something, for 6 million users each having voted on 500 videos, and you're at 6TB; still some ways off from 15TB, but not insurmountably far. (votes/user is rather tricky to get; but, as…
500 bytes? A user ID couldn't be more than 8, a date is another 8, a video ID is another 8, and an IP is 16. Even if you assume there is some overhead, a database cannot possibly need more than 100 bytes per row.
Re: "Return YouTube Dislike" Chrome Extension Injecting Ads
#35Earlier quoted context omitted.
> the extension requires quite a large database (~15TB) Maybe I am missing something but how does a database which just needs to store video ID and a number become 15TB in size?
Also a user ID, which seems to be 36 base64 characters (can't have one user count for multiple votes). Round up to 500 raw bytes per row (perhaps including time/ip and other random garbage, plus indexes), 3x replication/redundancy or something, for 6 million users each having voted on 500 videos, and you're at 6TB; still some ways off from 15TB, but not insurmountably far. (votes/user is rather tricky to get; but, as…
Why not summarize every 3 months? It would allow someone to downvote every 3 months on the same video but it's easier to just install this extention on another profile.
It would bring the size down to under a 1T and allow the developer to go ad free. Hope this message reaches him.
Re: "Return YouTube Dislike" Chrome Extension Injecting Ads
#36You gotta be a bit short sighted to imagine that the kind of people that would download an extension would accept ads. On the other hand, you also have to be a bit short sighted to be installed gargabage like "an extension so you can downvote" lol.
They won't "accept ads" but they also won't pay for the extension, so I think in practice this is a good way to tell users "you're costing me money, go away."
I think this every time someone suggests an alternative to YouTube. Sorry but no one is making a video hosting service for users who both reject adverts and a premium subscription. And no content creator is going to work for free to post there.
Re: "Return YouTube Dislike" Chrome Extension Injecting Ads
#37I highly recommend following the official tutorial to create a browser extension for your preferred browser, and just making any changes to websites there instead of installing extensions made by someone else. For example, removing youtube shorts is like five lines of code in my personal extension. The rate at which published browser extensions turn into malware has escalated from “oh that’s concerning” to “How many…
How would your tutorial help get voting information from other users?
Re: "Return YouTube Dislike" Chrome Extension Injecting Ads
#38You gotta be a bit short sighted to imagine that the kind of people that would download an extension would accept ads. On the other hand, you also have to be a bit short sighted to be installed gargabage like "an extension so you can downvote" lol.
You can downvote youtube videos without the extension, the extension just shows how many people downvoted a video since youtube took that visibility away a few years ago. It does help when there are shitty video recommendations and can ignore videos that have a bad ratio
Subtle correction: The extension shows how many users of the extension downvoted the video. It has no way of knowing what non-extension-users did.
Re: "Return YouTube Dislike" Chrome Extension Injecting Ads
#39Earlier quoted context omitted.
Also a user ID, which seems to be 36 base64 characters (can't have one user count for multiple votes). Round up to 500 raw bytes per row (perhaps including time/ip and other random garbage, plus indexes), 3x replication/redundancy or something, for 6 million users each having voted on 500 videos, and you're at 6TB; still some ways off from 15TB, but not insurmountably far. (votes/user is rather tricky to get; but, as…
500 bytes? A user ID couldn't be more than 8, a date is another 8, a video ID is another 8, and an IP is 16. Even if you assume there is some overhead, a database cannot possibly need more than 100 bytes per row.
That's assuming all of those are stored in packed formats, but even then it's not that low.
I already mentioned that the user IDs are 36 base64 chars, or 27 bytes if you store them max-packed; YT video IDs are 11 base64 chars, so 66 bits, doesn't quite fit in 8 bytes (not to mention that trying to pack the video IDs would mean your db becomes useless if youtube suddenly added a new video ID format). IP needs another bit somewhere for ipv4 vs ipv6, so likely 24 bytes (or just a string could be used).
Then you have some overhead for padding and string field lengths, and whatever overhead for packing the data for the disk storage (padding for all entires to stay within a page? maintaining a percentage of free space to ensure the B-tree property?). Then you have a copy of the fields in indexes, with whatever overhead those come with.
Granted, even that's probably around 200 bytes, not 500, in a reasonable db, but who's to say that the db used used is a reasonable & well-configured one; of course it's possible that a bunch more metadata is stored for user trustworthiness statistics or something, or duplicated tables where relations would work.
Re: "Return YouTube Dislike" Chrome Extension Injecting Ads
#40Earlier quoted context omitted.
Also a user ID, which seems to be 36 base64 characters (can't have one user count for multiple votes). Round up to 500 raw bytes per row (perhaps including time/ip and other random garbage, plus indexes), 3x replication/redundancy or something, for 6 million users each having voted on 500 videos, and you're at 6TB; still some ways off from 15TB, but not insurmountably far. (votes/user is rather tricky to get; but, as…
Why not summarize every 3 months? It would allow someone to downvote every 3 months on the same video but it's easier to just install this extention on another profile. It would bring the size down to under a 1T and allow the developer to go ad free. Hope this message reaches him.
That'd easily result in accidental re-votes if a user watches the same video every couple months (and such re-watchers would likely be ones that.. like the video, thereby skewing data away from dislikes over time).
Especially if the extension just sends the vote status instead of only reacting on a press (which'd allow it to send forward a vote done originally on, say, mobile; don't know if it does this, but it seems like a useful thing to do).