About Lemmit

For example, it'd be nice for anyone that looks at/finds https://lemmit.online/c/dota2 to also find that https://discuss.tchncs.de/c/dota2 or https://lemmy.world/c/dota2 is an actual community that corresponds to that with user content, not bot content.

I'm sure there's lots of equivalents for other communities as well where that would make sense.

Before was running on the cheapest model (1 core / 1GB mem / 30GB storage) at $12/month. The machine was running pretty low on memory, causing it to start swapping, which in turn caused the cpu to get too busy, and everything to slow down.

Now it has a whopping 2GB of memory, and things seem to have calmed down - cpu is back to around 10-15% usage, and swap is down to 0. Happy times all around.

Because of the amount of subs being archived, it now takes about 15 minutes between updates for each sub (was 18 before I updated the VM).

I'm planning to build some kind of scoring system, based on the amount of posts per subreddit (per day?), and amount of subscribers on the lemmy community. That way communities with little subscribers or that don't see many posts per day, will only be updated once per hour.

At the same time, I feel that subs like AskReddit, OutOfTheLoop and other "question-based" subreddits shouldn't be archived by Lemmit. In my opinion those kind of posts are useless without those answers, but please let me know if you disagree.

[email protected] doesnt match up with r/perchance. its last post was 5d ago.

• Fixed a bug where posts would not be submitted because the title didn't contain long enough words.
• Fixed a bug where posts would not be submitted because the url was too long.
• Fixed a bug where posts would not be submitted when it was linking to a /user subreddit.
• Fixed a bug where the bot would think Every Post Everywhere was a subreddit request, and would reply to it.
• Fixed a bug where the bot would crash without recovering whenever something went wrong during new subreddit requests

A fruitful day all in all, I'd say.

That the replies-everywhere-bug was just because I forgot to include a variable in the bot deployment? 🤦

Long story short: I messed up with the domain registration for this instance, and never replied to a mandatory email. The domainname (lemmit.online) got put in suspension, causing disconnects all over the fediverse.

I fixed it as soon as I found out, but it will probably take a few more hours for the issues to be fully fixed.

So ehm. Whoops. Hope this explains and fixes the federation issues we've been having today.

If Lemmit is federated, doesn't that mean that all of its crossposts of reddit content should show up in everyone's "All" feed (for example, on Lemmy.world)?

When I went to https://feddit.de/c/[email protected] I noticed the sidebar links to /c/about - which doesn't exist on feddit.de

I'd suggest to change the link to https://lemmit.online/c/about so people from other instances can find it more easily.

Current reply:

I'll get right on that. Check out /c/[email protected]!

Proposed reply:

I'll get right on that. Check out /c/[email protected]!

Click here to fetch this community for your lemmy instance if you get a 404 error with the link above.

Most importantly that the bot no longer crashes (and does nothing all night while I sleep 😛) when trying to create a community that has already been requested.

Furthermore mostly making the code prettier and adding tests.

In card view all you see is the bot header and none of the actual content. Maybe it should go at the bottom and just prepend something short like [Lemmit Bot]

This bit.. This is an automated archive made by the Lemmit Bot. The original was posted on /r/ayaneo by /u/HystericalBanana on 2023-06-17 21:43:04+00:00.

Great for communities that have not made the jump to lemmy. Now I don't need to dive into reddit to get that info. Will this break when the reddit Api limits come into force (assuming people keep requesting more communities)?

If you want can you add comment syncing so we can see the comments on Lemmy too

Fixed a couple of bugs today:

• Nasty one that made the bot get stuck in an infinite when trying to add a post by a deleted user, which kept the bit offline for most of last night.
• Another creative one that, when posting certain links, would actually work, but the lemmy gateway would respond with a timeout. It only happens on certain links, but consistently. Which would make the bot think it was unsuccessful, which would make it try to post again the next time. Causing a duplicate post each time (technically it was a cross post to itself... Which is interesting in a whole new way).

TLDR: right now there is a workaround in place that assumes a timeout post to lemmit was actually successful. This might cause it to drop posts in the future, but seeing that the server is barely breaking a sweat at this time, it should be good until a better fix is implemented.

Also got some great feedback from users, which I added to the TODO.