Hi Everyone > 1) Is there a "definitive" TW (definitive in the sense that it serves as some > kind of master > reference copy for documentation of how TW works -- I'm assuming this is at > https://tiddlywiki.com/
Yes, the docs at tiddlywiki.com (and tiddlywiki.com/dev) are intended to be the authoritative reference docs for TiddlyWiki. The reference docs live in GitHub so that they are in lockstep with the code; one can check out an old version and be confident that the docs will line up with the code. The contribution process to GitHub is indeed too complex for casual users. I’d like to tackle it in several ways: * To take the non-reference docs out of the TW repo, and provide a lower friction path for contributions (eg Google Forms, or a custom server app - see below) * To make it easier to contribute directly to GitHub using something like this new JS library that runs in the browser: <https://github.com/octokit/rest.js <https://github.com/octokit/rest.js>> - users might only visit GitHub to create their account, and then perform everything else through the TW UI We’ve also got some work underway to speed up the deployment process through a continuous integration build server. > 2) Every wikipedia has a Talk page - for discussions about a page. > This seems like a good idea - currently the only way to comment on a page > is to make a better version and send a push request to github -- this seems > a bit awkward I agree that it would be useful for the same reason as Wikipedia. The aspiration we’ve long discussed is to have a federated discussion community based on a mix of P2P tech (Dat/Beaker), centralised services, and personal servers. > Case in point :the SetWidget has an example saying > > > <$set name="myVariable" value="Some text"> > <$text text=<<myVariable>>/> > </$set> > > But the text says name is a variable - but the <<myVariable>> is a macro > expansion. > So here set has defined a macro. The Variable tiddler talks about 'special > types of variable’ The double angle brackets when used as the quotes for an attribute cause it to be interpreted as a transclusion of the raw text of a variable; using the double angle brackets syntax as an element will transclude the variable and also “wikify” it (parse and render it). > What I've wondered, and asked before, is whether it is legal/acceptable to > import the content of TiddlyWiki.com <http://tiddlywiki.com/> into such a > wiki. If not, it would take years to generate comparable material. Absolutely, yes, the documentation content on tiddlywiki.com is licensed under the same BSD license as the code (because we’re treating the docs as part of the code). Remixing the documentation is positively encouraged. > All this is why having a real stand-alone wiki would be so much more > expeditious. But it would take forever to populate if you couldn't grab an > existing information source as a starting point. This is our million dollar question, and has been for some time. Things are changing, though. As I think I’ve mentioned elsewhere, over the last 18 months I have built a scalable TiddlyWiki serverside based on Amazon’s cloud services, called Xememex. For the old timers, it’s like TiddlySpace, except that I can run a batch script and create a whole new instance in just a few minutes. It’s what I’ve wanted to make with TiddlyWiki for many years: a traditional multi-user TiddlyWiki, with user accounts, authentication, access control, and the ability to build lightweight static pages from tiddlers. I’ve funded the development through the consultancy work I’ve been doing through my company Federatial. It’s now reached the point where it could support either or both of our community documentation efforts and our discussion requirements, and we could consider whether we wanted to adopt it. The challenge is that this cloud infrastructure costs money to run; Amazon’s web services are billed by usage, so there’s no charge for an app or site when nobody is using it, but conversely the charges can rise rapidly with heavy usage. The idea of charging users money to participate in the TiddlyWiki community is unacceptable to me (because — duh! — I think I learn so much from the community that if anything I should be paying them/you, and not the other way around). Anyhow, it’s a good time to be talking about this. Best wishes Jeremy. > > Cheers > > /Joe > > > > > -- > 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+unsubscr...@googlegroups.com > <mailto:tiddlywiki+unsubscr...@googlegroups.com>. > To post to this group, send email to tiddlywiki@googlegroups.com > <mailto:tiddlywiki@googlegroups.com>. > Visit this group at https://groups.google.com/group/tiddlywiki > <https://groups.google.com/group/tiddlywiki>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywiki/5a5fcc58-adf3-4ac3-8b27-a38a639346bc%40googlegroups.com > > <https://groups.google.com/d/msgid/tiddlywiki/5a5fcc58-adf3-4ac3-8b27-a38a639346bc%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/E84D6A89-202A-4DA7-9609-6C6ACBD434AB%40gmail.com. For more options, visit https://groups.google.com/d/optout.
