TiddlyDrive - Google Drive as store for tiddlywiki community documentation.

[Danielo Rodríguez]

Hello everyone,

I have been developing (and I'm still working on it) a plugin that allows you to save individual tiddlers to Google Drive. There is a lot of things I want to implement, but in its current state it is advanced enough to what I want to propose: collaborative Tiddlywiki  documentation.

This is how I think this can be done (summary): 

• You want to contribute, but you don't have any Github or Node experience
• You visit the page of the project, create or edit a tiddler and click upload to the public repository.
  
• Then anyone can check your work and then an administrator can add to the main wiki page.
• You can even download the wiki so you can make your editions offline and upload them later

The files are uploaded to a PUBLIC Google drive folder, and can be viewed by anyone. Since I have enough space on Google drive there are unlimited tiddler revisions. As I said, this is publicly available for anyone to see, edit or download. The changes are not automatically added to the main page, so this way we can avoid a mess as index page.

This system can be used to create also a public PLUGINS REPOSITORY, this is another topic but I also have plans to implement that.

You can check it here:

danielo515.github.io/TW5-CommunityDocumentation

I think it is clearly explained on the project page, but if anyone have any doubt they can ask here.

Talking about the plugin itself, there are a lot of things that I want to implement. If anyone is interested those are:

• Create tiddlers by email.
• Plugins repository.
• Private tiddler store.
• Control panel for server.
• Save the full wiki html file to the server
• 100% Google drive hosting

What do you think about my proposal? Anyone is welcome to join!!

Regards

[Jeremy Ruston]

Hi Danielo

Congratulations, a great piece of work, and very nicely presented too.

I think we need to play with it and explore it a bit before we adopt it as the official route for documentation contributions.

Best wishes

Jeremy.

--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

--

Jeremy Ruston
mailto:jeremy...@gmail.com

[Danielo Rodríguez]

El jueves, 27 de noviembre de 2014 17:09:50 UTC+1, Jeremy Ruston escribió:

Hi Danielo

Congratulations, a great piece of work, and very nicely presented too.

Thank you

 

I think we need to play with it and explore it a bit before we adopt it as the official route for documentation contributions.

Of course! One of the objectives to present it was to try it out with the community, find possible problems, better ways to work with it.. We don't even need to make it the official documentation, but It can be a good un-official resource.  

[Mat]

I must look into this thoroughly but from what you describe and after a first peek, your set up seems PERFECT for a concept I'm sketching on to have the community easily contribute things in an unofficial way that may, possibly and if good enough, be transferred to a more official place.

I believe these emerging initiatives will have a great (and positive) impact on the directions of TW and the TW community.

Thank you Danielo! This is very exciting!

<:-)

@Jeremy Ruston wrote:

I think we need to play with it and explore it a bit before we adopt it as the official route for documentation contributions.

I think a point with this is that it does not have to be "the" or evan "an" official route for documentation contributions. I imagine these initiatives as adding roads "towards official". I'm in full agreement with you Jeremy that tw.com should be the authoritative place for TW. These other things are, in my mind, best seen as a playground for evolution of things that might eventually make it to official status. We need a lot of these community paths because the community consists of a plethora of minds that work in different ways and have different preferences and capabilities to contribute.

One Rome, many paths. Pax Tiddlum.

<:-)

[Jeremy Ruston]

Hi Danielo, Mat

My observation was triggered by the fact that the project currently describes itself as "Welcome to the Community Documentation project for tiddlywiki5". That doesn't really do it justice; it's a technique with much wider applicability. It also conflates two different things: a cool new way of collaborating on TiddlyWiki content, and a proposal for managing community documentation. I think it would be clearer to present it as the former, with a note that if all goes well it could be used for community documentation.

Best wishes

Jeremy.

 

--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[Danielo Rodríguez]

Hello Jeremy

Feel free to edit such note and add it to the repository 😉

[Jeremy Ruston]

Hi Danielo

> Feel free to edit such note and add it to the repository 😉

Are you serious? I'm writing to you about it here because I can be confident that you will see it, and so that it forms part of the conversation for others to participate.

