You Should Know
YSK - for all the things that can make your life easier!
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules (interactive)
Rule 1- All posts must begin with YSK.
All posts must begin with YSK. If you're a Mastodon user, then include YSK after @youshouldknow. This is a community to share tips and tricks that will help you improve your life.
Rule 2- Your post body text must include the reason "Why" YSK:
**In your post's text body, you must include the reason "Why" YSK: It’s helpful for readability, and informs readers about the importance of the content. **
Rule 3- Do not seek mental, medical and professional help here.
Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.
Rule 4- No self promotion or upvote-farming of any kind.
That's it.
Rule 5- No baiting or sealioning or promoting an agenda.
Posts and comments which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.
Rule 6- Regarding non-YSK posts.
Provided it is about the community itself, you may post non-YSK posts using the [META] tag on your post title.
Rule 7- You can't harass or disturb other members.
If you harass or discriminate against any individual member, you will be removed.
If you are a member, sympathizer or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people and you were provably vocal about your hate, then you will be banned on sight.
For further explanation, clarification and feedback about this rule, you may follow this link.
Rule 8- All comments should try to stay relevant to their parent content.
Rule 9- Reposts from other platforms are not allowed.
Let everyone have their own content.
Rule 10- The majority of bots aren't allowed to participate here.
Unless included in our Whitelist for Bots, your bot will not be allowed to participate in this community. To have your bot whitelisted, please contact the moderators for a short review.
Rule 11- Posts must actually be true: Disiniformation, trolling, and being misleading will not be tolerated. Repeated or egregious attempts will earn you a ban. This also applies to filing reports: If you continually file false reports YOU WILL BE BANNED! We can see who reports what, and shenanigans will not be tolerated.
Partnered Communities:
You can view our partnered communities list by following this link. To partner with our community and be included, you are free to message the moderators or comment on a pinned post.
Community Moderation
For inquiry on becoming a moderator of this community, you may comment on the pinned post of the time, or simply shoot a message to the current moderators.
Credits
Our icon(masterpiece) was made by @clen15!
view the rest of the comments
So, adding the not clause works but only if the leopard is within the title row I believe. I can go to the leopards ate my face and see posts, but those with the block words are still being filtered. Since you're now our IT support for UBO and Regex do you by chance know if it's possible to connect the title and community rows into a UBO filter for the :not part?
I'm not sure I follow - the filter seems to work as-is to me. It allows posts on both the front page and the [email protected] to bypass the filter for me.
To be clear, it's not only applying to the title row - the
articletag it targets contains the entire post as it appears in the post feed, including the title, community name, the person who submitted it, the timestamp, etc. So if anything there contains a filtered or whitelisted word it should trigger the filter.I wouldn't have necessarily expected the whitelist filter to work directly on the leopards community page, since posts on community feeds don't include the community name, but it works anyways because, it seems, there's a hidden mod option in the HTML with the community name in it:
<div class="modal-body text-center align-middle text-body">Are you sure you want to transfer [email protected] to [email protected]?</div>I did not do extensive testing, but what I did was directly visit the leopards at my face community and could see there were articles being blocked within there. This filter leaves the separator lines of the posts that have been removed, and I was surprised to see articles blocked when viewing that community directly. Maybe I just messed up my regex, but I wanted to unblock anything with leopard/leopards in it even if it wasn't within that specific community just in case
Actually it seems to be a difference based on our instances - if I look at the community from infosec.pub then the bit of HTML I quoted above with the mod option isn't present, and there's no 'leopard', hidden or explicit, for the whitelist filter to find.
As a note, the (s)? on your leopard isn't needed - just 'leopard' will already match the 'leopard' part of 'leopards'
I don't know how to fix this currently, but I'll test out a bit more later to see if I can find anything that works well
I appreciate it... Obviously this is not critical :) and I appreciate your effort!
Hey! I'm pretty sure this one will work:
Where now we have three filters. If the community name matches the first regex, then nothing at all will be filtered out - and then the other two work the same as before. So any post that matches the blacklist regex will be filtered out unless it also matches the whitelist regex.
I chose to make the first regex
/.*?leopard.*?/ibecause my thinking is you may want to just copy/paste the other whitelist filter there for simplicity, but it might make more sense to do it like the others, like/leopardsatemyface|second community|third community|etc/i. The "title" of a community for the purpose of this filter should be whatever appears after /c/ in the URL, not counting the @lemmy.world (or whatever instance) part.Wow, nice work... I'll apply this and test it out and give feedback.
So, within the code snippet above, that line is not working with the
.*?leopard.*?but when I swapped in the community nameleopardsatemyfaceit seems to work as expected.Within the community I see trump posts, and within the main feed I do not. I need to see if a trump post from that community bleeds through to my main feed. I'm watching for that.
What happened with
.*?leopard.*?? It was still filtering Trump posts even from the community page? My own testing showed that variant working - I never actually even tested theleopardsatemyfacevariantTo be clear, this filter should allow for Trump posts that mention leopards or come from that community to show up on your main feed - that's what's desired here, right?
It also occurs to me that the
?on the.*?isn't necessary - even just.*leopard.*should work as expectedIt was not filtering trump from my main feed. Sorry I should have explained "not working" better in my reply :)
Hello again 🙂 I have a good feeling about this one.
It's doing basically the same thing as the last one but now instead of targeting an tag with the community-link attribute, which was basically just the first way I was able to find of identifying a community last time, it targets the title of the page itself, which seems like it should be a lot more reliable. This does mean using the literal
leopardsatemyface-type filter won't work since the title of the page is the community's user-friendly name: "Leopards Ate My Face" in this case.So as before it should block any posts which contain words from the blacklist, unless they also contain words from the whitelist - and now if the title of the page has any words from the whitelist (indicating we're on an allowed community page), it will block nothing at all. The blacklist and whitelist will apply to the post title, community name, and even the submitter's name - anything you can read and even some things you can't read.
I'll check it out for sure and get back to you! It is nice cleaning up my feeds. I use boost on my phone and while I can't limit filters like this it sure has cleaned up my feed there too.
I think I may see why. I didn't actually bother to check the main feed before, but it seems like it does have the a.community-link tag the new filter targets in every post - so if a post from leopardsatemyface ever shows up in the main feed, then the filter will think it's on that community page and fail to block any posts. But the filter should work fine so long as no posts from that community are currently on the main feed. This should be the case regardless of which regex is used - if it wasn't just a coincidence earlier I'll have to test around to figure out what happened with that.
It's a process making a good filter, I guess - I may look into a more reliable and narrower way to achieve the desired effect later on