This is a chance for any users, admins, or developers to ask anything they’d like to myself, @nutomic@lemmy.ml , SleeplessOne , or @phiresky@lemmy.world 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 @phiresky@lemmy.world 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
What is currently in the works to help admins locate spammers and problematic users on their instance?
Right now I believe it relies heavily on users reporting and admins looking through a users history however I think that is really inefficient.
Are there any better visualization tools that could be made to aid admins?
Registration applications, and user reports are the best way to handle trolls. The first stops 90% of them, the second means we can ban and remove all their spam at the click of a button.
I don’t see how you could prematurely know about spammers or trolls until someone reports them. We don’t plan on adding any text-analyzing AI or anything like that into lemmy’s codebase.
I don’t think you can. My suggestion was more focused on how admins make decisions after a report. Right now they have to do a manual scan of the person’s comment history and that is the part I find inefficient. If it was possible to just show extra high level information on the user it might make it easier for the admin to make a decision.
Yeah using AI to try and analyze comments would be overkill and probably prone to manipulation anyways.
Edit: I’m sorta talking more specifically towards banning a user or seeing if what a user is doing is a repeated pattern.
I don’t think there’s a way you could avoid going into their history. I do that as an admin to verify that the account in question is indeed repeatedly breaking rules. I’m open to suggestions tho.
How would you suggest to make it more efficient?
Well I am not 100% sure on what the best method would be.
I think the addition of letting moderators see who is voting on what posts is a nice addition since they would tend to be closer to where the content is.
More generally I was thinking about creating a dashboard that gave the admins statistics about that user.
Similar to how we as users can see how many comments and posts any user makes, it might be useful to allow admins to see statistics about which communities the user interacts with or some rudimentary similarity score with other users?
These are some ideas I thought of on the fly and have not thought about the implications but the gist is something that allows the admins to get a better understanding of what is going on from like a bird eye’s view.
Edit: and where -> on what posts
The main implication is that someone would have to implement it, and we dont have enough developers for that.
Yeah that’s fair. It was just more of a possible what if.
Hopefully you’re able to get more people that can help develop the features that are in the backlog.
Anyways thx for answering. I was half expecting it to be skipped.
This seems like a big change that also requires a lot of brainstorming to flesh out. It sounds like it would best be made as an RFC for now.
Hrm… I remember my time as a reddit mod, community statistics were very useful in making mod decisions. But that was only because reddit hosts so many vile communities, which isn’t a problem we really have at the moment.
There is now a voting ledger for comments and posts for admins, that shows who is abusively downvoting or upvoting everything. I am a victim of it by GrapheneOS “rabid dogs” (Techlore community uses that term aptly), though they may have started to become cautious in the past week or so after 2 months of doing it.