thanks, but sorry, that wasn’t the question.
I’m perfectly aware of the user end principle, but I’m not so sure about the technical backend.
where is the data of remote instances stored?
if this is synced to the local instance, than small servers would need to mirror remote content.
but I guess, I’ll check the ActivityPub and Lemmy Doc/Code
thanks for the input!
I just haven’t figured out, what happens if users on my small instance would join larger communities in other instances. does the small instance needs to mirror or route the traffic to the other instance, or is this only done through links and on the small instance is really only the stuff local users generated?
did the temptation win? ;-)
if you start a fork, I guess currently there are quite some people to contribute/join the effort
I’m holding myself back a bit, because daily work doesn’t leave me with much free time at the moment - with not much change in the near future…
three idea was more, how the single instances can finance themselves. network traffic and storage need to be paid somehow.
I’m not sure how the federated system works exactly and how much a small instance would need to mirror or pipe through, when the users subscribe to large communities on another instance.
so I was wondering, how instances with a small user base can keep up financially - bigger ones can probably live of donations. If a small instance doesn’t need much space or traffic, because subscriptions on remote instances are directly handled on the remote instance, than this is probably no problem.
I’m thinking of setting up my own small server and am not sure what exactly to expect…
it’s absolutely awesome here! :-D
I feel like being part of the internet of my youth again.
yeah, but then you need someone on the outside to open 18 (!) bolts, before you can exit. no way to open from the inside. so you’ll probably suffocate anyway.
how this design got through…