I'm suggesting that it is confusing to label the project "Community Documentation project for TiddlyWiki5". It may become that, but right now it is a demo of TiddlyDrive. I mean, it's in beta, right? You surely don't want people to spend hours composing documentation edits and then finding that the tool has crashed or lost data. Before we can adopt it for community documentation we need to make sure that it is robust and suitable for the task. With all due respect, that is something for the community to reach consensus on, and not something that any of us can unilaterally assert.

As I say, I think you need to separate the two things:

1) A cool new thing called TiddlyDrive

2) The idea of using TiddlyDrive for community documentation

Another reason is that we already have a proposal to set up a community wiki on TiddlySpace for TW5. That's worked well for TWC in the past, and it's a tried and tested approach.

Best wishes

Jeremy.

On Thu, Nov 27, 2014 at 4:51 PM, Danielo Rodríguez <rdan...@gmail.com> wrote:

Hello Jeremy

Feel free to edit such note and add it to the repository 😉

--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[Felix Küppers]

Hi Danielo,

great idea man. Using google drive as webspace for tiddlers and making the accessible via ajax is such a cool idea!
Really smooth design for upload and download with the cloud icon. great!

I have a suggestion:

The problem is, it is difficult to download tiddlers you created because you will certainly forget the titles. Maybe you could introduce a convention like this:

1. a user enters his/her email adress at some point
2. once the user did so, you send an ajax request to the directory "/<email>/.tiddlers" in google drive.
3. the file contains the names of all tiddlers the user created and uploaded in json
   
4. everytime a user uploades a file, you also update "/<email>/.tiddlers".
5. this way the user can immediately recreate his/her environment.

Felix

[Danielo Rodríguez]

Hello Jeremy

Are you serious? I'm writing to you about it here because I can be confident that you will see it, and so that it forms part of the conversation for others to participate.

 

Sorry but that sounds a little rude to me. The happy face at the end of the sentence means that I'm not serious.

 

I'm suggesting that it is confusing to label the project "Community Documentation project for TiddlyWiki5". It may become that, but right now it is a demo of TiddlyDrive.

Actually the version that I presented is a subproject of tiddlydrive. Tiddlydrive is the conjunction of the plugin and the server side, and the idea to use it for collaborative documentation is a separate project

 

I mean, it's in beta, right? You surely don't want people to spend hours composing documentation edits and then finding that the tool has crashed or lost data.

It is in beta but you should not lost data. The worse thing it can happen is that you can't connect to the server. In that case you can still keep an offline copy.

 

Before we can adopt it for community documentation we need to make sure that it is robust and suitable for the task. With all due respect, that is something for the community to reach consensus on, and not something that any of us can unilaterally assert.

I did not pretend to impose anything. Sorry If it looked like that. Maybe I express myself wit too much enthusiasm.  I just wanted to provide a way to the community to collaborate. If the community is OK with using it, then is cool, if not, then is cool also. I never pretended to make it an official way but just one more way for those who wants to use it.

 

1) A cool new thing called TiddlyDrive

 

I though like that but, honestly, right now I feel a bit pissed off (maybe sad and embarrassed is a better description).

 

2) The idea of using TiddlyDrive for community documentation

Just one more option. 

Another reason is that we already have a proposal to set up a community wiki on TiddlySpace for TW5. That's worked well for TWC in the past, and it's a tried and tested approach.

And maybe that is the best way for an official documentation. As I said, I respect all the options and the choices and I just wanted to give one more option. Seriously, I read several times parts of tiddlyspace documentation and I feel that is a cool tool. I tried to use it several times, but it was too complicated to set up the server, at least for me. I respect it as a robust and better option.

Sorry If I bother you in any way. It was not my intention, and, off course I trust your decisions. You have demonstrated that have a very good sense of how things should be build to stand. In fact you are the author of my very favorite piece of software.

If anyone wants to suggest a better description for the HelloThere I would be very grateful. I'm horrible sumarizing things and giving names.

Peace.

[Felix Küppers]

Hi Danielo
 

Maybe I express myself wit too much enthusiasm.

This is really just a misunderstanding. Don't let yourself down, you did a nice job building such a prototype!

Felix

[RichShumaker]

