myersguy

I was mostly just poking fun. Right now my media is only consumed at one location, so I primarily use Kodi on an Asus mini PC. I will likely keep Kodi as a client, and move to Jellyfin as a server in the future to allow for more clients.

EDIT: I understand downvoting my original tongue in cheek comment. Downvoting my response to someone's follow up question is pretty odd though. Especially the guy signing in with multiple accounts to do so 🤨

Mostly just poking fun. It came off as an odd flex (laughing at people who choose to pay for media) while also repping software that has features locked behind a paid tier (a subscription, at that)

Lol using closed source apps with paid tiers hiding important features for media 🤣

I understand why it had to happen, but I miss seeing the old name everywhere ☹️

Your opinion?

Our opinion.

So happy to have a new home

Really hope he gets all of his back problems under control. I could go for another five or ten years of Lewis fights.

Love Wonderboy, and am glad to see he is looking out for himself.

I've seen this happening a lot, so I would assume there are some issues federating comments.

Wow, that is surprisingly not bad given the size of the instance!

Interesting indeed. I spent some time combing through the DB and pictrs folder to try to figure it out, but I'm at a loss so far.

Again, my knowledge of the Lemmy codebase is very small, and we could possibly host the monolith in microservices style. The point I am making is this (when it comes to scaling monolith vs microservices):

If the federation logic were split out, we could configure it to run on super tiny docker instances on Google Cloud or AWS. Any time we needed it to, it would autoscale to handle the traffic. The configuration for these dockers could be super minimal memory, no storage, and multiple weak CPU cores. This would be super affordable while still being able to handle as much traffic from federation as we ask it to. One of the cool things with Google Cloud Run is that it handles load balancing between docker containers for you (just point the federation traffic at the necessary URL)

IF Lemmy has things like background services, scheduled tasks, etc, this would significantly muddy the water (we would need each service to be able to handle being run on a multitude of instances, or we would need to be able to disable each one instance by instance). And if we just scaled by spinning up more instances of Lemmy, we would also need to ensure that only federation traffic is heading to the weaker instances that we spun up for such purpose, or we would need to ensure that each spun up instance has enough resources to handle federation traffic along with the main application.

I feel like I need to state once more: I don't necessarily think Lemmy needs to move to microservices. Only that scaling monolith vs microservices is not necessarily the same.