This is an opportunity for any users, server admins, or interested third parties to ask anything they’d like to @nutomic and I about Lemmy. This includes its development and future, as well as wider issues relevant to the social media landscape today....
Disk space is definitely not an issue for us w/ postgres, or any text data really. The entire wikipedia english text data, is ~20GB. Images are the main disk-space concern for servers.
A backup of lemmy.ml’s DB is only ~1.8 GB currently, and that’s 3+ years of data.
We have no plans to move away from postgres, and lose all of its features and performance.
Just like any performance issue: server runners are doing great work to discover what’s crashing their instances, and those bubble up to lemmy, so people can do PRs to fix them.
There are certainly people who are only using lemmy, not because its FOSS, but because reddit has closed off API access (not realizing those are interconnected issues). To them it wouldn’t matter if lemmy’s source code is open or not.
Its not too big a concern for me, the fediverse isn’t going anywhere, and it’ll continue to grow, and be resilient to challenges.
Probably infinite scrolling in jerboa, as its a very harmful psychogical anti-pattern. Now that I’ve added it, people have been extremely resistent to my insistence that it should be done away with.
For obvious reasons, we don’t want to be involved in inter-server conflicts. Admins are free to run their servers however they see fit.
Would you think Ranked Choice voting for admins i.e. with the Schulze method - which Debian power-genius uses - integrated into the sites would mean that better community supported decisions can be made for both moderation as well as in comments/communities about stuff?
I don’t know how the debian one works (I’m also personally a fan of olympic score / range voting over ranked choice). Because of the possibility of weaknesses of these community-moderation proposals(people creating fake users to vote, and gaming them in hundreds of other ways I can’t think about) I’d rather not stress-test them in lemmy.
We don’t have a remind-me, but someone could implement it, it’d def be useful. I don’t even think there’s an open issue for that one yet.
I’m no legal expert, so I don’t know what updating the license entails, and why you wouldn’t as the creator be able to change the license freely as you see fit.
Image uploads are currently the biggest disk-space burden on server runners. We don’t have any limit hard-coded in lemmy’s back end, but admins are free to set hard limits in their nginx / server configs.
The biggest ones I can think of, are the re-write of the UI in rust / leptos, and notifications using unified push. Those will both be a ton of work, and its going to be hard to carve out time to complete them.
The back end has gone through plenty of refactors, and we place an emphasis on code maintenance, so its stayed up-to-date. The back-end and DB stack all seems future-proof so far, so I wouldn’t change anything.
While we had the ability to remove posts / comments early on, we didn’t have a system to report content. That was added much later, and has proved to be absolutely vital.
Thanks for this. These companies sometimes make it really simple for us, by showing what they don’t like. If they know what hurts their profits, then its likely in our best interest :)
Looks like its a subset of range / score voting, but only scores of [1-4] are allowed (as opposed to range voting which doesn’t specify the number of scores, but its usually 1-10 or 1-100), and it uses the median, instead of the average for some reason.
I love democracy (lemmy.ml)
We're the creators of Lemmy, Ask Us Anything. *Starts Monday, 7 Aug, 1500 CEST*
This is an opportunity for any users, server admins, or interested third parties to ask anything they’d like to @nutomic and I about Lemmy. This includes its development and future, as well as wider issues relevant to the social media landscape today....