this post was submitted on 16 Mar 2024
96 points (97.1% liked)

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

54669 readers
432 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
db0@lemmy.dbzer0.com
sunbrothersco@lemmy.dbzer0.com
dataprolet@lemmy.dbzer0.com
Flatworm7591@lemmy.dbzer0.com
RandomLegend@lemmy.dbzer0.com
96
DMCA takedown requests - how responsive? (lemmy.ml)
submitted 8 months ago by cerulean_blue@lemmy.ml to c/piracy@lemmy.dbzer0.com
22 comments fedilink hide all child comments
 

I'm in my first month of Usenet. I own several popular BluRay Movies but thought I'd save time ripping them manually and instead see what I could get off Usenet (NZBGeek + Eweka) now that my niece is visiting and needs entertainment.

I noticed a number of popular titles are consistently difficult to obtain ("aborted, cannot be completed"), even when live within only a few days, or even hours.

I assume this is a very vigilant DMCA takedown bot. How commonplace is this? And why does it only apply to some titles and not others?

Is it worth continuing with Usenet? I thought paying for content would ensure a certain "quality" of experience. So far, I'm a bit disappointed.

you are viewing a single comment's thread
view the rest of the comments
[–] GlitzyArmrest@lemmy.world 6 points 8 months ago (1 children)

That's not the problem here unfortunately. This is usually a complete take down on the server side, and has nothing to do with their location.

[–] PoliticallyIncorrect@lemmy.world -5 points 8 months ago

Personally I don't use Usenet, I thought its location or some type of blocking by the ISP could be related to the problem, I think you are right and it must be a problem in the server side.