I am working on a project that this would work great for and I would love to be a 'test' subject.

I have read the documentation and was not exactly sure how to set it up on the Google Side.

Also what is the security process for the user and password to keep it from being hacked.

Let me know privately or post up the process for setting this up if you are interested in more people testing it out.

Really GREAT CONCEPT and awesome job.

Thank you.

Rich Shumaker

[Birthe C]

Hi Danielo

 

I though like that but, honestly, right now I feel a bit pissed off (maybe sad and embarrassed is a better description).

Be happy and enthusiastic, you are creative and have so many good ideas. Your ideas sound good  for cooperation and really we cannot have too many options. To me that sounds really TiddlyWiki typical, options and use it like you want, when you want, to what you want.

Please understand, that you have obviously thought of this Idea for a longer time and in depth, It will take some time for others to totally understand, what it can be used for, and then you tell us, there are even more.

Thank you for taking the time to develop new and exciting plugin.


Birthe

[Danielo Rodríguez]

El jueves, 27 de noviembre de 2014 20:01:41 UTC+1, RichShumaker escribió:

I am working on a project that this would work great for and I would love to be a 'test' subject.

I have read the documentation and was not exactly sure how to set it up on the Google Side.

Hello, that is because I did not write any documentation about that. TiddlyDrive consist (currently) in two parts: The plugin side and the server side. The server side Is a Google apps script published as a web app. The google apps script should be published for "anyone to use". I'm thinking in how to make the server part config as easy as possible. Probably I will end asking the user to make a copy of my script and run some kind of "setup" function. I also have plans to create a control panel to setup the server, so you only have to open the code editor once.

 

Also what is the security process for the user and password to keep it from being hacked.

Currently the security is based in its lack of popularity :P As I said, the script runs as the user that owns it but it should be publicly available for anyone to run it. This is obviously a risk but users can only upload and download tiddlers, but not delete them. Also the application is "sandboxed" and it only operates on a particular folder of your drive and not the whole drive.  I have plans to implement user and password authentication, but this will take some time and in the first version the username and password will be coded directly on the script which code can only be viewed by you and have all the security a private google drive document can have.

 

Anyway, I think there is not much to worry about, I saw this setup several times in many public projects and no one was harmed. There was a lot of crap things because many of them were tutorials and provide live examples, but that was all. The URL of the script is pretty ugly and long and there are not many chances that someone with bad intentions finds it out.

Let me know privately or post up the process for setting this up if you are interested in more people testing it out.

I will let you know when the first private version can be tested. If I don't say anything in a week or two feel free to contact me again.

 

Really GREAT CONCEPT and awesome job.

Thank you.

Thank you for your kind words.

 

[Adrian Sampaleanu]

Really cool and simple to use, Danielo. It's a great contribution! With this, Felix's taskgraph and Jeremy's Cecily, tiddlywiki going to be the ultimate PIM. It's really exciting to witness so much activity around this project.

Cheers

[Mat]

It can already be seen in the top folder that it will become very full and messy. Maybe uploading should automatically place it in an individual subfolder? Perhaps a signature could automatically create a folder titled like the signature. If two individuals use the same signature, I assume it's not possible to have the system tell them apart so uploads would end up in the same folder - but that may not be a big problem, at least not compared to currently when everything ends up in the same folder. And you can't if one signature is one or really ten people anyway. Having folders based on signature we at least have some segregation and it would be easier to find your own contributions.

Can I reach other contributors tiddlers in any other way than via the folder? I.e is it possible at all to reach via the actual TW? I'm guessing this is not possible. But to depend on moderators to approve stuff for inclusion on the TW is cumbersome. How about this idea:

To upload, you must add a signature. As proposed, this creates a subfolder. And the tiddler(s) are added to that folder. The tiddlers are also autotagged with this signature.

In the TW you can tic checkboxes for which 'signatures' you wish to see included. Maybe a left sidebar checkbox list for quick on/off checking for what should be visible.

Taking it a step further, the signature can instead be a topic of some sort. If we're talking about Documentation, the signature could perhaps be Documentation. Or maybe "Documentation on Macros" or other angle. A visitor can then use the checkboxes to have only relevant information appear in the TW.

