Hey everyone, I just finished up a new bot for the instance called Link
This bot aims to give suggestions for other communities in the instance to post to to start populating the more specific topic communities. It currently is triggered just off of keywords it finds in post titles.
This should help people find other communities after they post to [email protected] and encourage cross-posting in the instance since thats recommended (and standard lemmy behaviour is to show crossposts as one post in the post feed)
I added some of the communities in the instance and will go through and add in the rest of them shortly
Great idea :)
I wonder if it would be better as a PM to the OP instead of a comment
is it open source?
yeah although I havent pushed changes to a repo recently, ill do that and share in a sec
figured having it as a message also makes it a spot where readers can see communities for that topic as well
yea the comment does give that visibility to other people too, although you would see the cross-posted communities anyways (as long as those communities are federated with the reader’s instance)
I mean like
I think it’s good either way though, probably doesn’t make a big difference for us since we’re all in this instance, but if people start using this bot for other things too and across multiple instances then the comment could be better than a PM
The one issue I ran into is alternate UIs other than lemmy-ui dont seem to collapse crossposts in the post feed so the recommendation of cross-posting everything floods people not using lemmy-ui
Going through and making issues in all of their repositories
Source is up at https://github.com/PangoraWeb/link-bot
Leaving my 0.02$ here:
Please don’t deploy this bot. It’s annoying, it contributes nothing to actually create interesting content for the community to engage, and in fact its main output is spam.
It does more harm than good. Please don’t.
I’d add that if the idea was any good then instead of spamming people left and right, it would suffice to crosspost stuff on target communities.
I can’t stress enough how annoying and ill thought out this bot is. I’ve seen the bot react to posts to [email protected] pointing to [email protected] , and then react to posts to [email protected] to point to [email protected]. What’s the end goal here? Spam all communities with requests to cross-post stuff to all communities under the sun?
If the goal is to kill Lemmy as a usable service, you’re doing a good job.
The article on c/programming was about postgresql and the article on c/postgresql was about performance. Both were articles that could be crossposted to those communities and both are communities that need some more activity so the bot just lets the author and people who enjoy that post know about a community they may not otherwise know about.
Based on firing without me tweaking it to remove that case its fired twice in the past two days, once today and once yesterday out of all of the posts posted to the instance which is barely anything and is nowhere close to spam. There was 46 posts in the instance total today and 85 in the past two days. Its also one comment that can easily be ignored and will be buried by other comments due to how lemmy’s default comment sort works with putting newer comments at the top
If you severely dislike the bot you can block it and you will no longer see those comments
I leave this comment ulrik gave you
The article on c/programming was about postgresql and the article on c/postgresql was about performance.
It really doesn’t matter. It’s really not about the article. It’s about the high volume of spam that you are trying to generate on programming.dev communities without creating any value at all. I mean, your bot is not cross-posting content: it’s spamming communities to get someone else to do the work.
Here’s the latest screwup that your bot is creating (link):
The [email protected] community currently lists 3 active users per month, and your bot spammed it on each new post sent to it asking those 3 active users to cross-post stuff to multiple communities. This is nuts.
Again, please stop with all the spamming. Your bot is the single most damaging thing done to programming.dev since its been launched.
for node.js it seems like it was triggering on the .js which I just went through and removed so it should get barely any triggers now unless you explicitly mention something
for that community message it sent you posted an article about graphql and about performance
I made it not crosspost by default so I can tweak things and so people are guided for future posts. (and to prevent false positives while im tweaking things). Im purposely tweaking it to fire less and less and like I said im aiming to get it to fire on 2% of the posts
again, block the bot if you dont want it
for node.js it seems like it was triggering (…)
The problem is not how the bot is triggered. The problem is that the bot is broken by design. Its main output is spamming Lemmy instances with posts that add no value at all.
I mean, haven’t you even noticed that in some communities your bot is posting more messages than the number of daily visitors?
What exactly do you plan to achieve with this?
Please shut down your bot.
which communities? And triggering is relevant since by reducing how its triggered it reduces the about the comments it posts or as you like to call them spam
Ive responded so many times at this point saying why its not spam and why they add value
Just for you ill add a rule that it cant trigger on any of your posts
which communities?
If you’re paying any attention to what your bot is doing, you’ll be aware of which communities it’s triggering and what/how many messages it’s spamming them with.
Nevertheless, again: the problem with your bot is that it’s broken by design. If your goal is to cross-post submissions to related communities, instead of spamming discussions with requests your bot would be cross-posting submissions to related communities. If you did any semblance of requirements gathering, you would also notice that a basic feature of these bots is a) be opt-in, b) stop posting based on community feedback.
