Show HN: Feed Remover • Hacker News Board

Re: Show HN: Feed Remover

#31

Post by RiOuseR » Fri, Oct 20, 2023, 10:17 PM UTC

[dead]

Re: Show HN: Feed Remover

#32

Post by nomilk » Fri, Oct 20, 2023, 10:38 PM UTC

This is cool.

I use uBlock Origin to block GitHub's feed (I find it surprisingly distracting, and often right when I need to remain focused).

Re: Show HN: Feed Remover

#33

Post by Groxx » Fri, Oct 20, 2023, 10:49 PM UTC

chalsprhebaodu wrote: post #27

zukerpie wrote: post #25

Earlier quoted context omitted.

Added a quick domain check to avoid the issue that you've mentioned :)

I believe you could use a sub tree mutation observer instead of polling.

Yes, definitely use mutation observers. Far faster to react and doesn't require polling, they're better in essentially every way when things aren't changing many times per second.

Re: Show HN: Feed Remover

#34

Post by croes » Fri, Oct 20, 2023, 11:05 PM UTC

RheingoldRiver wrote: post #29

croes wrote: post #26

Earlier quoted context omitted.

There isn't really a special protection if you install a extension in developer mode. More the opposite because you have to totally trust the source. Web stores search for certain malware patterns and get at leat some.

You're not wrong, but in this case the total source code is like 30 lines long so it's not hard to verify what it's doing yourself

But that is independent from the way you install an extension.

You gain no security from an unpacked extension.

Re: Show HN: Feed Remover

#35

Post by rendall » Fri, Oct 20, 2023, 11:24 PM UTC

zukerpie wrote: post #23

jsf01 wrote: post #22

Cool! Just curious, why do you query 10 times per second for a feed? This seems kind of excessive and maybe a bit bad for battery life, especially since this could be running in several tabs at once.

This is just the straightforward idea of waiting for some element to appear on the website. But once the element is found, this thing stops. It won't stop for YouTube if you are on Facebook though but it's just a first implementation and it could actually be very easy to recognize the site. Thanks for the helpful suggestion!

I wrote an extension that did something similar for Twitter, back when Twitter had "So-and-so liked this" tweet, which was inevitably something awful. It's archived now, because it's no longer relevant. But you might find something useful in the code.

I tried polling, but it was against the Chrome extension guidelines at the time, so I used a "mutationObserver" on page load and then a "scrollListener". I don't remember if I ever tried an "intersectionObserver" but that might be worth looking at.

https://github.com/rendall/twitter-like-hider/blob/master/co...