Easiest and privacy concerned way to publish online for a single user

[Mario Public]

Dear All

I wish to to have my TiddlyWiki online for easy access from every device/location.

I am the only user of the TiddlyWiki.

I am using the google drive extension and it works but I would prefer not to host personal files there. Nothing particularly sensible, just personal.

What is the easiest and most private way?

I have my own domain and I tried to host the wiki there by uploading it and using store.php but I got errors and it did not worked.

Is dropbox a better option?

Thanks

Mario

[Mat]

Hands down, tiddlyspot is the simplest solution. And the easiest way to set one up is probably here: http://tiddlywiki5.tiddlyspot.com/

Other than "not giving out your url", you can restrict access to it by going to http://yourtiddlyspot.tiddlyspot.com/controlpanel

It is probably not *secure* but if your data is merely "just not for others" then I'd definitely say it's fine. I use it exactly like this myself.

<:-)

[Mario Public]

Dear Mat

Thank you! I will give it a try!

Mario

[Mark S.]

As an aside, how are people using Google drive now?

The link for google drive on TiddlyWiki.com leads to a 404 page.

The link on tiddly toolmap leads to a chrome store. The problem there is that the reference site

(http://lordratte.info/tiddlydrive/) leads to two warnings from ublock including one for badware. When

I push on through, I get popup advising me that by agreeing to "accept" I will have the chance to change to a "safer"

search on Firefox. I don't like this. This seems dowdy, scam-y  and possibly dangerous.

So, what do we know about the provider of the google drive extension? Or is there some other undocumented approach people are using?

[TiddlyTweeter]

Mark S., 

Right. I think the oomph of that post is that we kinda get into trust issues on cloud dependencies not in a TW fold. I think that may get worse over time.

The problem is becoming the "supplicant daughter" who has to accept poor information, rather than a robust proven protected TW nest.

The issue of how external storing dependencies work matters I think.

Thoughts

TT

[Mark S.]

I actually trust Google to do it's job. I expect they know more about security than hand-made PHP locations.

What concerns me is the intermediary software that connects to Google, about which I know nothing, and

which has a reference address that questionably offers to change things on my computer BEFORE even

allowing me to the target site.

[TiddlyTweeter]

Right. But from end-user point of view the chain of connect matters. It is only as good as the Weakest Link. 

[Mario Public]

Good obseravations.

Just to update:

I was able to create the tiddlyspot site using the site referenced but only on Chrome. Firefox failed at last step.

The site is working but not from my android phone, differently from the google drive extension.

The safest way would be to store the TW on my hosting website space, but I was unable to to do that (changes are not saved).

Mario

[TiddlyTweeter]

Mario Public wrote:

I was able to create the tiddlyspot site using the site referenced but only on Chrome.

RIGHT. It fails of FF on creation. After it should be okay on FF.

TT

[TiddlyTweeter]

Mario Public

The safest way would be to store the TW on my hosting website space, but I was unable to to do that (changes are not saved).

Just FYI, I  use local save with follow on auto-FTP to do it.

IMO if you have a site, use it. It is better addressing. There are various solutions if you need live save to Web. I never used them personally. I found FTP fine.

TT

[Mark S.]

store.php needs some tweaks to match changes in PHP. They are mentioned at the bottom of

https://tiddlywiki.com/#Saving%20on%20a%20PHP%20Server

There's also a newer PHP saver:

https://github.com/sendwheel/tw-receiver

Haven't used it, but at least it's been updated.

But I wouldn't think your own site is the safest option, unless you're well versed in security issues.

My concern about the google drive solution is that I don't know who makes the web extension, and their reported reference site appears dodgy.

Other possibilities include using the github saver on a private repository.

You can also use syncthing to synchronize your devices on your own network and then use whatever

works locally for saving (e.g. PMario's file backups).

[Thomas Elmiger]

Hi Mario,

One more option, in contrast to TiddlySpot running under https would be Gitch. See
https://nota-bene.glitch.me/

Good luck!
Thomas

[Mat]

Mario Public wrote:

I was able to create the tiddlyspot site using the site referenced but only on Chrome. Firefox failed at last step.

Yes, that is a known quirk (noted halfway down here). But it is only for the first creation of the wiki. Thereafter things should work as usual.

 

The site is working but not from my android phone, differently from the google drive extension.

In what way does it not work? 

<:-)

[Mario Public]

Il giorno venerdì 6 marzo 2020 22:20:38 UTC+1, Mat ha scritto:

In what way does it not work? 

Apparently changes are saved but they are not. If I browse the wiki from the PC or I restart the browser in the phone, they are gone.

The same from an Ipad

Mario

[Mat]

Mario Public wrote:

Apparently changes are saved but they are not. If I browse the wiki from the PC or I restart the browser in the phone, they are gone.

The same from an Ipad

I'm probably stating the obvious but: There's a separate saver for tiddlyspot natively built into TW. Make sure you've set your password there.

<:-)

[TonyM]

Mario

My solution would be to use tw-reciever in its own folder and use the server to make that folder secure. To see any files in the folder you will have to login to the server. That's your privacy. Then in tw-reciever you have to provide the credentials to save the wiki.

Then if you use a password vault like last pass login and save the login credentials.

This will do as you wish. The only hassle is needing a userid password and tw-reciever credentials to login from elsewhere since the bigger a password the better. That's why I suggest a password vault.

Regards
Tony

[Mario Public]

Gosh..I feel so stupid! I was not thinking that it needs to be set in each device.

Actually it work now!

Thanks!

Mario

[TonyM]

Great,

Did you protect the folder with a user ID or password?, other wise people can access it with the url?, and any error on the folder above could make the url visible.

Regards

Tony

[Mat]

Gosh..I feel so stupid! I was not thinking that it needs to be set in each device.
Actually it work now!

LOL! ;-)

TonyM wrote:

Did you protect the folder with a user ID or password?, other wise people can access it with the url?, and any error on the folder above could make the url visible.

No "folder" when using tiddlyspot so the way to protect it is via restricted access as set in:

http://....tiddlyspot.com/controlpanel

<:-)

[TonyM]

Mat,

Thanks for adding that for tiddlyspot, to be clear I was recommending the PHP server solution which has folders that can be secured.

No "folder" when using tiddlyspot so the way to protect it is via restricted access as set in:

http://....tiddlyspot.com/controlpanel

Regards

Tony 

[Beckstrom]

FWIW my approach is this:

- I use the node.js Tiddlywiki server so I can access it from any device. This is running on a Digital Ocean VPS

- I use nginx as a reverse proxy, directing requests to "mysite.com" to the tiddlywiki port

- Also in nginx I have access to that URL restricted to only localhost (only requests from the server itself can view my wiki) and my home IP address

- I also run a VPN server on that machine

- So when I'm at home, I can just connect like a normal website

- When I'm not at home, I connect to the VPN and I can connect to the website

I hope that makes sense! Perhaps a complicated solution, but it works well for me

[Mario Public]

Thank you Chris,

This is also interesting. I have a Raspberry PI model 2B+ taking dust and maybe I can try to set it for this.

I do not know if I am enough expert but I ready to learn.

Regards

Mario

--
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/C8qyvM1MSG0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tiddlywiki+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/8faae383-7f77-4b23-a97a-3f6c5795cb8d%40googlegroups.com.