DEV Community

Discussion on: Deno - Node.js successor (?)

Collapse
 
sebastienbarre profile image
Sebastien Barre • Edited

Dev.to, is there a point to this? As Deno reached 1.0 we saw a deluge of posts riding this wave and essentially repeating the exact same points as the announcement, and posting the very same video (since Ryan did only a few). This one takes the cake; the same four bullet points we have seen here for the past 2+ weeks, the video, and what is essentially an ad for the author's product. This type of astroturfing brings down the overall quality of Dev.to in my opinion. Anybody at the wheel?

Collapse
 
bbarbour profile image
Brian Barbour • Edited

This is the first one that I clicked about the Deno thing. But, is it really up to DEV.TO to be "editorial" about their content? This is an open blogging platform, not an e-zine.

Collapse
 
sebastienbarre profile image
Sebastien Barre • Edited

There are content managers on DEV.TO; a new one was announced just this morning for example (Gracie). Is contents being managed? Not a trick question; I actually don't know, hence my comment.

It takes five minutes to create your own, possibly self-hosted blog nowadays, so posting here on DEV.TO is something one does purposefully to benefit from the many eyeballs and captive audience. This post strikes me because a 2-seconds search for "deno" on this site would have brought a dozen of articles repeating the same bullet points and video. This one is an ad-dump. As a regular reader, I'm asking myself: what was brought to the community's plate, or my own? This is not the first time I see this on DEV.TO, duplicate/reworded contents and poorly disguised ad have been rampant. All known, unfortunate practices I'm afraid.

I'm not asking for censorship of course, but if this is a community, and not a free-for-all dumping ground for people to just drive traffic back to their own portals or products, I believe we could benefit from being able to easily flag posts as duplicate, low-quality, "ad", or "sponsored", whichever may apply. And possibly filter our feeds accordingly, or by a quality threshold. This would elevate the experience for developers.

UPDATE: answer from a co-founder