this post was submitted on 13 Nov 2024
23 points (100.0% liked)

Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

54670 readers
341 users here now

⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.

Rules • Full Version

1. Posts must be related to the discussion of digital piracy

2. Don't request invites, trade, sell, or self-promote

3. Don't request or link to specific pirated titles, including DMs

4. Don't submit low-quality posts, be entitled, or harass others



Loot, Pillage, & Plunder

📜 c/Piracy Wiki (Community Edition):


💰 Please help cover server costs.

Ko-Fi Liberapay
Ko-fi Liberapay

founded 1 year ago
MODERATORS
 

I've told qbit to exclude those files and many other extensions from someone's helpful comment on here previously, but the stack keeps on grabbing and seeding them, which the latter I'm a little unhappy about sharing malware.

While all the boxes on my network have no sign of Windows to get exploited it does worry me about another family members arrr stack because there is a Windows laptop down there, but thankfully not used for media consumption.

Help?


edit: big thanks to kiszkot@feddit.nu for pointing me in line separators instead of comma separated exclusions!

you are viewing a single comment's thread
view the rest of the comments
[–] kiszkot@feddit.nu 16 points 1 week ago (1 children)

According to some posts online you should use pattern matching to exclude filetypes. "*.ink" should match any file ending in "ink". Exclusions should be separated by a newline.

[–] ladfrombrad 8 points 1 week ago

Separated by a newline

You brilliant person got it in one! Love you 😘

https://files.catbox.moe/tda0my.jpg

Now I haven't tested which of the line separated ones blocked it, but the wildcard *.lnk didn't work when they were comma separated but do when line separated.

Again, 👌