There could be sub-subfolders. Documentation/Macros/BeginnerLevel for finer granularity. However, this also indicates a problem: Should it be ../Macros/BeginnerLevel or should it be  ../BeginnerLevel/Macros ? This suggests another variant, kind of what is used in gmail for emails: There is a global list, but with filtere-folders based on tags. There is only one instance of each tiddler but there are alos topic foldes created from tags where you find the relevant tiddlers.

I would suggest additionally treating the signature as a tag here. Again, so you can quickly locate your own contributions, but also so you can filter on another individuals contributions. Maybe you're working closesly with some other guys on something.

Note, instead of checkboxes, maybe better with the "tagsplorer macro" in TWC by, was it FND? It's a AND filter that lets you add one tag at a time from a list showing tags that are matching the filter so far.

Why all this? Because we should not need moderator approval at this stage. It's too early. At this stage it is collaboration on (e.g) documentation. You write something and I should be able to build on this right away. Too slow otherwise, hampering development.

There are probably issues with my proposal regarding versioning. We must look deeper into that.

Also, must things not be sandboxed or limited somehow? I mean... what about code that affects the TW itself? Documentation is perhaps rather harmless but what about building up a collection of scripts?

Thoughts?

<:-)

[Danielo Rodríguez]

Hello Mat,

Thank you for all your suggestions. Currently is possible to reach any file by the TW itself. You just have to list all the sub-folders. This is not easily doable right now. For that matter I opened a github ticket: https://github.com/danielo515/TiddlyDrive/issues/2 The idea is that listing the mail folder will give you also the subfolders, and clicking them you can list them.

Your signature suggestion is also implemented IMO. In the main list of tiddlers there is one that ask you for configure your session. There you can define a subfolder. Does this fit your needs? If you download the wiki the subfolder will be maintained as part of your configuration. I know you have tried it.

Currently there is no way to automatically build the wiki. I decided to host the wiki on github for having an easier name. If we host the file on google drive I can write a saver module that saves the whole HTML file back to drive, saving the file as a backup of itself and overwriting the "public" version. Then we have to face the risk that we can overwrite the tiddlers of each other. This is not a problem if you save the tiddlers individually: all you have to do is to download your tiddler from the tiddlers store.

Another option is to load all the tiddlers that are not currently on the wiki asynchronously. This have the risk of eat all my script quota, but maybe is something to try it out.

[Danielo Rodríguez]

I just got an idea: folders should be a special type of tiddler. This way you can make list with them, buttons to query the server, give them custom view templates. For example the view template can be an interface to list that folder. Then the folder can hold who created it in the creator field. How does that sound?

[Danielo Rodríguez]

Hello

I just updated the community edition to the latest version of tiddlydrive, both at the plugin and the server side. I changed the title of the wiki and part of the hello there description to make everyone know this is unofficial and beta. I have to rename the project at github, wich will be done soon. The major improvement of this version is the lazy load of server tiddlers on startup. This means that immediately after the wiki is loaded the server is queried for tiddlers that are on the server but not on the current wiki. The Tiddlers are downloaded as a skeleton, with just the title and it's ID. This way you can search those tiddlers by title and download them if you want.

Check it out!

[Felix Küppers]

Hi Danielo,

the links all give a 404.

Felix

[Danielo Rodríguez]

Hello,

I just renamed the project to TiddlyDrive4Community to avoid confusion. Here is the new url:

http://danielo515.github.io/TiddlyDrive4Community 

