This probably isn't as good an idea as it sounds.
Firstly, you don't want to do anything that interferes with the browser's native touch events. If a browser relies on the user swiping from the edge of the screen to change tabs (as per more recent Android browsers), your functionality could potentially clash. Users who try to do the one will end up doing the other, and it could be hard for users to keep track of whether they're moving between tabs or moving between articles. Gestures like this typically work on an application level - by adding your own, you could be creating interaction problems further down the line.
Secondly, this isn't common behaviour on the web, so you'd have to signpost it. This means using up space and drawing attention to something on the page, which is obviously something you want to ration as far as possible.
Thirdly, is this even useful? Is there actually a logically defined 'set' of articles to be traversed through in order? If they're of different topics or categories, swiping blindly is pointless. If they do make sense read in order, why not present them on scroll rather than rely on a UI neologism?