From a technical standpoint, great work! This is awesome.
From a community moderator standpoint...ugh, do we really need someone to write a bot and share it with the world, incidentally making the spammer's jobs that much easier?
Then again, I think some of the spammers have already accomplished this, so that's moot. Shrug
Maybe we need DEV to have a official tag or identification system for bots, so it can be a notifications preference to squelch it.
Your point is valid. But it’s not like this isn’t providing content. It’s just doing it via a automated way. I have seen other bots that don’t offer value in the same way.
Oh, I agree, great concept and use! I'm just concerned what the rise of the DEV bots will lead to later, but I agree with the author and Ben that this isn't presently a problem, and making bots clearly labeled (as you suggested) first-class citizens will help keep the negative down.
I'd like if we could make bots first class citizens, with a special classifications. Likely we'd want these bots to belong explicitely to users and/or orgs and they could do the same basic things, but would be classified in a special way.
I think the usefulness of bots for certain types of subscriptions, like I might want a bot that auto-creates a post for every issue in a repo for a side discussion or just to keep up with stuff going on.
Once we get this system underway we can migrate this bot there. Until that system is available, we'll likely take the standpoint of neither endorsing this nor denying it if done with the right intentions.
One thing you may want to do short term, is just to tag bots somehow. Not so much for user transparency, but to flag would existing things would be impacted by any change.
The added benefit would be any user transparency it brings.
That being said, that may be half the effort already.
The first thing I'd like to say is that, to the best of my knowledge, I am directly not helping spammers in any way with this bot. As of writing this comment, the source code for the bot is not public, and so, without access to that private source code, spammers could not use that code for any purposes.
Another thing to say is that Daily Developer Jokes uses the DEV API, which provides the ability to create posts via a basic POST request to any DEV user give post data and a valid API key. So, in theory, anyone could use that API endpoint to create automated posts. In fact, one DEV member has made a Chrome Extension that utilizes the API to schedule posts (see article). The DEV API imposes "a limit of 10 articles created each 30 seconds by the same user", which the Daily Developer Jokes abides by.
Lastly, I'd like to just agree with @khrome83
, in that Daily Developer Jokes provides unique content, just in an automated fashion. From what I can tell, Daily Developer Jokes abides completely with the DEV Code of Conduct.
It would be interesting to see if more bots on DEV start appearing, and if and how DEV staff will react to that.
— Gabriel
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
From a technical standpoint, great work! This is awesome.
From a community moderator standpoint...ugh, do we really need someone to write a bot and share it with the world, incidentally making the spammer's jobs that much easier?
Then again, I think some of the spammers have already accomplished this, so that's moot. Shrug
Maybe we need DEV to have a official tag or identification system for bots, so it can be a notifications preference to squelch it.
Your point is valid. But it’s not like this isn’t providing content. It’s just doing it via a automated way. I have seen other bots that don’t offer value in the same way.
Oh, I agree, great concept and use! I'm just concerned what the rise of the DEV bots will lead to later, but I agree with the author and Ben that this isn't presently a problem, and making bots clearly labeled (as you suggested) first-class citizens will help keep the negative down.
I'd like if we could make bots first class citizens, with a special classifications. Likely we'd want these bots to belong explicitely to users and/or orgs and they could do the same basic things, but would be classified in a special way.
I think the usefulness of bots for certain types of subscriptions, like I might want a bot that auto-creates a post for every issue in a repo for a side discussion or just to keep up with stuff going on.
Once we get this system underway we can migrate this bot there. Until that system is available, we'll likely take the standpoint of neither endorsing this nor denying it if done with the right intentions.
I think that’s a fair and great place to start.
One thing you may want to do short term, is just to tag bots somehow. Not so much for user transparency, but to flag would existing things would be impacted by any change.
The added benefit would be any user transparency it brings.
That being said, that may be half the effort already.
You make an interesting point.
The first thing I'd like to say is that, to the best of my knowledge, I am directly not helping spammers in any way with this bot. As of writing this comment, the source code for the bot is not public, and so, without access to that private source code, spammers could not use that code for any purposes.
Another thing to say is that Daily Developer Jokes uses the DEV API, which provides the ability to create posts via a basic POST request to any DEV user give post data and a valid API key. So, in theory, anyone could use that API endpoint to create automated posts. In fact, one DEV member has made a Chrome Extension that utilizes the API to schedule posts (see article). The DEV API imposes "a limit of 10 articles created each 30 seconds by the same user", which the Daily Developer Jokes abides by.
Lastly, I'd like to just agree with @khrome83 , in that Daily Developer Jokes provides unique content, just in an automated fashion. From what I can tell, Daily Developer Jokes abides completely with the DEV Code of Conduct.
It would be interesting to see if more bots on DEV start appearing, and if and how DEV staff will react to that.
— Gabriel