1
Priceless by Jonau (pricefield.org)
1
kiss by suerer (pricefield.org)
1
1
1
Max and Chloe by kgmtk (pricefield.org)
1
1
yuri by snooompy (pricefield.org)
1
1
1
1
1
[-] b3nsn0w@pricefield.org 68 points 7 months ago

this has to be illegal.

like, no, seriously. i'm not a lawyer but i was working on a (since failed) startup in 2018 and distinctly remember how much headache the gdpr caused. literally one of the main things was that you cannot coerce users into consenting to data processing, or make features conditional to them. the gdpr makes a distinction between processing you do to perform a contract (that's why no one asks for your consent for processing your email address to log you in, that's implied) and processing you do for other reasons, which require user consent (that's why everyone asks if they can spam you on the same email -- it doesn't matter that your email address is already on their server, processing it for marketing reasons requires consent of the data subject). opting into these kinds of processing needs to be granular, if it's not they lose the validity of your consent.

i seriously hope facebook gets slapped so hard over this that no one ever thinks about doing this again. "paying with your data" should never be a thing in any society that calls itself civilized.

[-] b3nsn0w@pricefield.org 28 points 11 months ago

There was a man at CERN once who was sick of questions. His name was Tim-Berners Lee.

[-] b3nsn0w@pricefield.org 29 points 11 months ago

I thought the most dangerous one was president, at an 18% fatality rate (8 out of 45 so far)

[-] b3nsn0w@pricefield.org 40 points 11 months ago

actually, do yeet the baby if you have an application with different needs. for example, if you want to play a game, you're better off yeeting 60 babies a second and just hope that whoever is on the side catches enough of them to get a smooth stream of babies, than making sure every baby is handed gently to the next person and get the whole line clogged up the moment anything disrupts it. if you just use the yeetomatic 3000 you're always getting fresh babies on the other end, a few might just be dropped in the process

[-] b3nsn0w@pricefield.org 42 points 11 months ago

lmfao, frickin seriously? you're gonna build up an instance where the domain is part of all of your users' identities and you're not even gonna spend the $10/yr to keep that solid? with how much time goes into running a lemmy instance and not getting overrun by bots, that's an absolutely ridiculous assignment of resources

[-] b3nsn0w@pricefield.org 46 points 11 months ago

shows the actual capacity reddit has to operate without the help of their experienced moderators who they managed to collectively piss off

[-] b3nsn0w@pricefield.org 91 points 11 months ago

meanwhile, the eu: well we can't jail a company, so fuck you, if you break the gdpr you're liable for 4% of your yearly revenue (not profit, that can be cheated)

fines do work but only if they're relative to how much you make

[-] b3nsn0w@pricefield.org 34 points 1 year ago

yep, it's important that we have this capability, but it's also nice that unlike other platforms that do their best to lock you in, lemmy actively pushes you toward a safer alternative

[-] b3nsn0w@pricefield.org 227 points 1 year ago* (last edited 1 year ago)

yeah, the difference is pretty stark:

  • lemmy: we'll give you a way to dm anyone on site, but please don't use that, if you set up an app on this other open source service we're not affiliated with (which is basically an encrypted discord) we'll do our best to make it as seamless for you as possible. we'll keep warning you for your own privacy.
  • meta/facebook: aggressively keeps you on-platform for spying purposes; literally killed xmpp a decade ago and they'll fuckin do it again (if we let them)

They trust me. Dumb fucks.

- Mark Zuckerberg

(yes it sounds like satire but that's a real quote)

[-] b3nsn0w@pricefield.org 24 points 1 year ago

i don't think there's an api endpoint for that yet. the database definitely stores it, it would be doable, but it's not implemented yet in the backend

[-] b3nsn0w@pricefield.org 27 points 1 year ago

Yeah, it's actually a welcome change that they're federating. However, the way they killed off the last federation we had with XMPP was through the EEE model -- they first acted friendly, joined our federation, then they ensured their client would be the best featured, capturing a majority of the people in their user base, and after that they defederated and the community collapsed in their favor. People on non-proprietary solutions had to switch to the proprietary one.

To avoid this, we need to defederate while we're still ahead. I'd personally draw the line at 25%, but the point is just having it significantly less than 50%. If they defederate before they reach a majority, the community will collapse in our favor, and people with proprietary accounts will be the ones forced to come over here. Worst case, we'll just exist beside each other as competitors, and in the best case we'll snuff them out.

We need to be willing to do this to them, because they absolutely will do this to us. Threads is developed by the same Meta who helped kill XMPP a decade ago. (And "helped" only because the main culprit was Google -- regardless, they're not our friends.)

[-] b3nsn0w@pricefield.org 79 points 1 year ago

yeah, honestly, i think the optimism is somewhat misplaced. we must ensure that proprietary solutions, like threads, are not the main way people interact with the fediverse. it's better to defederate early and continue in smaller communities while we still can, than to let them seep into every community we have, only for them to pull the plug later and lock everyone into threads.

i think it's alright to federate with them a little bit, but we cannot allow threads to become the most popular fediverse app

view more: next ›

b3nsn0w

joined 1 year ago
MODERATOR OF