this post was submitted on 15 Aug 2023
189 points (98.5% liked)

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

54758 readers
333 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
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 35 points 1 year ago (3 children)

Concern trolling about the legality of discussing piracy is just a distraction. Their goal is to serve ads on their site, and removing all references to piracy is a step towards that.

[–] [email protected] 4 points 1 year ago (1 children)

How can they even serve ads if you dont use their website? Wouldnt other websites and apps need to implement ads for it to work?

[–] [email protected] 3 points 1 year ago (1 children)

However Meta decides to serve ads on Threads or Threads content. Whatever it takes, Threads will definitely do ads, as they are owned by an advertising company, but we don't really know how LemmyWorld will do ads until those ads are live.

[–] [email protected] 3 points 1 year ago (1 children)

Threads can only display ads on their app

if lemmy.world adds ads, people can just not use the lemmy.world website

As far as i know they cant force other apps to show ads

[–] [email protected] 2 points 1 year ago (1 children)

Threads can only display ads on their app

What is stopping them from adding ads to the website?

if lemmy.world adds ads, people can just not use the lemmy.world website

That's what I imagine happening, a few people can't stand it and leave or use uBlock, and the rest of the userbase gets served ads

As far as i know they cant force other apps to show ads

Not unless ads are a footer or something in post or comment content. That's an intellectual property gray area, I wonder what will happen.

[–] [email protected] 3 points 1 year ago

eugh, if they embedded them as posts, they'd be federating the ads as well.

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago) (1 children)

How do they expect to serve ads to people with that abysmal uptime that they have. They literally go down every single day, and that's probably just from one person from hexbear who's pissed at them, imagine how bad it's going to be after this, or if they even started running ads.

If they actually are planning on running ads I don't foresee it going very well for them. Maybe it will maybe they'll be financially successful but I bet they're probably also going to get defederated and therefore not platform successful.

[–] [email protected] 4 points 1 year ago (1 children)

How do they expect to serve ads to people with that abysmal uptime that they have.

The probably see it differently, that their uptime is limited by their funding, and additional revenue would help uptime.

Maybe it will maybe they'll be financially successful but I bet they're probably also going to get defederated and therefore not platform successful.

The current logic I've seen about why instances continue to federate with LemmyWorld is that they're "too big to fail", the same logic applied to Threads, and I don't see ads changing that. If Threads uses a more PR-friendly way of running ads when they inevitably do, maybe LemmyWorld will copy whatever ad-serving method that is.

[...] and that's probably just from one person from hexbear who's pissed at them, [...]

You probably saw someone else say this, rather than making it up yourself, but Hexbear does not DOS anyone, please don't repeat misinformation

[–] [email protected] 6 points 1 year ago (1 children)

The probably see it differently, that their uptime is limited by their funding, and additional revenue would help uptime.

They know that they are being DDoSed and have stated as much themselves, where are you getting this information, it sounds like you're arguing that the downtime is because of massive user registrations and not from an attack like they said themselves, even the activity charts shown are indicative of an intentional attack, rather than user load, a single sharp spike in requests or activity preceding downtime instead of a large hump.

The current logic I’ve seen about why instances continue to federate with LemmyWorld is that they’re “too big to fail”, the same logic applied to Threads, and I don’t see ads changing that. If Threads uses a more PR-friendly way of running ads when they inevitably do, maybe LemmyWorld will copy whatever ad-serving method that is.

Uh threads has been defederated preemtively by several fairly large instances due to concerns regarding what Meta's control over it and how it will affect federation. Lemmy.world hasn't done anything to suggest they would be a significant privacy and security risk to users, at least not yet, pushing ads to federated servers or collecting and selling user data would absolutely change that I guarantee it.

You probably saw someone else say this, rather than making it up yourself, but Hexbear does not DOS anyone, please don’t repeat misinformation

I did indeed hear it from others, don't worry you guys aren't the only suspects in that, though you can't really prove someone from as in registered to Hexbear isn't behind them. I'm not saying they are or aren't affiliated with Hexbear itself but one theory is that it's a person from hexbear and you can't prove that it isn't unless you know who's behind it. Honestly I heard from many admins (Lemmy.world and others) that Hexbear has a spam/trolling/brigading problem so it wouldn't surprise me if a problematic user there was behind it, or at least collaborating in the effort.

I didn't and won't go as far to accuse the instance owners themselves of being behind the attack but I won't say it isn't a user from Hexbear because nether you or I can prove that it isn't.

[–] [email protected] 4 points 1 year ago (1 children)

[...] it sounds like you're arguing that the downtime is because of massive user registrations and not from an attack like they said themselves [...]

I have no idea where their downtime is from. If it is DOS-related, though, they would protect against it using a DDOS protection service like CloudFlare, which costs $$$

Lemmy.world hasn't done anything to suggest they would be a significant privacy and security risk to users, at least not yet

They have, though. The LemmyWorld admins doxxed a user who they believed (incorrectly) to be Hexbear admin [email protected]. Source: https://lemmy.dbzer0.com/comment/1754850

[...], pushing ads to federated servers or collecting and selling user data would absolutely change that I guarantee it.

We'll see, but the larger they grow, the more permanent they get, and ads only affects that so much.

I didn't and won't go as far to accuse the instance owners themselves of being behind the attack but I won't say it isn't a user from Hexbear because nether you or I can prove that it isn't.

Hexbear is not more suspect than other instances, and there is no reason to name-drop Hexbear, alone, in particular. If they're being DOSed, then whoever is responsible is most likely involved in a community that has a culture of DOSing in general, like a Chan, maybe the same one that has actively been responsible for vandalizing Lemmy instances.

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

I have no idea where their downtime is from. If it is DOS-related, though, they would protect against it using a DDOS protection service like CloudFlare, which costs $$$

They currently do use Cloudflare actually, doesn't magically stop all forms of DDoS though (ever heard of SQL queries, some of them can take seconds to execute). Anyway I only said that because a big misconception by people is that Lemmy.world's uptime problem is caused by "the Reddit hug of death" as in user traffic and that it's a scaling issue, when it isn't.

They have, though. The LemmyWorld admins doxxed a user who they believed (incorrectly) to be Hexbear admin [email protected]. Source: https://lemmy.dbzer0.com/comment/1754850

That's pretty bad, though honestly it still pales in comparison to Facebook's awful history with collection and selling user data, though I guess how each instance views it. Maybe lemmy.ml (one of the biggest instances to ban threads) would use this to justify defederating from world (maybe I'll let them know about it and see what they say, I know they're certainly not going to go hunting for it on their own).

We’ll see, but the larger they grow, the more permanent they get, and ads only affects that so much.

I guess we'll have to wait and see how it pans out

Hexbear is not more suspect than other instances, and there is no reason to name-drop Hexbear, alone, in particular. If they’re being DOSed, then whoever is responsible is most likely involved in a community that has a culture of DOSing in general, like a Chan, maybe the same one that has actively been responsible for vandalizing Lemmy instances.

I have indeed seen many things that do elevate Hexbear on the list as of the possible origins of an attack, but there isn't any reason it couldn't also be from one of the chans or any instance that was defederated from them.

It does seem a bit weird to me though that you are strangely adamant about defending Hexbear, which does also make me slightly more suspicious, though that isn't definitive, many people will defend their instances for totally innocuous reasons. Anyway we're done with this, there was drama and concern (from several instances, not just world) and there's no point in arguing about it when we can't prove anything for certain here. Also this isn't exactly the place for a debate, this is c/piracy not a debate forum.

[–] [email protected] -2 points 1 year ago

They’re cryptofascists. Probably have had db0 in their crosshairs since forever.