I'm pretty sure, you did discuss these concerns allready. So I'll post here, instead of a wider public.
I think having the websocket is cool stuff. I can think about serveral features allready. Question first: Is it planned, to have a ServerSetting that lets me (per space) "opt out" of the public live stream? At any other service I use, I highly appreciate "opt in" as a default setting. Since I did/can set my default bag to "_private" I'd accept the "opt out" option with TiddlySpace. ===== This is just a thought experiment / "gedankenexperiment". If no "in/out" option is provided, I can think about some cool and evil stuff too :) It seems to be quite easy to listen to newly created tiddlers of all users. Just several lines of js. So let's say, one creates a little browser based program, that just listens to the live stream. If a new tiddler address comes in, one fetches a full text version of this tiddler and writes it to a database. After some minutes, one uses this database to have a look, if these tiddlers, still exist. If not, consider them as private and mark them for further processing. further processing: Full text search for keywords, that could be interesting if something found, mark them as interesting. Since TS traffic isn't that high, the number of interesting files, shouldn't be that high. So it may be even viewed by a human. ===== I know, that nobody would accidentally save "privat" data in the "public" space and than change it back to "private". But what scares me, is that machines probably will be faster reading my stuff, than me making it "private" again. just my 2 cents -m -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
