I was thinking it would be kind of fun to have a TiddlyWiki backup
button that used your post or upload plugin to store a copy of the
TiddlyWiki on SharedRecords. That would make it very easy to archive
and share TiddlyWiki documents.
You could even do it securely by using the proxy API which gives you
back a QR code that includes a decryption key. (See examples below).
Anybody done this? Would this be useful to the TiddlyWiki community?
I'm sure it would be useful to me, even as just a place to backup and
distribute TiddlyWiki files.
If you put the resulting URL into the locally saved document, you end
up building a complete version history within the document. Becomes a
"poor man's" TiddlySpot (but with complete versioning).
This could also be a way to solve John's problem. If you create a
template, just publish it on SharedRecords.org and use the resulting
URL as a place to start. Note that you don't actually have to do any
synchronization, just back up/publish whenever you want.
Only downside is that the URL keeps changing with each new version.
(Think of this as the permalink).
-Greg
[Note the endpoints of the REST URLs will change soon when the next
version is rolled out.]
=====Plain text (unencrypted) storage====================================
API: http://www.sharedrecords.org/trac/sharedrecords/wiki/RestRecordDeposit
Example:
SHA1(original.html)= 8e636b1c0af14814fc67748ab54a3aa7d01893fb
curl --verbose --upload-file original.html
http://sra.sharedrecords.org:8080/SRCDataStore/RESTServlet/8e636b1c0af14814fc67748ab54a3aa7d01893fb.data
===Secure, encrypted storage with QR code token for retrieval=============
API: http://www.sharedrecords.org/trac/sharedrecords/wiki/ProxyPut
Example:
curl --upload-file original.html
http://sra.sharedrecords.org:8080/SharedRecordsProxyServer/ >
token.jpg
--
UnaMesa.org - Learning to Serve