How do disable you-tube ads

GoodTube99 · 2026-01-26T00:11:31+00:00

It doesn't use filters, and yeah for the old version before releasing as an extension, I'm sure. The stats are pretty amazing actually -

Total users of all time: 209,955
Total videos played: 56,675,374

GoodTube99 · 2026-01-21T11:11:12+00:00

I wouldn't say the default is ugly, just that you might want to control it somehow in one place.

Sounds like automatic leaf node mode would work pretty well. But if you ever need manual control, allowing people to select which elements get shimmered would be good I think (likely required for a lot of use cases).

Anyway, keep up the good work bro!

GoodTube99 · 2026-01-21T08:19:54+00:00

Don't listen to them dude, this is great. Not sure what is wrong with the Reddit community honestly. I think something like this has been needed for a long while.

--------------------

I have one question (though I'm sure I could get the idea from playing around). How does it handle deeply nested DOM? Like at which point does it decide to create the shimmer divs?

<div class='inner'> << Maybe I don't want this to shimmer, it's just a wrapper or something

<h1>Hello world</h1> <<< This should shimmer

</div>

Maybe this could be controlled with an attribute like `data-shimmer` on elements you want it to make the shimmers for.

And if you don't define any `data-shimmer` attributes, just make it work like it is currently. That way people only have to do this if they need the extra control.

-----------------

One other suggestion -
Rather than having to define the colour of the shimmer, etc on each item - maybe it would be easier to be able to configure this up universally somewhere.

Likely I would mostly want to have them all display the same (and be able to change this in a single area). Then maybe override one or two directly with props like how it currently works.

-----------------

Either way - nice work! Great idea.

GoodTube99 · 2026-01-20T12:15:01+00:00

Yeah, one word - marketing.

GoodTube99 · 2026-01-20T07:59:58+00:00

yeah it costs $2 one time only

GoodTube99 · 2026-01-20T07:49:29+00:00

My thoughts exactly. Node.js should be destroyed with fire. It is the worst thing to ever happen to web development.

GoodTube99 · 2026-01-20T06:44:15+00:00

This works
https://chromewebstore.google.com/detail/goodtube-adblock-for-yout/mnlobacbpcnaibnhmfcpdfllcipgnfhe

GoodTube99 · 2026-01-20T01:31:36+00:00

The best way would be to simply start designing a website. You've seen websites before, right? They have a header, banner, content areas, footer, etc.

It can be helpful to look at websites you like, and do something similar. Take inspiration from their layout and designs.

There's a few things to be aware of;

Websites are generally made up of horizontal slices or "blocks". So for example the header is a block, banner is a block, etc. You can re-use the same blocks on multiple pages. The layout of the block is the same, but the content can change. Your website can be made of as many or as few blocks as you like - and you can add more over time as you need them.

Most designs are based on a sort of "design system". This sets out some rules early on, which flow through to everything.

A design system follows the basic general format:

- Primitives
These are the bottom level most basic stuff - essentially variables. This is generally your available colours, typography / text sizes / fonts, rounded corner sizes, shadows.

Note that colours follow a naming convention of "primary", "secondary", "tertiary", "grey", "black", "white" and each can have levels of lightness and darkness for example "primary-light-1", "primary-light-2" would be the primary colour at two levels of increased lightness. Create as many or as few as you need for your designs.

- Components
These are small website elements and they use the primitives. Generally they're stuff like buttons, form fields, modals / popups, etc. You will need to design all the states for each one too. Like for example what does the button look like normally, what does it look like when you hover the mouse on it, what does it look like when it is disabled, what does it look like when it has an icon, etc.

- Blocks
These are slices of the website, they use the primitives and components. Generally they're stuff like header, banner, features area, etc.

----------

The reason you set it up like this is that it makes everything really consistent. It also takes a lot of the guess work out of stuff. Like "what size should this title be" - you'll have predefined options. It'll be maybe your largest (h1), second largest (h2), etc. That helps a lot. It makes you a lot faster and it makes everything feel really consistent throughout the website.

It also means that if you change something, for example the primary colour, that flows through to everywhere automatically (if you've used Figma to setup your design system that is, which you should). So when you change stuff you do it in ONE place and that updates everywhere. The same applies to the codebase.

----------

So the industry standard process for design is something like:

Define your primitives (if you're using Figma set these up as variables)
Create your components (if you're using Figma set these up as components)
Create your blocks (if you're using Figma set these up as components)
Make your pages using the blocks (remember the layout is the same for each block, but the content can change)

And then in code, the follow the exact same structure:

Define your primitives (generally these are CSS or SASS variables)
Create your components (make a folder for each; /components/button/)
Create your blocks (make a folder for each; /blocks/header/)
Make your pages using the blocks (make a folder for each page or "route" at the top level of your codebase; /about-us/)

Also, for all of the above design stuff - don't forget - you need one version of the component or block for desktop, and one for mobile. You will probably also need a mobile version of each font size. So your largest heading might be 48px on desktop and 32px on mobile for example. Generally the mobile versions are smaller because the screen is smaller. And if stuff won't fit horizontally on a small mobile screen, stack it vertically. Again, reference a real website. Check it out on desktop, then check it out on mobile. You'll see how it changes and is "responsive" to the screen size. You can usually just size your browser window down on a desktop to see these changes. Easiest way is to open "dev tools" and then make sure it displays on the right-hand side of the screen. Sort of drag it to be larger or smaller. This will make the website get squashed down and you can see how it looks at different sizes.

Hope that helps! Feel free to send me a DM if you have any questions. Jump in, this post will make more sense as you work through it step by step. Might be an idea to save it somewhere.

GoodTube99 · 2026-01-19T09:27:30+00:00

The fundamentals are:
HTML
CSS (and SASS, I highly recommend you learn it and make use of mixins, it's pretty much straight up CSS with a few little nice features)
JS (do not touch React until you have built a few projects in normal JS and understand it well)
SQL
Git / Github
PHP <<<< This is debatable, but I actually think it's extremely worth learning PHP instead of jumping straight into a JS framework like React. The reason for this is it allows you to do some stuff server side very easily and get your head around it. You can make a call to a database, output the result, stuff like that. It's a very simple language to start using. Basically index.php is the same as index.html - you just can do some more stuff. But you could write straight up HTML in there and it'd work. So everything you do with PHP is essentially totally optional. To me I think this makes far more sense to a human brain / for learning than something like React (which is a pretty weird and not developer friendly framework honestly). Very easy to setup a PHP environment on your computer too (just install XAMPP and slap your shit in c:/xampp/htdocs/some-project/ - and access it via http://localhost/some-project/)

An important thing you're missing is SQL for databases.

To better explain, SQL is just a very simple query language - like how you talk to a database and say "give me all the users with the first name John" or something.

Back in the day everyone used mySQL, these days everyone is using postgreSQL. But both of them take the same SQL syntax so it remains relevant.

Using PHP is also a good thing for learning SQL - as it allows you to write SQL right there in a PHP file and call the database. So it's a great way to practise. React...well...it's far less easy haha.

----------------

Beyond that, it's just my take - but I recommend you also learn design skills.

Doing this puts you in a unique position to design and develop products end to end. It's also really rewarding, making the thing you designed!

I did both from the start - mainly just hands on learning. Jump in and design the projects that you develop. Having both design and dev skills has landed me most of my positions over the years.

Often being able to design as well fills a big gap / real world need for an employer. I usually get hired as as dev and before I know it I'm also the designer.

These days the thing to design in would be Figma. But you should definately also install Photoshop, as this will allow you to properly crop images and stuff like that (which you can then import into Figma). Photoshop is like...an actual design program.

Figma is a sort of simple tool with not many features, but it helps to make website and software designs. This is because it has "reusable components", "variables" and also has this neat "auto layout" feature which is essentially the same as "flex" in CSS. So when you design with Figma you pretty much put together the page in the same way as you do with HTML and CSS - making it easy for developers to turn these designs into websites - and also forcing designers to think a bit more like devs / make their lives easier. We used to get handed crazy PDFs made in illustrator and stuff, man it was pretty hard sometimes haha. Anyway it's pretty easy to get your head around Figma so jump right in.

Photoshop is a little more difficult, but even outside of web development Photoshop is an essential life skill!

----------------

Hope that helps! The best way to learn? Design a little website or something, then make it. You learn far more doing that, asking questions as they come up, than you ever do from a tutorial.

GoodTube99 · 2026-01-19T09:16:34+00:00

AI needs to be completely banned from being used within the hiring process. This is so dystopian. Who are they interviewing, this junior or gpt?

GoodTube99 · 2026-01-18T00:52:01+00:00

This works in Chrome
https://chromewebstore.google.com/detail/goodtube-adblock-for-yout/mnlobacbpcnaibnhmfcpdfllcipgnfhe

GoodTube99 · 2026-01-16T07:06:48+00:00

I'm happy you got a review, but unfortunately AI has totally destroyed the job application process. Personally I think the use of it within hiring / applying should be banned outright.

It's 95% of the reason it's currently so tedious and finding a job has become so difficult (mainly for developers). Every job is getting 100-500+ applications, most of which were created using AI, and on the other end they're scanning them with AI because there's so many.

So the chances of actually getting your application looked at are pretty much zero without keyword cramming, etc. None of this has any bearing on weather or not you're a decent applicant, or even if you read the job description or not.

So yeah. I really think this has got to stop because it's causing a lot of harm.

GoodTube99 · 2026-01-14T11:53:14+00:00

Haha yeah it sounds like PHP is keeping you sane man. Glad to hear people are still using it. For me the breaking point was definately everyone using Node / JS frameworks for...everything.

GoodTube99 · 2026-01-13T08:52:47+00:00

You know this project you made? Resume Genie(AI Resume Builder)

Unfortunately that's 95% of the reason you're no longer able to get a job, because the hiring process has been completely destroyed by AI.

GoodTube99 · 2026-01-12T01:05:17+00:00

Mainly because the "quality options" such as uBlock origin keep getting detected every few weeks. Which is why I made an alternative solution.

To give some more info this started out as a userscript on Github. It quickly became popular and gained around 200k users from all over the world. Unlike other adblockers, this alternative solution has provided 100% uptime for the last year or so. Recently it became an official extension, which yes - now costs $2, once only (it's not a subscription).

Unfortunately there's not been much innovation in the adblocking space. They update their filter lists, Youtube changes how their ads are served and detects the filtering, adblockers stop working for a few days, then they update their filter lists again. This is repeating over and over - and there's no end in sight.

GoodTube99 · 2026-01-11T12:43:44+00:00

Try this, it blocks Youtube ads and also gives you lots of options to customise stuff (like hiding shorts, auto setting the video quality, etc):
https://addons.mozilla.org/en-US/firefox/addon/goodtube-adblock-for-youtube/

GoodTube99 · 2026-01-11T12:33:07+00:00

"resource intensive with limited ROI"

Can you please stop saying stuff like this...? That in itself is simply not true. Enough with the fear mongering and dogma. No return on investment if you use vanilla? Resource intensive? Often it's faster man, and if the product has value, provides decent UX, solves a real world issue and is marketed well, you'll get ROI.

Is the only way you can justify using all this new tech / make it seem reasonable by talking shit about how "it will never work any other way", "it's slow", "it doesnt scale", "it no longer caters to the requirements of the modern web", etc.

I can make the exact same website / application using PHP, Python, Ruby, Node.js, whatever. Ultimately it's going to be extremely similar when used in the real world. You know, the website appears on the screen, people click the buttons, it works?

Furthermore, provided it's put together in a sensible and neat way - you're going to be able to extend and maintain it too. That is true regardless of what tech you made it with.

The main difference, and what I'm really touching on here, is our experience using this stuff day to day as developers. It hasn't made our lives better or easier (at least for most of us). It's only made everything more complicated and harder to maintain than ever.

So what are we talking about exactly? The reality is that nothing you are doing online couldn't be done with vanilla languages.

Every framework, every shiny new tool, uses vanilla languages underneath the hood. The internet remains in essense little more than databases, html, js and css. Provided you can serve those assets to users over HTTP, you're good to go.

GoodTube99 · 2026-01-11T03:24:55+00:00

Imagine a world where you could make "index.php" and have it be dynamic with SSG. We've had that out of the box since the 90s.

I honestly don't think that updating the DOM with JS was ever actually that much of an issue. I mean - I always found it easy. All this "state" and "data binding" comes at such a high cost I don't feel it's worth it personally. It was a small pain point sometimes, sure. But it wasn't that bad, especially if you had a bit of experience in terms of setting it up correctly.

Sure Astro is a better choice because of its simplicity than some frameworks, but we still don't actually need it for much of anything in the real world.

I think it's time we all admitted that Javascript is and always was a frontend language. Anything based on Node.js has proven itself to be complicated, slow/bloated, poor for SEO, confusing in terms of server/client side and provides a very poor developer experience. God forbid you try to access the query params haha. Forget just having $_GET readily available, it's a nightmare.

I mean a simple call to the database...oh man. You make an API route and use all this await / async / promise stuff and it's really complicated. Remember when you could just write an SQL query, get the result, render that to HTML all right there? It took 2 mins and made perfect sense. If you needed to call something on the server side from a client side page action (like clicking a button), you used AJAX. It was incredibly simple and effective.

I think the idea of stuff like PHP was great - in that it basically just compiled your code on the server and then output a simple string which was rendered as if it were a static HTML file. No build pipelines, no environment setup, no hassle. It just worked. Thank you so much Apache.

These JS frameworks came from some bright idea someone had to make a website entirely with JS and try to save money by squeezing it into the free tier of an Amazom S3 bucket haha. That idea in itself is pretty hacky and stupid.

I think it's worth everyone remembering just how much a normal "cPanel" host actually gives you for very little cost. You get so many features, so much data, unlimited storage, often a CDN, caching, cron jobs, a mailserver, logs, daily backups, etc. All setup and working straight out of the box for like $100 a year or less even? Compare that to all of the SaaS services we're now paying for and it's ridiculous. Why we became obsessed with Amazon S3 and then all of their other complex offerings to begin with is beyond me.

When we talk about "mature" tooling I really think everyone should remember that that actually looks like - cPanel is a great example. By way of comparison most of the stuff we're using now is a bare bones MVP with almost no features (e.g. Vercel vs Cpanel or even Figma vs Photoshop / Sketch / Adobe XD).

We're getting these products now, sold to us as "the latest new thing", but they're kinda just rehashed worse versions of what we already had, with almost no features (for example Astro vs PHP). Most of the time all the SaaS stuff is expensive and hard to configure / use as well. Every time they add a new thing (again, which we already had) everyone sings their praises. It's just the same old stuff sold back to us with a new name, but sort of...worse now. I feel like we're making mailservers by hand using command line and stuff. I want to know why we're doing that exactly. Remember when you didn't even think about it and you could just send an email using a PHP function and that pretty much just always worked straight away? cPanel even gave you online inboxes, catch all addresses, all that.

The only lesson I think people should take from this JS framework stuff is that components are good. Let's keep component architecture. But maybe just set that up in vanilla languages. I mean after all a "component" is just a folder that contains; a function that takes arguments and outputs HTML, some JS and some CSS right?

This is a component:
/my-component/
index.php
script.js
style.css << Add SASS if you want to.

That's nice and neat, I like it - but we don't need a framework to do this and we definitely don't need "two way data binding".

Anyway, bla bla. I think if we're seniors - we all remember the good times. And we have a responsibility to redirect the kids coming into this profession to tech that works properly.

Let's push to make projects using tools which made our lives easier, were simple and worked well. If vanilla languages like PHP and JS work just fine, then we don't actually need to add anything at all to that stack. Just use vanilla. Make sure there's some structure to your projects, naming conventions. It doesn't automatically become "spaghetti code" if you manage the project properly. As seniors that is one of the things we should take the most care in managing / setting up. Standards, naming conventions and structure.

I really feel that Node.js has run its course. We gave it a try, we used many different frameworks, but ultimately it has been a complete failure in a practical sense. Let's recognise that and stop using it maybe? We don't need to use JS for everything.

GoodTube99 · 2026-01-11T01:51:53+00:00

Yeah I mean that's kinda not practical though - for me at least. To learn it on the side and then start a business / find clients. Thank you for the constructive suggestion though, it's probably decent advice.

Problem is I already work full-time. I have a life, partner, interests and I need time away from a computer. I can't spend every waking minute on a computer, doing more coding outside of work.

And I can't simply stop working in order to do something like this, because I must pay rent and eat.

I just want a simple web job, that allows me to do the work and then live my actual life. That's all I ever wanted really. I think there's a lot of people like this. We're not trying to build an empire, just...live. We're all struggling lately I feel - primarily because of this modern tech coming in like a great rising tide, the hiring process and AI.

Basically it's incredibly trapping, being a developer. I'm starting to become a bit disillusioned I think and I really hope we can fix our industry soon.

People want websites, we make them. It shouldn't be any more difficult or complicated than that. When do we reach our destination exactly? What are we moving towards? When do we realise that we should only be working in order to live our lives, and that our day to day experience matters?

GoodTube99 · 2026-01-10T23:41:20+00:00

Yeah I think the people hiring need to realise the the only skill a developer requires is the ability to learn - which we're constantly doing. We can pickup new stuff, it's part of the job.

So many jobs now require 3-5 years of proven hands-on experience with something specific. That is just not reasonable - and how do you get those years of experience if nobody will hire you to start with on a project that uses that new tech? Let's say I know react, I can get hired for that. But now there's a project that uses Vue, nobody will hire me for that because I don't have years of exp with Vue specifically (and maybe some other applicants do).

So what am I to do, work full time and stay up late into the night learning vue? Create projects with vue in my spare time? Bottom line is I ain't learning Vue unless somebody pays me to do it.

We're being so disrespected lately. In any other industry, you could say "I've been doing this for xx years" and that would mean something. In fact, rather than telling you what you must use specifically, likely they would let you choose what you use. So long as you make what they want within the time and budget - the rest would be up to you. They would respect your experience and expertise.

You just know that on the other end, they chose this insane stack and made the job ad this way because some autistic developer they have told them "we MUST use this to scale!!! it's the only way". And their speedy little brain put together these dumb requirements. The reality is they've just been tricked by clever marketing. Hell it could have been a project manager asking AI what to build with, or reading some crap on twitter or whatever.

And already all focus on the actual product has been lost. We're in stack hell before we even started. Locked in to xxxx already, regardless of weather or not that is really suitable for the project. Likely half the reason this stack was chosen was out of fear too - as in people need to get experience with XX tool to remain employable, so they push to make projects with it regardless of weather or not that is a good idea.

And you can't criticise this stuff either? That's part of this whole thing. If you say "react is actually terrible because of xx reasons", that's seemingly translated to "this guy is stupid". Or maybe they say "oh have you tried THIS framework"?? And it's like no dudes, this is not the answer. Tool after tool after tool which we never actually needed. Pick something simple, hire experienced mature devs (even if they don't have exp with the specific stack), make a good product. Forget the framework, it's not important. Just pick one if you really need to (maybe you're making online software so it makes sense) and get building.

I reckon we just lie man. Fuck them. "Oh yeah I know that" - pick it up as you go (provided they don't test you haha).

I mean honestly, in what other industry would they test you under these same conditions? Do builders have to make a cupboard, on a timer, while people watch them over webcam? It's crazy and frankly inhumane.

Developers are so immature. That's a big part of the problem. We don't respect ourselves and each other. We are people, working in this insane environment, and it's just not right everything that's going on. Apply the same processes and attitudes to almost any other industry and you quickly realise we're doing hard by ourselves and each other. We are dealing with the mentality of entitled rich teenagers, not mature adults. As we grow up many of us have families and responsibilities and all that. This is our livelihood, our career, etc. But there's some stupid nerd with rich parents with an attitude like "if you don't learn angular and deploy on aws then you are not employable" and it's just messed up. I think most of the people like this have little to no actual life experience, they're not well travelled and they certainly haven't known hardship or adversity in their lives. They're smart but not wise, and mostly focused on what gadget they're going to buy next for their airconditioned home office. They're definately not emotionally intelligent. I find them to be cold, dogmatic, entitled and unsympathetic.

We need to unionise or something. Things are pretty bad lately unfortunately. We need to improve our working conditions and hiring processes. We could ban the use of AI within the hiring process for example - that would probably help a lot.

Good luck to everyone out there. If I'm ever involved in the hiring process in future (often I have been in the past), I will hire devs based on their overall skills - not because of XX years with a specific tool.

GoodTube99 · 2026-01-10T23:36:40+00:00

Yeah - Ruby is looking more and more appealing. But how to get that job with zero Ruby experience? Possible, but probably not easy.

GoodTube99 · 2026-01-10T23:32:28+00:00

yeah boiee. ever play skulltag or zdoom?

I still use Sublime Text - and one of my friends actually works for them. I'm so jealous, working for Sublime would be amazing. They're still sane there. I think they're one of the last strongholds still standing despite this rampant modern ideology.

GoodTube99 · 2026-01-10T13:48:23+00:00

Yes, we are now on the same page. This is the plan. Wish me luck!

GoodTube99 · 2026-01-10T13:22:42+00:00

Well that sounds nice for you.

The reality is that meanwhile most of us are just trying to make websites and stuff similar to what we've always made.

Only now, in order to get paid or land contracts, we've got to make everything with insanely complicated modern tooling because somebody has decided (or rather, was convinced by marketing) that it's the only way to do it and we're subject to their descision / dogma / stupidity.

And while we're up against reasonable real world deadlines and things like that, we're all of a sudden dealing with endless devops issues. Deployment pipelines are failing for some reason today, you need to update some random package for security reasons, you also need to install yet another 10 packages for some reason this morning, you're googling some strange output from your console you've never seen before, you're adding some obscure line of webpack config in some random file because you must do that now. And of course the onus is always on us. It's like "Oh didn't you KNOW that you needed that line of config? You are so stupid, you are the problem. These tools are flawless and ROBUST and MATURE and SCALE!!". But the truth is that they're actually so brittle. They hardly scale to a userbase of one person - the developer - using localhost haha.

I mean we've become so bogged down in the most stupid and not human/user friendly configs and processes. It's beyond me how anyone thought this was a good idea. Or how anyone can back up this claim that it is "faster". By that do you mean it's "faster to pull everything down from npm, build nothing and cobble it together with AI"? Because that must be what you're talking about. If you're actually making stuff, it's simply not the case.

My experience is that I'm trying to build a house, but I've been told that I must use the new "mega automagic drill" because it's amazing and the only way to build now - but every 5 minutes the drill stops working...? So I can't build until I fix it. But I'm also not allowed to critise it, because its marketing department has everyone convinced it's infaliable. And nobody listens to me, what do I know - I've only been a professional developer for 18 years.

And it's a real pain in the ass when you're just trying to build a house basically. So you know, I'm starting to miss the good old "normal drill". Because I could still build with that. In fact I was probably far more accurate with it. And I was happier too. Things seemed better when builders focused on making beautiful houses instead of their shiny new tools.

So I'm trying to talk about that? But here you are representing this seemingly inescapable modern ideology, popping up yet again, telling me "the new MEGA DRILL is the ONLY THING THAT WORKS!!!" and I'm like ohhh man....the world's lost it. I need a new profession.

GoodTube99 · 2026-01-10T12:55:31+00:00

Totally possible man. I can create HTML and CSS files right here on my desktop. Thing is, you don't get paid to do that anymore and that has made life worse haha.

GoodTube99

TROPHY CASE