https://github.com/epicstuff/lemmit

"Fork"ed from https://gitlab.com/sab_from_earth/lemmit
https://github.com/epicstuff/lemmit

Last synced: 4 days ago
JSON representation

"Fork"ed from https://gitlab.com/sab_from_earth/lemmit

• Host: GitHub
• URL: https://github.com/epicstuff/lemmit
• Owner: EpicStuff
• License: other
• Created: 2024-01-09T03:34:17.000Z (about 1 year ago)
• Default Branch: main
• Last Pushed: 2024-01-09T20:10:35.000Z (about 1 year ago)
• Last Synced: 2024-11-20T10:05:57.885Z (2 months ago)
• Language: HTML
• Homepage:
• Size: 178 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE.md

Awesome Lists containing this project

README

        
# Lemmit

A Reddit-to-Lemmy cross-poster.

## Known bugs:

- When a time-out occurs on a post, it will not be posted again. Often, the post created successfully, but something goes wrong in the gateway. Proper solution would be to check afterwards.

## To do:

- Add a sticky to each community, explaining Lemmit is a Bot-service, and link to any known **non-botty** alternatives. This will also allow Lemmy users to suggest proper alternatives, since bots aren't that smart.

- Disable deleted Communities in DB

- Allow for removal of communities:

  - When failing to post, check if still exist. If not, set enabled to False

  - Alert the bot through private message

  - Check when requesting

- Continue long posts in comments

- MORE TESTS!

- Create a watcher that periodically checks for updates (edits / deletes) on reddit post and sync those:

  * 1 hour, day, week, month after posting.

  * Automatically when reported (Unless queued in last hour, to prevent abuse)

## Won't do:

- Toggle between copying **New** or just the **Hot** posts

  * Not feasible with the amount of subreddits that are being monitored.

- Have a hardcoded set of subs, rather than working through a request community, for running on other instances.

  * Forks can take care of that.