Arviot lisäosalle Block Site
Block Site tekijä Ray
516 arviota
- Arvioitu 1/5kirjoittanut Oliver, kuusi päivää sittenDoesn't work anymore for me on Windows 11. It used to on Windows 10. Waste of time.
- Arvioitu 5/5kirjoittanut Davide, seitsemän päivää sittenGreat extension, thank you.
PS. It would be useful to have a "Note" field for each rule, so we can log some info / details :-) - Arvioitu 3/5kirjoittanut Firefox-käyttäjä 19538116, 18 päivää sitten
- Arvioitu 1/5kirjoittanut ᛊᛞDiesel_Wulfᛞᛊ, kuukausi sittenYeah, Random Sites Started Popping Up and it Wanted to "Disable WebExtensions"??? I Don't Care if this Add-on comes with a decent 3.9-Star Rating [That's a 78/100, a C+ Grade] (Out Of 512 Reviews) & 73,320 Users (as of 10/10/25) - if it opens stuff randomly over & over and asks that of me, I am concerned about my PC, You Never Can Be Too Careful These Days with Scams, Fraud, & Phising, afterall. An Excellent Idea, However, I'm Concerned About This Add-on's Authenticity & Security, & Will Not Be Running it On MY PC, for sure.
- Arvioitu 1/5kirjoittanut Firefox-käyttäjä 15554676, kuukausi sittenI need a solution to temporarily block access to a few opened tabs. But this add-on doesn't block tabs temporarily, it destroys them permanently.
- Arvioitu 5/5kirjoittanut g129512, kaksi kuukautta sittenThis is a very good plugin, but there's a bug I hope the author can fix. If you pause blocking for 5 minutes, then **close the browser**, and reopen it after 5 minutes, you'll notice that the block hasn't automatically resumed and you'll need to manually click "Resume Block" to restore it. I often find myself browsing a webpage after pausing for 5 minutes, then closing the browser. When I reopen it, the plugin is permanently no function unless I manually click "Resume Block."
- Arvioitu 5/5kirjoittanut Firefox-käyttäjä 19143823, kaksi kuukautta sitten
- Arvioitu 5/5kirjoittanut Linh, kaksi kuukautta sitten
- Arvioitu 5/5kirjoittanut Rin, kaksi kuukautta sittenI normally don't rate the expansion, but this site block extension is great. No fancy function, nor subscription junk. It is simple, and it gets job done. I really appreciate it.
- Arvioitu 1/5kirjoittanut Sniggling, kaksi kuukautta sittenWorked for exactly one day, the next day it stopped working entirely. Tried reinstalling it, using regex, changing configurations, and nothing.
- Arvioitu 4/5kirjoittanut poker lover, kolme kuukautta sittenThe addon works as intended for my limited use of blocking youtube.com. My problem is that I use youtube music and this extension blocks that website too, I have to disable blocking or remove youtube.com as long as I am listening to music. I am very addicted to watching youtube and this displeases me. I don't want to try reverse blocking as it restricts too much of my browsing.
- Arvioitu 1/5kirjoittanut Cyberknight, kolme kuukautta sittenDidn't work... Elaborating, it didn't work after adding a regex rule (maybe I should have tried harder, but I kind of quit after half a dozen tries, as the extension seems to add characters to the beginning and the ending of all inserted rules, regardless of them being necessary or not.) Even if it had worked, it'd be amazingly cumbersome to manage the rules, as, after added, they cannot be edited, just removed (there's an option to load a local text file with the rules, one per line, but then again, to edit one single rule, it requires the clicking on a purge button that removes all rules, then loading the file again...) It could simply have the rules in a textarea for free editing, like other blockers do, which would make it much easier to manage.
- Arvioitu 5/5kirjoittanut Firefox-käyttäjä 19126235, kolme kuukautta sittenthis is such a good extension dont know why people gave the bad ratings works completely fine and it does so much for free! its a really good extension for blocking websites would reccomend!
- Arvioitu 5/5kirjoittanut Firefox-käyttäjä 19203653, kolme kuukautta sitten
- Arvioitu 5/5kirjoittanut Firefox-käyttäjä 18919299, neljä kuukautta sittenIt's not just in private mode. Since... Few months (?) ago is not working animore, both in Chrome and in Firefox; private or not. The site isn't blocked at all and still appears complete instead the gray-background message of the extension informing about blocked site.
Anybody with the same issue or knows how to fix it or why it happens? I like so much this add-on and don't want to search another one...
I guess that needs an update since last is from later 2024 and some of you said about same issue since navigators' updates. Thanks and sorry for my english.
EDIT: I don't know why last updated appeared from 2024. I readed again the last reviews and see it was indeed updated again few time ago, when started failing. I searched updates, applied it and now works again like before. Thanks a lot. - Arvioitu 5/5kirjoittanut Firefox-käyttäjä 19160456, neljä kuukautta sittenAs mentioned by a few other reviews, a Firefox update caused the extension to not work in private mode. The extension was updated in under a week to resolve the issue. Works well, active bug fixes, open source. Highly recommend.
- Arvioitu 5/5kirjoittanut Jesus, neljä kuukautta sittenvery good tool to add additional security to your browser
- Arvioitu 5/5kirjoittanut Alejandro, neljä kuukautta sitten
- Arvioitu 1/5kirjoittanut rozsiiii, neljä kuukautta sitten
- Arvioitu 1/5kirjoittanut jijijijijijijij, neljä kuukautta sittenThe new update stopped allowing this extension to run in private mode. please fix, otherwise than this I give it 5 stars.
- Arvioitu 5/5kirjoittanut Firefox-käyttäjä 19122072, neljä kuukautta sittenSimple and useful, but a few days ago, it stopped working in private windows. 5 star if this issue is fixed. (edit, this issue has been fixed)
- Arvioitu 5/5kirjoittanut DuskVrai, neljä kuukautta sitten
- Arvioitu 3/5kirjoittanut Dizzy, neljä kuukautta sittenit's great! When it works. At first, I was wondering if it was my regexp that was the issue; I tried to block sites without regex and... it still didn't work. However, sometimes it does work?? It's very strange and I wish I knew what caused this so that I could talk about it on GitHub...