This is a chance for any users, admins, or developers to ask anything they’d like to myself, @[email protected] , SleeplessOne , or @[email protected] about Lemmy, its future, and wider issues about the social media landscape today.
NLNet Funding
First of all some good news: We are currently applying for new funding from NLnet and have reached the second round. If it gets approved then @[email protected] and SleeplessOne will work on the paid milestones, while @dessalines and @nutomic will keep being funded by direct user donations. This will increase the number of paid Lemmy developers to four and allow for faster development.
You can see a preliminary draft for the milestones. This can give you a general idea what the development priorities will be over the next year or so. However the exact details will almost certainly change until the application process is finalized.
Development Update
@ismailkarsli added a community statistic for number of local subscribers.
@jmcharter added a view for denied Registration Applications.
@dullbananas made various improvements to database code, like batching insertions for better performance, SQL comments and support for backwards pagination.
@SleeplessOne1917 made a change that besides admins also allows community moderators to see who voted on posts. Additionally he made improvements to the 2FA modal and made it more obvious when a community is locked.
@nutomic completed the implementation of local only communities, which don’t federate and can only be seen by authenticated users. Additionally he finished the image proxy feature, which user IPs being exposed to external servers via embedded images. Admin purges of content are now federated. He also made a change which reduces the problem of instances being marked as dead.
@dessalines has been adding moderation abilities to Jerboa, including bans, locks, removes, featured posts, and vote viewing.
In other news there will soon be a security audit of the Lemmy federation code, thanks to Radically Open Security and NLnet.
Support development
@dessalines and @nutomic are working full-time on Lemmy to integrate community contributions, fix bugs, optimize performance and much more. This work is funded exclusively through donations.
If you like using Lemmy, and want to make sure that we will always be available to work full time building it, consider donating to support its development. Recurring donations are ideal because they allow for long-term planning. But also one-time donations of any amount help us.
- Liberapay (preferred option)
- Open Collective
- Patreon
- Cryptocurrency
I don’t see how agglomerating vuew of all same name communities for the user impact you as a server owner ?
You still have totalitarian control over everything happening on your server.
You can still
Delete all post and comments
Change any text in any post or comment even if made by other users and without their notice
Ban any user
Ban any community
Even ban all users and all communities (whilte only model)
I must’ve read your comment wrong. Sounds like you just want a multi Reddit type feature? I agree that that should be implemented some apps have already did it. I don’t agree that the same word community should be lumped together universally and automatically.
No multireddit cannot solve this problem.
They are not a default agglomeration view so they will never make a difference as most users never change their defaults.
Covered in more details here
https://lemmy.ml/comment/7734804
A community cannot escape the stranglehold of moderators with a multireddit, because most users will simply not have it the backup community setup in their multireddit. They will never see dissenters posting in the backuos. And that makes multireddit largely useless
Who are the moderators in this scenario you’re talking about?
It’s an hypothetical community, so they’re hypothetical moderators/owners. I’m not sure how to respond to “who are they”.
They’re some bad hombrés…
Your argument through all of this is bad moderators controlling the largest communities so I’m wondering how what you’re saying fixes any of that.
Makes communities other than the one big one visible to nonlogged and default users without extra steps.
In effect this makes all communities global by default.