Also, had another idea, we can use their API (pretty sure they won't like 
this) to poll for updates from the server.
The way I think this would work is to :

1. Import some kind of tool like jquery to tiddlywiki, to further use it to 
handle communication via JSON with the server.
2. Use this <https://getpocket.com/developer/docs/authentication>to 
register as a developer and get an API key.
3. Retrieve a list of new articles, with the below attributes.
4. Retrieve all articles (only text content, no html) from getpocket, save 
it locally to a new tiddler with the attributes retrieved from the server.

Example JSON response : http://pastebin.com/czJYZF1Y

Regards,
Stefan


On Tuesday, 8 September 2015 04:00:43 UTC+3, RunningUtes wrote:
>
>
> I've been thinking lately about storing full text articles in a 
> tiddlywiki. Right now I'm using Pocket to save the links.
>
> My current thoughts on the process:
> 1. Export the links from pocket using https://getpocket.com/export
> 2. Use wget to grab all the articles and images (wget -i 
> ExportedPocketURLs.txt)
> 3. Clean up the article like pocket. This is the step that is giving me an 
> issue.
> 4. Drag and drop all the files into a tiddlywiki
>
> Another option I'm toying with is to:
> 1. Tag articles in pocket with "Save" tag
> 2. Use IFTTT to save articles with the "Save" tag to an Evernote notebook
> 3. Export Evernote articles to html
> 4. Drag and drop all the files into a tiddlywiki
>
> Has anyone had any luck with something that works?
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/281dd75c-936c-4530-9160-41f10cd2be56%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to