I though it would be redirected. But is not :(

[Tobias Beer]

Hi Danielo,

 

I just renamed the project to TiddlyDrive4Community to avoid confusion. Here is the new url:

http://danielo515.github.io/TiddlyDrive4Community 

Because TiddlyDrive will be the actual solution and this one that community project?

Best wishes, Tobias.

[Danielo Rodríguez]

 

Because TiddlyDrive will be the actual solution and this one that community project?

Best wishes, Tobias.

Because TiddlyDrive is a tool intended for single user use and the community edition has the pretension to provide a place to the community to work together building documentation. Regards

[Alex Hough]

Danielo,

Could it be configured to upload to my own google drive?

If so, what would I have to do?

Alex

--

[Danielo Rodríguez]

Hello Alex,

Thanks for your interest

El lunes, 1 de diciembre de 2014 13:51:46 UTC+1, AlexHough escribió:

Danielo,

Could it be configured to upload to my own google drive?

Yes, it is possible.

 

If so, what would I have to do?

You have to run your own copy of the server side and point your plugin to the server URL. At this moment there is no support for username and password control. But I have a couple of instances running under my personal google drive and  I did not find any problem. Both are publicly available and no one is trying to access them. In the worst case you will end up with a bunch of files on your Google drive inside a particular folder. The application is sand-boxed and should not write to any other folder but its main one, but I can promise you any security. If you are interested send my a private message and I will try to guide you on the process. It's not very complicated. But you will have to update manually the server version on future updates.

Regards.

[Mat]

@Danielo

As noted, this is very exciting.
I see one big ostacle for things to be effective; the need for a reviewer of contributions. This is a definitive bottleneck and a typical example of what I think can be solved in more "communal" ways. Compare for instance Wikipedia - no reviewer, yet works extremely well. Not saying we should do what Wikipeida does tho.

What do you think about the following... pipe dream:

Basically: For a documentation topic, there is one prime version, one prime challenger version and "the rest of the challengers". (For the first two, I was considering using the terms "official" and "unofficial" but this could cause confusions with the actually official tw.com documents). This means all contributions are directly viewable, but presented in a certain way:

Contributions climb the ladder from "challenger" to "prime challenger" to "prime" and fill the highest position available. Tiddlers are rated by the community to gain these statuses, perhaps by number of likes or such. In other words the need for review is minimized. Rating contributions also makes it easy to prioritize versions for an information seeker.

The process goes like this: a tiddler that has reached prime has been; first contributed to get into the system, then voted on by community to become the prime challenger and finally reviewed by reviewer to take over prime role from the current one. The one with higest voting after this switch get's to be the new prime challenger.

In other words, the job for a reviewer is minimized. The reviewer only needs to review a new prime challenger vs the current prime. And only when there actually comes a new prime challenger from votes. The community does the main job by just giving likes.

Ok, that was the general process, when there actually is full documentation on something.

If a tiddler is the very first on a topic then this gets prime status right away. No review and no matter how bad. Maybe such single contributions could be set to be editable until locked by a reviewer at some stage. Note it is still available for reading so it contributes value for an information seeker.
If a second version is added, it becomes the prime challenger.

Ok, there are some specific bits and pieces but that's the general idea to not have to rely much on a few individuals.

As understood, all versions of a document are reached in the direct vincinity of the prime. Layout wise it could be e.g a list of tabs along the primes edge and these are sorted by rate. Or it could be a dropdown menu. Etc.

There is a newhere type menu tool to create new versions which marks the created version with an identifier to which prime it belongs. No tiddler is deletable. We will need some way to clean up though, haven't thought that through. Also, on the Drive, maybe it would make sense to place all versions in one folder.

Ok, this relies on voting. Is this doable with TiddlyDrive? I figure it is possible to put up public documents in Drive that can be either freely editable or limited to allow comments but no changing/deleting of anything.

Thoughts? Doable or pipe dream? My main point is to distribute the work onto the community. And from what I can tell, you have most of the things in place.

<:-)

[Mark S.]

When I go to the site and reload the page, it says its getting tiddlers from the server.

But I'm not seeing anything there since the 30th of November. And only one that looks like documentation. Should I be seeing lots of tiddlers at this point, or has everyone been too shy to post?

The technology here is cool, but I'm not sure that it addresses the real problem.

I don't have a problem with git-hub per se, but the fact that everything has to be reviewed and posts don't show up for a week or more is a downer.

Mark

[Danielo Rodríguez]

Hello Mat

Your ideas are very interesting. I decided already to let anyone post on the wiki. I decide this when I though about load tiddlers from the server on startup. Currently only skeletons are loaded. My idea is to implement full load of Tiddlers. The difference between "moderated" and anyone's tiddlers is that the moderated ones are included in the html loaded when you access the Web page and the others are loaded by ajax in a way that I have to determine (on demand? All? Some of them?). The proposal of allowing votes is very interesting also but I think it deserves another additional plugin and more server side code. I have plans to implement the full load of Tiddlers this weekend. Regards.

