pocket: reuse pockexport data access layer

BREAKING CHANGE! Data parsing was switched to pockexport.
This would help to keep it consistent across different apps in the future.

When you update, you'll need to:

- clone pockexport (latest version)
- set pockexport repository in your config (see doc/MODULES.org)

doc/MODULES.org

@@ -19,6 +19,7 @@ If you have some issues with the setup, see [[file:SETUP.org::#troubleshooting][
   - [[#mygoogletakeoutpaths][my.google.takeout.paths]]
   - [[#myhypothesis][my.hypothesis]]
   - [[#myreddit][my.reddit]]
+  - [[#mypocket][my.pocket]]
   - [[#mytwittertwint][my.twitter.twint]]
   - [[#mytwitterarchive][my.twitter.archive]]
   - [[#mylastfm][my.lastfm]]
@@ -67,6 +68,7 @@ modules = [
     ('google'         , 'my.google.takeout.paths'),
     ('hypothesis'     , 'my.hypothesis'          ),
     ('reddit'         , 'my.reddit'              ),
+    ('pocket'         , 'my.pocket'              ),
     ('twint'          , 'my.twitter.twint'       ),
     ('twitter_archive', 'my.twitter.archive'     ),
     ('lastfm'         , 'my.lastfm'              ),
@@ -149,6 +151,23 @@ for cls, p in modules:
         # alternatively, you can put the repository (or a symlink) in $MY_CONFIG/my/config/repos/rexport
         rexport    : Optional[PathIsh] = None
     #+end_src
+** [[file:../my/pocket.py][my.pocket]]
+
+    [[https://getpocket.com][Pocket]] bookmarks and highlights
+
+    #+begin_src python
+    class pocket:
+        '''
+        Uses [[https://github.com/karlicoss/pockexport][pockexport]] outputs
+        '''
+
+        # paths[s]/glob to the exported JSON data
+        export_path: Paths
+
+        # path to a local clone of pockexport
+        # alternatively, you can put the repository (or a symlink) in $MY_CONFIG/my/config/repos/pockexport
+        pockexport  : Optional[PathIsh] = None
+    #+end_src
 ** [[file:../my/twitter/twint.py][my.twitter.twint]]
 
     Twitter data (tweets and favorites).

doc/SETUP.org

@@ -427,7 +427,7 @@ Several other HPI modules are following a similar pattern: hypothesis, instapape
 
 ** Twitter
 
-Twitter is interesting, because it's an example of a data source that *arbitrates* between several data sources from the same service.
+Twitter is interesting, because it's an example of an HPI module that *arbitrates* between several data sources from the same service.
 
 The reason to use multiple in case of Twitter is: