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
Hmm, my first thought is that a plugin is better, since it works without worrying about federation, etc, but as front-ends become more diverse it might be difficult to keep it working on everything.
Are you thinking the site option is like browsing using normal federation, or would it be more like using an app?
I think a site / API and maybe an iOS / Android app. If I open up the API, I might lean more on the community to build the apps. Doing this would take a load off instances but put more load on me as an entry point to the Lemmy fediverse. I still have to figure out how it’ll work and run. The changes in designs and themes is a problem and will only get worse. I think there are too many variables to get a chrome/firefox extension to work.
Ah, what I meant by federated site vs app is would SocialCare act as if you were browsing the community in question from a federated instance (i.e. the posts have been federated over and you work off of that data) or something like wefwef/Voyager where you’re still connecting to the original instance’s API (plus maybe also some SocialCare APIs for any extras)?
I see what you’re saying. It would be a mix of both due to some limits of the current Lemmy API. Rate limits based on IP & inconsistent instance limits are the biggest factors. They also merge a lot of unrelated stuff into limit buckets. Without a robust API with client keys, I’m kind of limited.
It’s an interesting problem; I guess federation needs to be part of the solution just to allow access to enough data when your need it.
In my head the solution was a plugin that could call external APIs, like (plug incoming) the image duplicate detection tool that I’m working on.
I rather have it as a site which I could also selfhost.
It’d be easier to improve without relaying on having the browser open.
Also it’d be easier to make it work on mobile.Some of the tools I use to build it cannot be distributed. I plan to get a SaaS solution out ASAP and then work on a distributed build separately and as an open-source project for self-hosting.
I’m calling it the reverse WordPress. They had FOSS first, then hosting. But due to time and need, I’m doing it in reverse.
