TW Obfuscation for Sharing+Debugging

Diego Mesa

unread,

May 31, 2019, 2:25:09 PM5/31/19

to TiddlyWiki

Hello all,

Im very interested in debugging my TW, but dont want to share all of my data. In order to share as close to "As is" as possible, Im interested in "obfuscating" it. Note: I dont mean this in a real cryptographic/provable sense - more just practically.

I think a simple system would just replace every word/title/link in your TW with a random string, perhaps of equal length (or not), while maintaing correct inter-linking. That way, we can more easily share/debugg TW and/or plugins.

Has anyone developed something like this?

TonyM

unread,

Jun 1, 2019, 2:59:11 AM6/1/19

to TiddlyWiki

Diego,

I have not seen anything like this, and in my view it would be better for you to build a test data set, that the macro / plugin you have a problem with and import that to an empty.html or TiddlyWiki.com to reproduce it. You will possibly solve the problem as you do this anyway. Keep in mind you should be able to reduce the possibilities of where the problem lies before you set up the test data, thus reducing the effort to set up the test data. Your ability to reproduce the error on another wiki is a good step to take.

Depending on your setup, Perhaps you could force dummy text into tiddlers (text field) and list all tiddler titles, scan the list with your eyes, renaming those with information in them, do the same for all tags. There are some batch tools that should help with this.

I know this is not answering your request. Sorry, Its just I think it the wrong approach, however your case may be different. Best of Luck.

Regards

Tony

PMario

unread,

Jun 1, 2019, 6:16:18 AM6/1/19

to TiddlyWiki

Hi Diego,

I absolutely second every word Tony wrote. ...

Your desire to create a copy, that is as close as possible, to your real world wiki is understandable, but you have to be aware, that "on the other side" there are people, which have to debug your wiki in their spare time. The more complicated that is, the more time consuming is it.

That's why developers like "easy to reproduce" test cases. ... And as Tony wrote, ... when you create the testcase the chances are high, that you see the problem yourself.

If you need a code snippet, that allows you to create a big number of tiddlers ... "Follow the rabbit hole".

You probably can modify it, that it meets your needs.

If you visit or load a TW site, you can activate a JS scratch pad with shift-F4

have fun!

mario

TonyM

unread,

Jun 1, 2019, 8:52:36 AM6/1/19

to TiddlyWiki

Diego

Another thought is share screen shots or video prepared without your confidential info. Hopefully your macros and code is not too intertwined with your data.

Best
Wishes
Tony

@TiddlyTweeter

unread,

Jun 1, 2019, 10:45:11 AM6/1/19

to TiddlyWiki

PMario wrote:

If you need a code snippet, that allows you to create a big number of tiddlers ... "Follow the rabbit hole".

That is a powerful concept--Rabbit Hole--I assume you thinking of Lewis Carrol's writing? https://www.youtube.com/watch?v=5Z12-A88tHU

Not entirely OT.

My question is this: WHERE does Diego go already to get perspective on this Testing Issue?