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

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

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 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

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?