The rules for bots # Bots should be clearly prompted by a command # Bots that always post without human intervention are noisy and are often unwanted.
Bots should not act in a community without mods from that community being contacted first # Moderators should not have to chase down the bots being used in their community, it should be opt-in. Just ask, be nice.
Bots should minimize the space they take with their messages # A bot’s response should be a small as possible to avoid taking space that could be used by people.
Hi there!
I’ve been contacted regarding my @[email protected] bot. Currently it’s disabled for beehaw.org as can be seen here.
I’d like to raise a discussion though as I think the bot is really useful.
Here are some global all-time stats:
---------- --------- ----------- ------------------------- ------------------------- ------------------------ Comments Upvotes Downvotes Negative comments count Positive comments count Neutral comments count ---------- --------- ----------- ------------------------- ------------------------- ------------------------ 430 3096 82 0 429 1 ---------- --------- ----------- ------------------------- ------------------------- ------------------------These are per-instance stats (I stripped other instances than yours). If I’m not mistaken, downvotes are disabled on Beehaw, so the like ratio doesn’t say much, but other numbers still could:
-------------------- ---------- --------- ----------- ------------ --------------------- Instance Comments Upvotes Downvotes Like ratio Upvotes per comment -------------------- ---------- --------- ----------- ------------ --------------------- beehaw.org 28 236 0 100.00% 8.43Edit: The stats are generated by this - while it’s not the cleanest code I’ve ever written, I think it’s pretty readable and everyone can see that the stats are not some weird numbers to make it look better than it is.
My thoughts are mostly that I wish this were integrated in Lemmy because of a couple reasons:
I liked the original autotldr bot on Reddit. The one here though seems to be producing a large summary instead of just TL;DR.
Here’s an example: https://lemmings.world/comment/920986
This comment takes up most of the screen space on my mobile device. I don’t consider this to be a TL;DR. At this rate, I’d opt to just read the article in question instead.
The other problem is that lengthy TL;DRs like this obstruct comments, making it annoying to scroll past for those of who are on mobile devices. I could block the bot of course, but I don’t want to - I do want a legit TL;DR, not a reworded article.
Here’s my attempt at generating a TL;DR of the mentioned article, using ChatGPT:
IMO, this is what a TL;DR should look like - a single paragraph and under 150 words.
To be fair, the TL;DR would be a lot shorter if the breaks between sentences were removed. I personally draw the line at around 200 words for a summary, so the 183 words in the summary is a bit long but still a reasonable TL;DR for an article.
Since Lemmy implements spoiler tags, I think wrapping the summary in a spoiler tag would be a way to solve the length problem.
I love the idea of wrapping the summary in a spoiler tag! I think that would be a great idea to be implemented for bots like that and would solve a lot of this. That’s a great idea you’ve had and I thank you for sharing it!
Would it be possible for the bot to DM us instead when communities decide to ban/restrict them for whatever reason?
I’ve found this bot incredibly useful personally, and I assume the community does too, looking at various Lemmy posts where the TLDR bot upvotes closely follow the OP upvotes (sometimes exceeding it)
Note - I’m not a beehaw user, for anyone reading whose apps do not show my instance.
Well, I may try it, but it might drive the costs of running the bot significantly if a lot of users use the feature.
Edit: Done. Will see how it goes, might roll this back if it’s too taxing on my wallet.