My laptop is on Manjaro and has been running flawlessly for years …such a great experience with gnome 40+
My desktop is also on Manjaro, and things could not be more different. No Wayland, no animations in the gnome desktop, visual glitches since the last update …guess it doesn’t play well with Nvidia drivers. Anyone managing something decent with gnome+Nvidia?
I am typing this on my Pixel 7 (recommend me a Lemmy app please :D )
I had a 4a before this, I liked the finger print reader way better on the 4a but other than that my 7 is better, its the best and most expensive phone i’ve ever owned.
Before the 4a I had some random Honor and Huawei phones and I used to upgrade phones almost yearly which I felt was kinda depressing so I figured I should “invest” in a phone I could use for ~3 years.
The only Apple product i’ve had was some kind of iPod that I asked my uncle to copy cd’s onto, it was kinda cool i guess.
Tears of the Kingdom. I’m going to be here for awhile, but this game has made me want to play some other Switch games in my collection that I’ve been putting off, like Xenoblade Chronicles.
One question I still have is how quickly posts and comments propagate across the Fediverse. How can I be sure the comment I’m writing actually shows up across other instances, and how long after I write it does it take on average to show up other places?
For instance, when I look at the list of comments on this thread sorted by both Hot and New, directly on Lemmy.ml versus on my home instance of Lemmy.pt, I don’t see the same set of comments. Not all of the ones from Lemmy.ml appear to have made it over to my instance. Is there some sort of eventual consistency mechanism in the system?
A small cloud server + a domain name costs less than a Netflix subscription. The developers have taken care to package lemmy in ways that are relatively straight forward to deploy, so a dedicated person with a small amount of experience can have an instance up and running in an evening. As long as a few percentage of users are willing to pay a netflix subscription to keep a server running, the financial burden would be spread.
I think this underestimates how users will naturally gravitate towards more centralized instances, or they’ll give up because the bigger instances are closed. Someone’s gotta pay for it, and it’s going to cost more than a Netflix subscription. Servers aren’t cheap.
This also ignores that the system isn’t horizontally scalable at all, so scaling up gets even more expensive
I think this underestimates how users will naturally gravitate towards more centralized instances, or they’ll give up because the bigger instances are closed.
(This is purely my personal opinion, of course!) In the scenario in which a few large instances dominate, the idea of the fediverse failed. One may estimate the likelyhood of success or failure given how they expect humans to behave, but in the end experiment beats theory. I think that for the fediverse to work a significant cultural shift has to occur, but I don’t think that it is an impossible shift. I would like the fediverse to succeed, and so I choose to take part in the experiment.
This also ignores that the system isn’t horizontally scalable at all, so scaling up gets even more expensive
Yes, that might cause some serious issues. The project is still in an early-development phase, and I don’t understand the technical aspects well enough yet to be able to identify whether there is obviously a fundamentally invincible barrier when it comes to scalability. My optimistic hope is that the developers are able to optimize horizontal scalability fast enough to meet the demand for scale. If it turns out to be impossible to scale, then only rich enough parties would be able to have viable instances, and that could be a reason for failure.
This is what I think, but if anyone understands it differently please correct me.
Vertical scalability refers to scaling within a single instance. More users join and they post more content, increasing the amount of disk space needed to hold that memory, network bandwidth to handle many users downloading comments and images at once, and processing power.
Horizontal scaling refers to the lemmyverse growing because of the addition of new instances. The problem in this form of scaling is due to the resources that an instance has to use due to its interactions with other instances. So, you may create a small instance without a lot of users, but the instance might still need a lot of resources if it attempts to retrieve a lot of information (posts, comments, user information, etc) from the other larger instances. For example, at some point a community in lemmy.ml might be so popular that subscribing to that community from a small instance would be too much of a burden on the smaller instance because of the amount of memory required to save the constant stream of new posts. The horizontal scaling is a problem when the lemmyverse becomes so large that a machine with only a small amount of resources is no longer able to be part of the lemmyverse because its memory gets filled up in a few hours or days.
Five posts a day isn’t bad as you put it. You’ve been for years overstimulated by Reddit’s abundant content. Many of us have been contributing to lemmy perfectly fine; we see reccurent usernames and profile pictures, we grow compassionate and sincere with each others thanks to this familiarity.
Not everything should keep on mindlessly growing. Not growing fast enough isn’t a problem, yet our modern, capitalist lifestyles make it seem so. That said, I am not against lemmy’s ongoing growth per se.
Thanks for the post! Been thinking of spinning my own instance as well because my Hetzner server doesn’t get used that much. Though then I would have to actually make sure it stays up and that I won’t just dip out one day lol.
Lemmy is Federated. You don’t distribute hosting, you have the federation servers communicate with each other.
The best thing you can do is spin up your own instance and convince your friends to use it. That way big communities like lemmy.ml/c/asklemmy only has to send your server one update for a post for all your users to view, rather than sending that update to 20 browsers themselves.
So your lemmy.mo_ztt.com instance could serve the one copy of it’s content to your dozen or so users which takes load off of the “main” instance.
“Instance operators” as you termed it… could be literally anyone. You can host is on a raspberry pi for a handful of users easily. This would lighten the loads on the major “Instance operators”.
What’s the right term for what I’m calling an “instance operator”? I realize that anyone could be one, I just need some language to use to distinguish the people who are from the people who aren’t.
kbin.life
Top