The dominance of cat content VS dog content on Lemmy reflects its current techie userbase by LargeHardonCollider in c/showerthoughts@lemmy.world
[-] LargeHardonCollider@lemmy.world 1 points 1 year ago

I don’t think he’s saying they’re better, he’s saying it’s a preference thing and he prefers dogs because you can bond more with them.

Cats are way easier to take care of because they don’t need as much attention, which makes them better for a lot of people

YSK: Lemmy All Third Party Clients List (Android/iPhone/Web) with status of that apps! by LargeHardonCollider in c/youshouldknow@lemmy.world
74
Another case for defederating from threads.net (Meta’s Twitter replacement that supports ActivtyPub) (lemmy.world)
submitted 1 year ago by LargeHardonCollider@lemmy.world to c/technology@lemmy.world
22 comments fedilink

There’s been a lot of talk about Meta’s new twitter clone called Threads because it will federate with other ActivityPub apps. I’ve seen several posts about them possibly using the app as a way to embrace, extend, and extinguish ActivityPub.

Another more immediate concern I have is that Meta will now be able to harvest data from users of other ActivityPub social networks like Lemmy and Mastodon. If Alice on Threads follows Bob on Mastodon for example, that means Bob’s mastodon instance will send information about all of Bob’s posts and everyone who interacts with them to Meta so that Alice can see it.

This is a concern specifically with Meta and other big tech companies running ActivityPub-enabled servers, because their primary motive is to harvest user data to use for advertising. The scariest part to me is that users on networks like Mastodon specifically migrated to Mastodon to get away from big tech, and Meta is still able to harvest their data with Threads.

These are the privacy permissions that you grant for Meta's new twitter competitor by LargeHardonCollider in c/technology@lemmy.world
[-] LargeHardonCollider@lemmy.world 1 points 1 year ago

Another really big concern I have is that activity pub by definition shares all your posts with any instance that hosts your followers. So if you have a mastodon follower on FB’s activity pub/twitter replica, FB automatically gets your data even though you don’t use it

The type of things they get are

  1. Your profile
  2. Whatever you post
  3. Who interacts with your posts
Workaround for the performance issue with posting in large communities by LargeHardonCollider in c/lemmyworld@lemmy.world
[-] LargeHardonCollider@lemmy.world 1 points 1 year ago* (last edited 1 year ago)

Reading more about how this works, sending out updates to each instance shouldn’t block the request from returning unless you have a config flag set to debug source.

It might be due to poorly optimized database queries. Check out this issue for more info. Sounds like there are problems with updating the rank of posts and probably comments too

Workaround for the performance issue with posting in large communities by LargeHardonCollider in c/lemmyworld@lemmy.world
[-] LargeHardonCollider@lemmy.world 0 points 1 year ago

Is the slowdown that it the instance has to send out updates about the comment to every other instance before returning a successful response? If so, is anyone working on moving this to an async queue?

Sending out updates seems like something that’s fine being eventually consistent

LargeHardonCollider

joined 1 year ago