It's a hypnic jerk.
They'd no single agreed on cause, but they happen during the transition from wakefulness to sleep.
What's the current setup, if you don't mind me asking?
Asus ZenFone 8.
I love it, it's a nice bit of kit, and the few gimmicks it has are useful: scheduled charging for better battery life, digital well being stuff to stop me being glued to my phone.
Battery would be a problem for a super power user, but lasts me all day with commuting, reading the web etc. Camera is not on a par with flagships but I rarely take pictures.
Prior to this I had a Huawei until the battery died on me. I upgrade when I have to, I hate consumer upgrade cycles.
I have zero android ecosystem products.
I'm Android/Linux all the way unless work force me to use a Mac, which happens periodically, as part of the great cycle of life.
Databases are also the hardest bit to horizontally scale. Web servers are easy cos they're (usually) stateless . It's state that's hard to scale out.
Set it up and I'll sub.
https://en.m.wikipedia.org/wiki/Eternal_September
There used to be an influx of young students to the internet every September because most people used it at university for the first time. That changed when home internet became more widespread leading to the eternal September.
In the older, better days, we used kill files, and our choice of platform was eventually overrun by spam.
It'd be slow, though, like a lot of the darknet protocols, and would mean that whether or not your post is visible depends on which users you're connected to. I think the usability problems would likely rule it out.
P2P works great for filesharing because you're reading small numbers of large things, so if each thing takes a minute or two to start, that's fine. It would suck for reading the memes community on a social network cos you need to read many small things, and if they don't load quickly the experience is ruined.
Ja, but you need an index for each thread, some kind of time partitioned thread index for each community, same for all.
Then you need to query all comments or posts by user, so that's another index, then you need some way of querying for hot, or controversial or what have you.
It's doable, but fiddly. Tempted to have a go though!
Seems like storage is the cost prohibitive part. Search is going to be difficult, too. I wonder whether the model there might be community supported shared services. A bunch of instances could jointly run an elasticsearch cluster or Algolia instance and charge for API access to cover costs.
Some things can go faster if you add more workers, some things can only go faster if you make the workers bigger or faster .
If you're tidying a garden you can get it all done more quickly, and tackle bigger gardens, by getting your friends to help. That's horizontal scaling.
If you need to get a parcel from your house to Burkina Faso the only way to do that more quickly is to use a bigger, faster machine. That's vertical scaling.
The way Lemmy is designed right now (says the op, I don't know the detail) you can only support more users by making the server bigger and more expensive, not by using lots of smaller servers.
Edit: note that Lemmy as a whole scales horizontally: more instances == more users, but each instance has to scale vertically.
I think they meant they've seen one Russian troll on Lemmy already, not that skidface is a Russian troll.
I ... Have to assume so, anyway