0 Followers
0 Following
1 Posts

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

Lol I do the organic one all the time
It’s on the App Store now!!! apps.apple.com/app/id6450204299
‎Memmy for Lemmy

‎Memmy is built for the community, not for a profit: Fully open source and transparent; all code is available on GitHub. Completely funded by our community through donations. No advertising, no trackers - ever. Modern, sleek, and powerful: Highly performant with a slew of optimizations. A beautiful…

App Store

Another case for defederating from threads.net (Meta’s Twitter replacement that supports ActivtyPub)

https://lemmy.world/post/1076566

Another case for defederating from threads.net (Meta’s Twitter replacement that supports ActivtyPub) - Lemmy.world

There’s been a lot of talk about Meta’s new twitter clone called Threads because it will federate with other ActivityPub apps [https://techcrunch.com/2023/05/19/everything-we-know-about-instagrams-twitter-clone-due-this-summer/]. I’ve seen several posts about them possibly using the app as a way to embrace, extend, and extinguish [https://en.m.wikipedia.org/wiki/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.

The website definitely works, but it has weird issues with posts jumping around.

Also you can’t use gestures on the website, but you can on apps. Like swiping to comment/like, tapping to hide, etc). It just feels way smoother

That’s awesome! Thanks for hosting the server!

Reading more about how this works, sending out updates to each instance shouldn’t block the request from returning 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

activitypub-federation-rust/docs/09_sending_activities.md at main · LemmyNet/activitypub-federation-rust

High-level Rust library for the Activitypub protocol - activitypub-federation-rust/docs/09_sending_activities.md at main · LemmyNet/activitypub-federation-rust

GitHub

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

I’m still kinda new to lemmy, but it sounds like every post on all your communities get sent to your instance? And maybe every comment?

That’s probably fine for now, but when happens when one of the communities you follow gets a ton of users? I imagine you’d end up having to scale your self-hosted server even though it’s just you consuming the content?

That doesn’t seem sustainable. Not knocking your idea to self-host, more concerned with the scalability of lemmy

Why doesn’t it work between beehaw and lemmy world