Sidebar
Lemmy Moderation Tools
cross-posted from: https://discuss.online/post/6776820 > The Sublinks team has written up a little survey, which we feel is both thorough and inclusive. It covers a wide range of topics, such as user privacy, and community engagement, along with trying to gauge things that are difficult when moderating. > > Also please be aware **the information collected by this survey is completely anonymous**. As many of us in the social sciences background know, if you want the REAL feelings of individuals, they need to feel safe to express themselves. > > **[👉Moderation Survey HERE👈](https://forms.office.com/r/bEwUgpmcWW)** > > Please feel free to comment in this thread, we will do our best to respond to any genuine questions. > > We look forward to hearing from each and every one of you! > > Sincerely, > The Sublinks Team
cross-posted from: https://sh.itjust.works/post/8365829 > Question: What moderation tools do you find most useful? > > Follow up question: Are there any moderation tools you wish existed but don't? > > My wish would be some form of content editable by multiple accounts, useful for megathreads or community wikis.
I just posted about this on [!fediverse@lemmy.world](https://lemmy.tgxn.net/post/152704), but figured 'd share it here as well. :) I'm the author of lemmyverse.net and I've recently been working on a new moderation tool called Lemmy Modder. https://modder.lemmyverse.net/ Currently, it supports user registration/approvals and content report management. I offer it either as a hosted app *(which is currently only compatible with Lemmy 0.18 instances)* or a package that you can run alongside your Lemmy instance *(using Docker-Compose)*  Feel free to give it a go and send any feedback my way :) https://github.com/tgxn/lemmy-modder Edit for a note: This tool does **not** save, proxy or store **any** of your user credentials or data to me, it is only ever stored locally in your browser. I also do not use any website tracking tools. 👍
I'm building a PHP SDK for the Lemmy API. Here is the repo: https://github.com/jgrim/lemmy-sdk Here is the packagist: https://packagist.org/packages/jgrim/lemmy-sdk It's still in early development. It works; however, it's missing some tests, CI/CD tooling, and examples. Feel free to use, contribute, or ask questions.
I decided to provide my open tasks to a Kanban board rather than many update posts. I'll make larger announcements as I make headway, but you can view the Kanban board for due dates and progress. As I work on it, I'll add more details to the board, issues, wiki, etc. Key takeaways from this post: - Updates should be easier to pull than waiting for me to announce. - Anyone can register to comment or add issues. - This should give you an idea of what I've been doing and what's next. - I had gotten distracted from the bots' only initial goal and added many more features. - Everything is near completion but took longer; the first release will be bigger but more delayed. - I think I added everything I'm doing there. It might change as I realize what I've done or plan to do. I could also add missing details on some tickets if requested. - The code from socialcare.cloud will be closed source. The FOSS solution is coming later. The Kanban board can be found here: https://track.gr.im/agiles/145-2/current
I spent about 10 minutes creating a simple landing page for [socialcare.cloud](https://socialcare.cloud). This will sit there as I finalize some of the user interfaces. It lists a few features. As I get closer to being ready for release, I'll post more details. I've very close to the first release. I also created the Mastodon account [@SocialCareCloud@utter.online ](https://utter.online/@SocialCareCloud) & [Matrix Space](https://matrix.to/#/#socialcare-cloud-channels:discuss.online). I'm hoping to get the first release out by this weekend. The second by next weekend.
Would you rather install a browser extension to expand moderation tools of Lemmy or have a dedicated website to do moderation in? I've been reviewing the Reddit toolbox and believe I can create something similar to work with Lemmy using a mix of storage techniques. The other option is to pull full posts, comments, and history into SocialCare and recreate the Lemmy UI with added features that are embedded into the pages naturally rather than through extension. I've also uploaded the Icon of SocialCare.cloud to this post as a preview. Completed tasks: - I have the Lemmy integration complete - I have the design and UI of the admin complete - I have job scheduling working & fetching data from instances What's next: - Build the bot configuration - The first bot will be a post scheduler - Release previous features - The ability to create notes for users and communities - Release - Automod features - etc. More updates to come. Please, let me know what you think! -Jason
I've decided to keep the first version simple in an effort to get it live ASAP. I've decided to develop a cloud solution on the domain socialcare.cloud. I'm writing it in PHP using the Laravel framework. I should be able to get the base features done within a couple of weeks. I've already begun development. Once the service is running I'll be pursuing self-hosted options. Perhaps, in the original tech stack of Rust/Svlete/Postgres. Distributed software takes a lot more time than self-hosted and I'd like to get live asap. I'll opensource what I can. For example, there isn't a Lemmy client SDK available for PHP. I created my own and it will be opensource with an MIT license. I'll report progress as it's made. I hope everyone agrees to my decision to keep it lean and targeted.
So, never thought i would suggest a form of crypto or token, but it struck me that one of the best ways to help people pay for hosting services would be to create a de-centralized crypto token that when awarded to a user it is send on the back end to their instance. If we put this token on some of the exchanges then people could pay with either real money by buying tokens and gifting/awarding them, or converting other crypto into Fediverse tokens. We could even use the same blockchain to allow minting of one off or limited run tokens where users can create their own. Would also be cool if awards attach to the profile and are federated, but with the ability to make tokens private by the user. Just a thought, because someone wanted to give me gold for a post, and I linked to our donation page, but man it would be easy if they could have just purchased a token and sent it right then and there without having to go through all the different instance donation methods. Sadly, I am not a programmer so hopefully this idea is worth a shit and one of you smart people takes it and runs.
Hello, I've been reading over all the feedback provided by the community. This is an update on progress while also asking some questions to the community. I'm currently working on the Detailed Design of the project. This is a document that serves two purposes: 1. Ensures what I plan to build is what is expected 2. It forces me to think through the project in detail to find any holes early on While working on this document, I realized it would be great to separate additional contributions the community can make that cannot relate to this project. I am going to define the following feature sets: * In the scope of this project * Which parts must be a core enhancement * Out of the scope of this project * Finally, the requests that require significant design decisions today ## In-Scope Features There is a clear set of features that will be included. These are must-haves for this project to be a success. 1. Roles & Responsibilities 1. The ability to create super admins, moderators of the entire site, single communities, and/or just application reviews. 2. Smart mod queue ranking 1. The ability to rank local or external posts higher. 2. The ability to use rank posts by how well the OP behaves (has moderation strides against them already, etc.) 3. Certain words, phrases, or domains will rank reports higher. These words can be used to also auto-report posts. 3. A way to resolve reports by sending and recording a warning to the user or suspension by time or permanently. 4. Private notes for local moderators on posts, accounts, comments, users, etc. 6. The ability to search & filter the mod log by the user, posts, comment, community, local or remote instance. 7. Statistics to help find: 1. Overactive users that like, comment, post 2. Retention 2. Report details 1. Open reports 2. Resolved 3. Response time 3. Totals on users, communities, comments, etc. 4. Likes of posts & comments over time 8. List of posts from users of your community to other communities. For general scanning of busy communities. 9. List of comments from users of your community to other communities. For general scanning of busy communities. ## Must be core enhancements Several requests are changes to the core of Lemmy and cannot be accomplished by an external tool. 1. Restricting content from federated instances from pulling locally. Federation is all or nothing. It would be a terrible user experience for a post to be on the main instance but never able to be pulled locally without some notification that the content broke local rules. 2. Restricting federation in any form. 3. Forcing federated communities and/or instances to moderate your instance rules. 4. Blocking federated users from local communities in any way. ## Out of scope Some features I just cannot fit within this project's scope or help push the need for them to be added to the core. If these are important to you, please, work with the core team to add them. 1. Customer service tasks 1. Password reset (site handles this) 2. Changing user account details 2. Federation tools 1. Most federation-related requests will require major changes to the core and should be done as core contributions. 2. Limiting which posts show or are hidden from the feed. 3. User tracking across instances. 1. This feature would require a single instance, a central database to track, and/or enhancements to the federation logic within Lemmy. 2. This includes preventing certain users from posting in a community. 4. Any bugs with Lemmy ## Finally, a design decision Some features will require some design decisions to be possible. Mostly, the ability for more joint moderation between instances. I'll list the features below: 1. Strike count across instances 2. Risk ranking of users across instances 3. Common SPAM detection 4. Instance frustration detection (lots of strikes against its users, lots of removal of communities, etc.) 5. Shared private notes on users/communities/posts, etc These features will require some central moderation hub, which brings me back to one of the original questions. Do you want to self-host without central features, or do you want there to be a central site (like mods.socialcare.cloud) where you log in and interface with your instance? Self-hosting brings additional costs. Some data will need to be stored for this moderation tool and scale depending on your site's traffic. So for site admins, here are the pros and cons of self-hosting versus cloud solution: ### For cloud hosting #### Pros 1. Simple setup and zero to low cost 2. Better communication between instance mods 3. Quicker development 4. No need to devote development hours to installation scripts, guides, community support, etc. #### Cons 2. Admins cannot modify code directly 3. Potential subscription cost (no monetization has been figured out to run the servers/development) ### For self-hosting #### Pros 1. Admins can directly modify code rather than wait for updates or changes. #### Cons 2. Slower to develop 3. Potentially complicated installation 4. Might be less adopted by users ## What's next? I'm working on the Design Doc for what is In-Scope. These features will be built regardless. This will be done by tomorrow's EOD (July 2nd, 2023). After that, I will break ground on development. The plan is to split some of the development into microservices. This should allow for parallel development for whoever wishes to contribute. ### "What can I do?" Please help me figure out what to do with the core enhancements. Please let me know if anyone wants to take them on and own them. Let me know if you'd prefer I create GitHub issues for the core team. I need you to let me know what you want to do or can do. Please help me add to this pro/cons list for self-hosted vs. cloud-hosted, and let's decide. Thanks, jgrim
I've still actively working on the design doc. I've had to prioritize some full-time work this week so there is not a lot of progress to show. I've created the repositories to store the backend and front-end code: https://github.com/jgrim/socialcare https://github.com/jgrim/socialcare-ui This is a great place to add suggestions and track progress. I plan to fully utilize GitHub's project tools to track. Oh, and I named the product socialcare... I own the domain socialcare.cloud. Let me know if you disagree. Thanks!
cross-posted from: https://lemmy.dbzer0.com/post/220288 > New feature has been deployed on the [Fediseer](https://fediseer.com) where it can autogenerate special .svg badges for your Fediverse domain which you can embed directly. > > The images have an embedded link to the endpoints proving this, but that doesn't work in markdown, so when embedding in markdown, you need to put the link manually. > > ## Guarantees > > `https://fediseer.com/api/v1/badges/guarantees/{domain}.svg` > > This badge will display which other fediverse domain guaranteed that your domain is not spam. Remember each instance can only have 1 guarantor due to the chain of trust. > > Example: [](https://fediseer.com/api/v1/whitelist/lemmy.dbzer0.com) > > ```markdown > [](https://fediseer.com/api/v1/whitelist/lemmy.dbzer0.com)` > ``` > > ## Endorsements > > `https://fediseer.com/api/v1/badges/endorsements/{domain}.svg` > > This badge will provide a count of how many other fediverse domains endorsed for yours. An instance can guarantee another instance for any reason. > > Example: [](https://fediseer.com/api/v1/endorsements/lemmy.dbzer0.com) > > ```markdown > [](https://fediseer.com/api/v1/endorsements/lemmy.dbzer0.com)` > ``` > > ## Display > You can place these anywhere you want on your site, but obvious suggestion is on the main sidebar. This will work for any domain known by the Fediseer. If your domain is not known, simply [claim it](https://lemmy.dbzer0.com/post/185949) and then [find someone to guarantee for you](https://lemmy.dbzer0.com/post/186156).
cross-posted from: https://lemmy.dbzer0.com/post/185949 > if you think the idea of the [Fediseer](https://fediseer.com/) is a good one, we could use your help! > > If you have an instance, make sure you've claimed it. To claim it, you can use this curl command > > ```bash > DOMAIN=lemmy.dbzer0.com > ADMIN=db0 > curl -X 'PUT' \ > 'https://fediseer.com/api/v1/whitelist/${DOMAIN}' \ > -H 'accept: application/json' \ > -H 'Client-Agent: unknown:0:unknown' \ > -H 'Content-Type: application/json' \ > -d '{ > "admin": "${ADMIN}" > }' > ``` > > In the above bash script, simple replace your DOMAIN and ADMIN with your own. If you're on windows, you can use `git bash` to run it. > >Now you simply need to wait for someone to guarantee your instance. You can ask in this thread, or just look for other guaranteed instances which share your values and ask them. In fact if you pass a "guarantor": "domain.tld" key/value to the payload above, the admins of that instance will get a PM to guarantee for you! > > Once you get your API key with a PM, you can then help us add more instance. If you know of any instances that are definitely not spam, simply use the below curl call to guarantee for them as your own instance. They don't have to be claimed yet. > > ```bash > APIKEY="abcdefsawadf" > DOMAIN="notspam.domain.tld" > curl -X 'PUT' \ > 'https://fediseer.com/api/v1/guarantees/${DOMAIN}' \ > -H 'accept: application/json' \ > -H 'apikey: ${APIKEY}' > ``` > > Alternatively you can use the [API directly](https://fediseer.com/api/) so you don't have to edit curl commands. > > I hope soon we'll have a working GUI which will make this very painless. > >
dbzer0.com
cross-posted from: https://lemmy.dbzer0.com/post/163869 > I have updated the content of this devlog to match the current workflow of the API, with the streamlined registration and claims
cross-posted from: https://lemmy.world/post/370342 > I'm kicking around a few feature requests. > > One of them I've already [created in github](https://github.com/LemmyNet/lemmy/issues/3228) as it seems appropriate to mainline Lemmy, but a couple of others I think are more appropriate to third party development. Since I'm more a product management / sysadmin type and not much of a coder, I'm putting these in the aether in case they drum up some interest in those considering features for bots or other tooling. > > First is YouTube aggregation - it doesn't have to be limited to YT. I'm interested in the ability to automatically collect notifications from a list of channels (click that bell icon, baby) and generate a community post to link new videos. > > Second is RSS aggregation. If a blog or magazine or news site has a feed, and if that feed should feature an entry matching keywords defined by a moderation team, generate a post to the community linking to that content. > > If these capabilities exist already for Lemmy, even in a hackish way, please do let me know. Otherwise, these are things I am wishing for :)
Hello, I'm still reviewing the technical limitations of building this tool. I'm deciding on one of two paths from the original list. The devs will not have time to do this themselves. The community must act. You can find out why by [reading their new blog post](https://discuss.online/post/22048). I had listed six options before. You can review them all on the post [Initial thoughts](https://discuss.online/post/15233). ## Decision I'm considering Option 1 and Option 4. I'll explain why not for some and why for these two options. ### Why nots - Why not 2: - I've been looking for a project to become more than a side hustle. I believe making this self-hosted could not be monetized properly. My options are donations or charges for the software. Donations are too unpredictable, and charging for a tool to enhance an open-source project feels wrong and unsustainable. It would have to be a charge for the admins of fediverse products who may not be willing to spend money on this tool, especially as Lemmy builds out its features with time. - Why not 3: - I want to build something part of the fediverse, not just Lemmy. Doing this option makes it directly and strictly for Lemmy. There is the possibility of building additional adapter services; however, that may not be worth the effort. - Why not 5: - They have stated that they cannot take on any community-requested features. They are working through bugs. - Why not 6; - Same as "Why no 3", I want to contribute to the fediverse, not just a single application. - Moderation will need a lot of information and tools to succeed. I don't believe the current Lemmy codebase and database structure are ripe for such a large enhancement. ### Why yes I'll now clarify why I am interested in options 1 and 4. - Why 1 - This would become a potential business. It could be monetized with monthly fees and add-on products. It would be much easier to keep costs aligned with the size of the community wishing to use it. - I could potentially make this full-time if it grows enough. - Why 4 - I'm calling this the WordPress model. WordPress is completely free to download and install. However, you can pay them to host and maintain it for you. This is much easier for most people. Following this same pattern, I could offer managed hosting for Lemmy and fediverse moderation tools as a subscription. - It gives people a choice. It's not as greedy a feeling as making a closed-source SaaS. However, this does add complexity to the development. I would probably release the SaaS solution before self-hosted to work out issues. - I could open-source it and get help from the community. ### Why no to yeses Options 1 and 4 also have their downsides: - Why not 1 - People may not pay for it. A lot of hobbies have been creating their servers. There may be only a handful of large enough servers that would need such a service. - I'd be counting on the growth of the fediverse and a need for centralized and smart moderation. - Closed source code. This is against the fediverse and FOSS. - Why not 4 - I don't want to become a product manager. It would be much more efficient for me to develop from the start independently. Then lean on the community for enhancements and fixes. Once it's open, I have to manage a lot of distractions before it's ready for ever-watching eyes. ## What about the roadmap and timeline? I'm still working through the feature set. I think there are some clear winners in what people need. The first release would depend on the model chosen. A feature-rich product would require some financial incentive for me to get it out quicker. It would be difficult to justify hours of my time away from my family to my wife for something that doesn't benefit her or our son. ## Next steps I need to read a bit more into ActivtyPub. I need a better understanding of some things before a path is chosen. I'm also working through the feature requests posted by others. I will create a list of base features and try to release enhancements on a roadmap. I'll next work on a detailed design doc to ensure I don't mix anything. Finally, get coding. I don't have dates for these items yet. It's been a busy Father's Day weekend. I've also been under the weather for a few days now too. I'll keep you all posted. Please provide feedback here or within the Matrix channel; I will try to watch all the channels there.
# Welcome Hello everyone, I can tell there is a lot of interest in a tool to enhance the mod abilities of Lemmy. I've been researching ways to do it. I have six options that I'm considering. I'm trying to keep the topics high-level and avoid implementation discussions. These are undeveloped high-level thoughts. I still have a lot of research into the Lemmy code base and ActivityPub. It's late for me, so these notes are from a stream of thought. There may be changes as I think more about this or get community feedback. ## Option 1 - SaaS ### Summary A service I host. Probably maintained by donations. I might have an additional tier for enhanced moderation tools. ### Pros: - Simple setup/registration. - No additional hosting cost for Lemmy admins. - Ability to use community-shared moderation. - Community data analysis to find bad actors across the federation. - Quicker to develop. No need to worry about tech support, setup, configuration wizards, etc. - Could be set up with any ActivityPub instance. (Mastodon, Lemmy, etc.). - If successful, it could be my full-time gig. - I would be more engaged ### Cons: - I have to store personally identifiable information & manage other compliance regulations. - Feature releases are limited to a single pipeline. - You don't get your data. - No direct DB access to do advanced queries and changes. - Limited by ActivityPub capabilities. ## Option 2 - Self-hosted ### Summary Admins would have to install, set up, and maintain the software. ### Pros: - No cost for me to run anything. - Admins store their data. - Direct access to databases to do advanced querying. - Open source community project requiring/allowing outside development ### Cons: - Additional network traffic if shared moderation is used. - Link flooding and spam tracking across instances aren't as likely to exist. - Would mostly be purpose-built for Lemmy. No additional federation support. - I would be less engaged and rely on community support ## Option 3 - SaaS that requires a self-hosted service ### Summary This is sort of a mix of the above. The interface and interaction are central; however, an agent must be installed to interface with the Lemmy instance. ### Pros: - Best of both worlds. - A custom API could be built to work with the adapter service. Not limited by ActivityPub. ### Cons: - Worst of both worlds. - Purpose-built for Lemmy to start. (Adapters for other systems could be built). - More complex to build. - Additional server cost and maintenance. More complicated setup for admins. ## Option 4 - SaaS & Self-Hosted ### Summary You could use the SaaS solution or install it locally. ### Pros: - I could charge for SaaS to finance the project. - All the pros of SaaS and Self-hosted - The people have choice ### Cons: - More complex to build - All the cons of SaaS and Self-hosted ## Option 5 - Ask the devs to do it ### Summary We tell the devs of Lemmy to include better tools and how we want them. ### Pros: - Less work for me/us - Moderation built into Lemmy and not a separate app ### Cons: - We have to wait for them to do it all - They might say no ## Option 6 - Contribute to the dev repo ### Summary Build enhancements to the core of Lemmy's moderation tools. ### Pros: - Community support to add features - Users only have to update to get new features, no configuration - No additional server costs ### Cons: - Only works on Lemmy - Lemmy becomes a Monolithic application - scaling challenges - Pro: A flag could be added to only enable moderation-specific scheduled tasks on a single instance.
Here's a laundry list of sort with tons of tools we'd like to see - Role for approval of applications (to delegate) - Site mods (to delegate from admins) - Auto-report posts with certain keywords or domains (for easier time curating without reports) - Statistics on growth (user, comments, posts, reports) - User total - MUA - User retention - Number of comments - Number of posts - Number of reports open - Number of reports resolved - Sort reports - by resolved/open - by local/remote - Different ways to resolved a report - Suspend account for a limited amount of time rather than just banning - Send warning - Account mod info - Number of 'strikes' (global and local) and reports - Moderation notes - Change email - Change password - Change role - Ability to pin messages in a post - Admins should be able to purge - Filter modlog to local - Better federation tools (applications to communities, limiting) - Applications to communities to allow safe spaces to exist (people should not be able to just "walk in" on a safe space - similarly to follow requests in Mastodon in a way) - Limiting (Lock our communities down from certain instances but still allow people using our instance to talk to people from those instances) Obviously considering the moment when this is being made - federation tools are our highest priority.