[Danielo Rodríguez]

Hello Mark

El martes, 2 de diciembre de 2014 17:44:05 UTC+1, Mark S. escribió:

When I go to the site and reload the page, it says its getting tiddlers from the server.

I have to change that message. It should say, listing tiddlers from server

 

But I'm not seeing anything there since the 30th of November. And only one that looks like documentation. Should I be seeing lots of tiddlers at this point, or has everyone been too shy to post?

One? There should be at least 4 tiddlers. We have to face 2 facts here, the first one is that nobody has written anything yet. The other problem is that at start-up the tiddlers are not actually downloaded but only its descriptions, so if you go to the all tab you can see all the tiddlers or you can see them if you search by title. The idea is that you can download them if you want. Maybe it is a better idea to fully download those tiddlers on start-up.

 

The technology here is cool, but I'm not sure that it addresses the real problem.

I'm collecting ideas and experiences to make this better. Any feedback is welcome.

[Mat]

Danielo Rodríguez wrote:

But I'm not seeing anything there since the 30th of November. And only one that looks like documentation. Should I be seeing lots of tiddlers at this point, or has everyone been too shy to post?

One? There should be at least 4 tiddlers.

There are these:
HelloThere
WorkFlow
How does this work?
Configuring your session
...and, under Recent, I can also find: save-all-wo-plugin-sources test

 

We have to face 2 facts here, the first one is that nobody has written anything yet.

You mean nobody has written actual documentation, right? Maybe you could already now permit every tiddler created so they do show, and, if possible auto-tag them with "UserTest" or similar. This would make it easier to see how it is actually supposed to behave plus it would be exciting to see ones own tiddler actually get in there.
 

The other problem is that at start-up the tiddlers are not actually downloaded but only its descriptions, so if you go to the all tab you can see all the tiddlers or you can see them if you search by title.

The idea is that you can download them if you want. Maybe it is a better idea to fully download those tiddlers on start-up.

I thnk merely loading title/description, until actually opening it, is quite ok. On the other hand, at this testing stage I'd say it's better to have them fully loaded so people don't have to deal with issues that aren't really crucial for the whole concept. You can set it back to only descriptions later if needed.
 
<:-)

[Jeremy Ruston]

Hi Mark

> I don't have a problem with git-hub per se, but the fact that everything has to be reviewed and posts don't show up for a week or more is a downer.

I'm afraid that content updates at tiddlywiki.com will always need to be reviewed by a core team member. We're planning to update tiddlywiki.org to TW5 for collaboratively working on community documentation.

Best wishes

Jeremy

--

You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[Danielo Rodríguez]

Hi Mat

There are these:
HelloThere
WorkFlow
How does this work?
Configuring your session
...and, under Recent, I can also find: save-all-wo-plugin-sources test
 

 

 

You mean nobody has written actual documentation, right?

Hello Mat, that is what I exactly mean.

 

Maybe you could already now permit every tiddler created so they do show, and, if possible auto-tag them with "UserTest" or similar. This would make it easier to see how it is actually supposed to behave plus it would be exciting to see ones own tiddler actually get in there.

I'm not a fan of using other tags that the user puts manually. That's why we have the creator field. What is wrong with it?

 

 

I thnk merely loading title/description, until actually opening it, is quite ok. On the other hand, at this testing stage I'd say it's better to have them fully loaded so people don't have to deal with issues that aren't really crucial for the whole concept. You can set it back to only descriptions later if needed.
 
<:-)

I agree, I opened an issue for this 

https://github.com/danielo515/TiddlyDrive/issues/7 

[Mat]

Danielo Rodríguez wrote:

Maybe you could already now permit every tiddler created so they do show, and, if possible auto-tag them with "UserTest" or similar. This would make it easier to see how it is actually supposed to behave plus it would be exciting to see ones own tiddler actually get in there.

I'm not a fan of using other tags that the user puts manually. That's why we have the creator field. What is wrong with it?

