Repository navigation
Trouble with complicated rules #700
|
Hi, Usually the recommended way of doing this would be making two separate block sets, but seems like that won't really work with time limits. What I'm trying to do is set a time limit for the main parts of instagram that'd be an issue, while keeping the rest open. So I'd want to block: With exceptions for: So to summarize basically put everything on a timer except stories, profile pages, and posts opened from a profile page. Best I've managed so far is this: +instagram.com//reels It's pretty close, but profiles are still blocked, and posts are unblocked regardless of where it's opened from. To have the main page blocked but unblock profiles idk how you'd solve that, since profile URLs have no unique identifiers and are just instagram.com/[username]. If you only wanted to block the main page it'd be fine, block instagram.com but put instagram.com/* as an exception. But in my case none of the other block rules seem to work if I do that. Would really want some hierarchy where for example an exception would override any rules below it but not above. One thing to mention is firefox doesn't seem to be great with referrers. If opened directly the referrer is null, and if opened from a search it always gives the search engine link as referrer even after navigating to a subpage. Is there any known way that a user can change that somehow, could that be done with an user script perhaps? Otherwise if there's nothing that can be done there it wouldn't be a huge deal if /p/ and /reel/ are unblocked everywhere, as long as there's some way to unblock profile pages. Hope this is clear and that there's some solution, or if there's another extension that'd work better for me? |
Replies: 1 comment
|
Yes, that's complicated. 😄 Everything you want is doable, except for the "posts opened from a profile page" part. The reason for the latter is that since 2020-21, browsers only report the referring site, not the referring page. Note that any URL that begins with the specified domain/path will be blocked. So Selecting the exact pages you want can be done with a regular expression (see under Advanced Options). Something like this should do it:
This should apply the time limit only to instagram.com, instagram.com/explore/, and instagram.com/reels/. Try it and let me know if it works. Note that if you use a regular expression, it will override anything in your block list. |
Yes, that's complicated. 😄
Everything you want is doable, except for the "posts opened from a profile page" part. The reason for the latter is that since 2020-21, browsers only report the referring site, not the referring page.
Note that any URL that begins with the specified domain/path will be blocked. So
instagram.comwill automatically blockinstagram.com/reels/etc. The*at the end of an entry will be redundant for the same reason.Selecting the exact pages you want can be done with a regular expression (see under Advanced Options). Something like this should do it:
^https?:\/\/(www\.)?instagram\.com(\/(explore|reels)\/)?$This should apply the time limit only to instagram.com, inst…