--
You received this message because you are subscribed to a topic in the Google Groups "TiddlyWiki" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tiddlywiki/OCUp73Bads0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tiddlywiki+unsubscribe@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/1b033412-0108-4af7-962b-00992c91ce0a%40googlegroups.com.
To unsubscribe from this group and all its topics, send an email to tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/1b033412-0108-4af7-962b-00992c91ce0a%40googlegroups.com.
Noteself looks promising, I think, but is confusing to me:
1) it says I can save multiple TWs but since the url is always the same, it is not clear how to move from one to the other,
and whether saving a new one will also include there all the tiddlers saved to date in the current one.
2) It looks like the only way to sync between devices is to already have a couch database.
I assume this means I need to do a whole learning curve re Couch databases to create one. I wouldn't even know where to begin with that.
3) Since the noteself url is always the same, it isn't clear how I would share a tiddler's permalink with others.
But is there a plugin for setting up online use that I could use to edit and save changes to them when out and about working from my ipad? Some way to host it online but where if I have the username and password, I can edit it? I recall Udo had something that worked like that for TW classic.
--
You received this message because you are subscribed to a topic in the Google Groups "TiddlyWiki" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tiddlywiki/OCUp73Bads0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tiddlywiki+unsubscribe@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/bf3529ca-f01b-4dea-83ba-984a87747ae6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
It does concern me, though, the level of insecurity of the store.php approach. So I will still eventually experiment more with Noteself. But to be honest I do need the ability to link between files and permalink to share with others.
...
Dave
When you say the insecurity of the store.php approach worries you, what exactly are you worried about?I agree there are security issues with store.php but I have seen far worse issues in commercial applications.Personally, I was concerned that store.php uses cleartext passwords in it's configuration file. So, I changed my copy to use a hash of the password (for the technical minded, I used the hash format for Apache Digest Authentication).Store.php has settings to override the tiddlywiki configured filename and backup directory, I used those to prevent someone from uploading arbitrary files.
There is still an issue of brute force password guessing that I haven't decided how I want to resolve yet.
On Monday, April 24, 2017 at 4:16:48 PM UTC-4, David Gifford wrote:
It does concern me, though, the level of insecurity of the store.php approach. So I will still eventually experiment more with Noteself. But to be honest I do need the ability to link between files and permalink to share with others.
...Dave
--
You received this message because you are subscribed to a topic in the Google Groups "TiddlyWiki" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tiddlywiki/OCUp73Bads0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tiddlywiki+unsubscribe@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/15a32c0d-1bc9-4a0a-8dc4-1f0ba849f031%40googlegroups.com.
Hi lost adminMy concern is the one contained in http://tiddlywiki.com/#Saving%20on%20TiddlySpot, since the store.php is the same process as Tiddlyspot.Dave
On Wed, Apr 26, 2017 at 9:08 AM, Lost Admin <thelos...@gmail.com> wrote:
When you say the insecurity of the store.php approach worries you, what exactly are you worried about?I agree there are security issues with store.php but I have seen far worse issues in commercial applications.Personally, I was concerned that store.php uses cleartext passwords in it's configuration file. So, I changed my copy to use a hash of the password (for the technical minded, I used the hash format for Apache Digest Authentication).Store.php has settings to override the tiddlywiki configured filename and backup directory, I used those to prevent someone from uploading arbitrary files.There is still an issue of brute force password guessing that I haven't decided how I want to resolve yet.
On Monday, April 24, 2017 at 4:16:48 PM UTC-4, David Gifford wrote:It does concern me, though, the level of insecurity of the store.php approach. So I will still eventually experiment more with Noteself. But to be honest I do need the ability to link between files and permalink to share with others.
...Dave
--
You received this message because you are subscribed to a topic in the Google Groups "TiddlyWiki" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tiddlywiki/OCUp73Bads0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/15a32c0d-1bc9-4a0a-8dc4-1f0ba849f031%40googlegroups.com.
To unsubscribe from this group and all its topics, send an email to tiddlywiki+unsubscribe@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/a3f22134-533b-4254-b607-64eb08201c9c%40googlegroups.com.
--
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 tiddlywiki+unsubscribe@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/2b846f3d-0b06-4f1d-9f4a-7b5f4d82b483%40googlegroups.com.
Or just host your standalone files on Dropbox and use https://twcloud.github.io/tw5-dropbox/ to access them. That is another option.
On Wed, Apr 26, 2017 at 1:23 PM, Lost Admin <thelos...@gmail.com> wrote:
For free certificates, you can have a look at both LetsEncrypt (https://letsencrypt.org/) and Startcom (https://www.startcomca.com/) which used to be StartSSL.Startcom uses something similar to the traditional ssl certificate request/validate/get approach.LetsEncrypt is fully automated but you need to have control over the server that the certificate will be used on (to run the agent).
On Wednesday, April 26, 2017 at 11:06:58 AM UTC-4, Mark S. wrote:Hi Dave,
If you have your own server, you might be able to add SSL. SSL requires a certificate, which used to run $100 a year. Some hosts will let you use a shared one that works for everyone on the machine. Or you can generate your own uncertified one. An uncertified certificate will cause your browser to generate alarming messages but you just add them as a permanent exception to your browser and then you're good to go. An uncertified certificate will encrypt your traffic just as well as a certified one, it's just that your browser doesn't have a chain of trust back to the uncertified one.
--
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 tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscribe@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/7bc8e9f8-9f2b-4436-8c63-8872e096fca6%40googlegroups.com.