My point was to treat every "test tiddler" as actual documentation just to let us sense how things would work if we were using it for real. Or you could maybe copy-paste some real documentation (e.g from tw.com) that people were allow to experiment with. The idea with a "UserTest" tag was just so you could flush out every such tiddler whenever you want. If you go by creator field, you don't know if it is a test or if it is a serious documentation attempt that should be kept. Or do I misunderstand something? Of course, if everything is to be treated as just experiments then no system created tag would be needed.

<:-)

[Tobias Beer]

Hi Danielo,

1) I think the least thing that needs to happen on TiddlyDrive is that when a contributor loads the wiki, he needs to be able to see those tiddlers that he created, whether approved by a moderator or not... ortherwise you're just doing things for neverending nirvana.

So, there you have that authentication problem popping up.

2) Your ControlPanel is essential. Ask users to take a look at it first!

3) Missing functions

— get list of subfolders

4) Workflow

to keep track of edits, a user can create a tiddler for his signature and put all the titles he created or edited and the folders for them into, e.g.

! FolderFoo

!! Created

[[Foo]]

!! Edited

[[Bar]]

[[Baz]]

5) Rather than...

...aspire to try and document TiddlyWiki itself, perhaps TiddlyDrive 4Community should be the place to actually document TiddlyDrive... and there is a lot more to it... and this is also a better focus, if not for now only.

6) I edited shadow tiddlers and they immediately take effect, e.g. DefaultTiddlers ...although not loading the contents, obviously

Best wishes, Tobias.

[Tobias Beer]

Haha, look at the SiteTitle :D

Ah, ok, I thought the server would be showing me the DefaultTiddlers.

But no, it was only the location in my address bar set to permaview.

So, no. Changed shadows do not immediately take effect ;)

Best wishes, Tobias.

[David Gifford]

Wow this looks really cool.

Questions:

1. I saved a tiddler with text, but when reloading the page, the tiddler text just says 'This tiddler is on the server'. How come it doesn't display the tiddler text?

2. Are the tiddlers also saved in the TW file? That is, does the file itself grow, or do the tiddlers only get stored in the drive? That could overcome the limitation of TW5 with regard to images and other large tiddlers.

Just a non-techie trying to wrap my head around this.

Dave

[Danielo Rodríguez]

My point was to treat every "test tiddler" as actual documentation just to let us sense how things would work if we were using it for real. Or you could maybe copy-paste some real documentation (e.g from tw.com) that people were allow to experiment with. The idea with a "UserTest" tag was just so you could flush out every such tiddler whenever you want. If you go by creator field, you don't know if it is a test or if it is a serious documentation attempt that should be kept. Or do I misunderstand something? Of course, if everything is to be treated as just experiments then no system created tag would be needed.

<:-)

My idea was that people usually do test anonymously. Currently you can tag the tiddlers manually if you want. Please keep giving me feedback. 

[Danielo Rodríguez]

Hello Tobias

 

1) I think the least thing that needs to happen on TiddlyDrive is that when a contributor loads the wiki, he needs to be able to see those tiddlers that he created, whether approved by a moderator or not... ortherwise you're just doing things for neverending nirvana.

I agree, and It's planned to load the latest version of each tiddler on start-up.

 

So, there you have that authentication problem popping up.

Not actually.

 

2) Your ControlPanel is essential. Ask users to take a look at it first!

Mmm, maybe I should put more emphasis on it.

 

3) Missing functions

— get list of subfolders

Agree, and it is planned, take a look here: https://github.com/danielo515/TiddlyDrive/issues/4

 

4) Workflow

to keep track of edits, a user can create a tiddler for his signature and put all the titles he created or edited and the folders for them into, e.g.

Maybe the workflow needs a re-factorization to make the idea of setting the username and the folder as the same thing.

 

5) Rather than...

...aspire to try and document TiddlyWiki itself, perhaps TiddlyDrive 4Community should be the place to actually document TiddlyDrive... and there is a lot more to it... and this is also a better focus, if not for now only.

It's a cool idea. I did not put any constraint to the kind of information we can store there.

 

[ceri...@gmail.com]

Up until today I was able access TiddlyDrive without problem. Now I get security complaints and then a 404. What has changed?

Thanks