I hardly ever use TD, so I’m not up at the latest. The following is a post from someone on mastodon, saying that TD creates Chrome/google traffic, and that it is using a broken API for spell check which causes unnecessary traffic.
Possibly someone here with more knowledge would care to address the issues?
Issue created:
I use TD all the time and with some personal content. Would it be prudent to revert back to using a browser until this is resolved?
I would never ever have guessed!
I’m just an end user. I’d assumed there was not anything going on in background—other than explicitly agreed allowed outreach.
I was wrong?
Well im guessing your browser already does this for spell checking.
Oh, ok, thanks.
Does this mean that TD was thought to be offering better security than the browser and in it’s current configuration, it might not be after all?
As I understand it…(I maybe wrong)
As part of browsers ability to check spellings they, apparently, send word data backto the mothership. This is fine. Probably.
People think of TD as a stand alone app which just works on your computer and doesn’t pass any info anywhere, but, as the og link pointed out, because people wanted spelling checking, and TD is basically chomimium browser window, TD now reports text back to the mothership, which is fine, probably, it’s just a bit of a surprise. So I guess, if it’s not there, an option to turn off the spell checker would probably be all that’s needed.
Understood.
Many thanks
Right. Well worth re-saying.
TiddlyDesktop is an app framework with a Chrome browser dedicated to running only TW.
I am one of those People you mention who thought that TD was insular. Searching high and low for a way to disable spell-checking has been unsuccessful. Could you or someone help me to find a way? Many thanks, Morton
I suspect @jeremyruston is aware of the situation and will hopefully get to sorting it when he has a moment or two spare!
@Scott_Sauyet has raised an issue on github so all we can do is wait.