Hi Poul
At last I managed to make tws (with noide.js) run/startup as a service on
my linux boxes.
It's great to be able to create and save TWs without any hazzle whatsoever
:-)
Thanks a lot for making this available - for all platforms..
I don't think there are any security problems to worry
Hi Poul
At last I managed to make tws (with node.js) run/startup as a service
on my linux boxes.
It's great to be able to create and save TWs without any hazzle
whatsoever :-)
Thanks a lot for making this available - for all platforms..
I don't think there are any security problems
Hi Poul
I run into problems with malformed text when I create a new document
with danish characters in it:
Same thing happens when I save an already existing document with
danish characters..
What can I do to make it work?
http://tinyurl.com/9k9vz3r
Cheers Måns Mårtensson
On 18 Okt., 10:20,
That's a lot of stuff to set up.
At this point, TW is no longer the light-weight, run-anywhere personal wiki
solution. There are already information and wiki systems that can run on a
USB stick with no install and no significant memory restriction. For that
matter it would be easier just to
someone to develop a TW plugin that will reduce security restrictions on
specific TW files that you indicate.
There is NO WAY to reduce security restrictions via a TW Plugin.
The Firefox methods for gaining local filesystem privileges have been
deprecated. As of FF15, they have removed the
On Fri, 19 Oct 2012, Mark S. wrote:
That's a lot of stuff to set up.
That's part of my point. It looks complex, and to some extent it is,
but it is considerably less complex than what is happening under the
covers when you do something like install a web browser. The
difference is that the
On Thu, 18 Oct 2012, Poul wrote:
I certainly sympathize with Chris's disappointment in the ability of
server-based TW solutions to gain developer support. But then, I am not a
Python believer, and if I were to invest a serious amount of effort in the
problem, I would most definitely go the
I don't think there are any security problems to worry about in using
node.js for a server as long as it listens only on 127.0.0.1 (the loopback
interface), as it is not exposed to outside connection.
But as the browsers are becoming increasingly unhappy with java applets, I
do believe it is
I certainly sympathize with Chris's disappointment in the ability of
server-based TW solutions to gain developer support. But then, I am not a
Python believer, and if I were to invest a serious amount of effort in the
problem, I would most definitely go the Node.js path. As it is, I am more
On Oct 16, 1:49 am, Mark S. throa...@yahoo.com wrote:
No one provided a realistic solution other than to suggest a web server.
The web servers suggested were large. After that I kind of lost interest in
TW.
This seems an opportune moment to remind folk that using TiddlyWeb +
TiddlyWiki doesn't
This is exactly why I wrote TWS (besides getting a feel for node.js). It
actually already has a mention on TW.com, but in the context of hosted
options, which is not really it's raison d'etre.
The way it works does of course break with the accepted paradigm of how you
work with documents on
Two and half years ago I asked what the future for TW was, given that
browser manufacturer's were trying to shut down the back-doors that allow
TW to save to the local hard drive:
https://groups.google.com/d/topic/tiddlywiki/5AS-lPmTCbw/discussion
No one provided a realistic solution other
12 matches
Mail list logo
