I'm a software developer, and I'm currently noodling around with the idea of a small suite of software to help me moderate a couple communities. Right now, the features I'm thinking of are:
- Lemmy bot integration - the suite would require a bot account.
- Some kind of content moderation (detecting things like spam, bigotry, etc.) to flag for me to review. Similar to the mod queue on that other site.
- Automatic removal of certain kinds of content. I figure this would be configurable, like you could choose whether your community is for text posts, for links, for videos, for pics, or some combination of everything.
- Domain blacklists and whitelists.
- Moderation record keeping - in other words, a database to keep track of bans, warnings, reports, etc.
- Canned automatic messages, which would be useful to send when banning, unbanning, responding to certain types of queries, and so on. So if you use the software to ban someone, they automatically receive a notification about what they were banned for, and for how long.
- Scheduled automatic posts, which would be configured with *.md files for content. Good for things like monthly meta threads.
- Controls for the bot via JSON objects in private messages, which would direct it to follow commands.
- Some kind of configurable user commands for the bot. (Haven't really figured out what this would look like yet.)
- A simple web interface for all of this.
That's what I'm considering so far, but I'd love to get more ideas from the broader Lemmy community, and will post it on Github if it comes together.
The technology stack I'm considering is:
- Node/Typescript
- The lemmy-bot library
- Sequelize for the database
- Nest.js for the web backend
- [TBD] for the web frontend (I hate React, so not that. Probably either Vue or Angular)
- Docker for containerization
So what features would other Lemmy mods like to see in a Lemmy moderation suite like this?
Edit: OK, I've had a chance to take a look at the code for the existing Lemmy "automoderator" bot that's in progress, and I think I'm still leaning towards working on one of my own, partly because it looks like there's a real desire for Lemmy bots that use Node. I think there's room for two or more in the fediverse. And hopefully, we can all learn from each other. I know I'm bookmarking the Python bot and watching to see how it improves.
Anyway, I'd like to thank everyone for the suggestions! I'm hoping to get started on it this weekend. We'll see how it goes.
I appreciate all of this perspective.
I have never worked with angular, but I've seen many talks on it. Imo it feels really rigid, and like it's not even js. I felt like when I interviewed candidates who had worked a lot with angular, they struggled to understand normal JavaScript and were fixated instead on how angular does things.
I tried vue and simply hated it with my entire soul. The syntax is enragingly confusing for me. Also doesn't feel like JavaScript.
I was pretty resistant to react but I guess in the end, the flexibility it affords is why I don't hate it. It feels like JavaScript. Have you tried next.js? I feel like it's a big help with a lot of react's pain points. Also typescript with next.js helps so much with the "stringed together mess" feeling you mentioned.
In some ways, you're absolutely correct about Angular as far as its rigidity is concerned. It's a framework, not a view library, which means it wants you to do things the Angular way. It wants you to lay out your file structure in a particular way, it wants you to use its integrated tooling, and so on.
That said, it's still just a Typescript framework, which, yeah, isn't JavaScript, but that's not a drawback unless you don't like Typescript. If you're comfortable in Typescript, any sense of rigidity in Angular kind of evaporates, and you start seeing its structure as guardrails that prevent problems, instead of restrictions on creativity.
At my work, our frontend is React, and there isn't a single developer on the team who wouldn't switch to Angular in a heartbeat if we could.
Regarding Next.js, I've played around with it, and it's not bad. The thing is... It actually strongly resembles Angular in the structure and utilities that it brings to the table. I think if you have to use React, it's probably the best way to do it, especially if you're also using Typescript. But honestly, the fact that you like Next.js and Typescript tells me you might not hate Angular as much as you may think if you tried it.
They work basically the same way. You have a CLI that creates your initial app and settings, it gives you sane defaults for folder structure, it comes with routing and HTTP clients built in, etc. The best thing about Next.js is that it gets rid of the majority of that dependency hell I mentioned, and Angular has always had that.
Anyway, I really appreciate that we can have this conversation without tearing each other's throats out! People can get so hot under the collar about their preferred development tools, but I've always been of the opinion that people should just use what they like and let everyone else do likewise.
Thanks for the reply. Yeah, perhaps I would feel differently about Angular now. The thing I didn't like so much was the
ng-attributes for everything. Maybe that isn't even a thing anymore.And yeah, I agree about having a discussion here -- I attribute this largely to a better community on Lemmy. On Reddit, it seemed like so many people were super rude and I think I got a bit that way myself. Here, I find myself being more charitable despite disagreements that can happen.
There are a few
ngattributes still, but if you're used to seeingng-- as in, with the hyphen - then that's the old version, AngularJS, which is very different. Today, thengattributes are mostly for interactive stuff, like iterating over an array or allowing a button to trigger a method on an Angular class. It's pretty similar in concept, if not execution, to the way you call JavaScript from inside JSX elements.I guess one way to look at it is that in order to glue together markup and code, you either have to have some markup in code (the JSX way) or some code in markup (the Angular way). It's mostly a matter of taste, in my opinion.
YES, absolutely. Couldn't have said it better. I think Reddit was already becoming toxic before it imploded, and I'm not sure why. Heck, you and I are both refugees from it, and here we are, having an extremely friendly conversation without going after each other despite minor points of disagreement.
Feels really great, honestly. It's a breath of fresh air.