Inspired by Facebook, Tiddles and sharks..... #CreativeOutburstWarning

[Alex Hough]

Dear All,

Tags: #CreativeOutburstWarning

 

"My Tiddles would never dream of using Facebook.... I despair"

!! Could we learn anything from Facebook comments?

In the past I have used them to write "texts" which Iv'e later cut and pasted into TW. Write something, comment on it.... its actually quite efficient. It occurred to me that once I press return a the curser moves into a new comment. Could the behaviour be emulated in TW? And would it be useful.

Maybe this could work in a "note-taking mode", or a "new story mode"

!! Sketch

Below is a sketch of some steps.

# There's always a new tiddler: 

## when "close all", new tiddler at top in edit mode, new story is set

# When a  tiddler is closed, a new one in edit mode appears below

# edit or delete: two stage button, like FB: same number of clicks to delete - do I really want to see edit mode before I delete.... in am in a rush...

Clearly, as a TW devotee I know all the evils of Facebook, but I seem to be using it more and more.... like even people I know and like go on it now.... 

!! Route from FB via IFTT to TW ?

I like the little fish which hang about with sharks, nibbling at the creatures growing on them. (Shark fans in the UK could do worse than search out the shark series on iPlayer -- ive been watching and somehow it made me think of TW)

Instead of making a mode, could I sketch out using already existing form and then refine in TW? 

The issue-- last time I looked into it-- was that IFTT can't be programmed to produce .tid files. Could a command line node.js thingy be run to convert a load of Facebook "tiddlers" feeding on the "shark" find their way home into my TiddlyWiki?

The Basking shark is home to many tiddlers, there are no fleas on the tiddlers.

!! Same  for Gmail

I write a lot in gmail to.... and wikitext has become part of my way of writing {{how I became a gmail junky}}. Looking at it now transclusion is the key aspect of wikitext when automatic writing like {{list of beat poets}}. Maybe {{JK}} would have used a wikitext for his stream of consciousness |texts".

<<.tip [[maybe missing transclusion list would be useful]]>> 

!! TW on the Train

{{TW is great on the train: list of stories}}

!! Turning things on their heads

Instead of thinking TW is small, think it is massive. Don't try to simplify it, its complex now

# TiddlyWiki is not small and simple: is massive. Its a really complex system, more complex than MediaWiki, Facebook ...everything.... (you can't even run FB on node.js, you can't even create WikiText!)

# {{The fittest cats eat scraps from all the tables, not just the top table}} - extending the (mongrel) [[metaphor|Conceptual Metaphors, Larkoff and Johnson]] of the "cleaning tiddlers" -- TiddlyWiki can collect the few valuable crumbs of knowledge growing on the shark.

# the feral stray cat (Movutun Jack) is more resilient than the tiger: whose DNA is  going to be around in 25 years, the .tid file, the single page of HTML or {{The thing that FB does))

Best wishes

Alex

Ps. Find me on FB https://www.facebook.com/alex.hough.50

[Jed Carty]

I completely agree with the facebook comment-like tiddler creation as an option, having it turned on all the time would be a problem, but that is definitely a desirable feature. That is what the fast new tiddler tool that Mat is working on will do, or something similar at least.

The good news is that facebook has (or at least had, I haven't looked in a while) an api for pulling data (posts, comments, likes, etc.) off of their site, and with JavaScript you may be able to get tiddlywiki to pull the data and put it into a tiddler.
The bad news is that facebook changes their api constantly, makes it horribly complex and doesn't write usable documentation. I tried to write something to get tiddlywiki to interface with facebook the way I made it send things to twitter and failed miserably. Their documentation may be designed to remove all joy from the world. I have heard from people who have much stronger backgrounds in JavaScript and related technologies than I do that they have the same problems with the facebook api, so getting it to work will probably require significant effort and luck.

Google does have a gmail api that may let you pull emails from your inbox, and I think that the data is in json format so it would play well with tiddlywiki.

From what I have seen the large social media sites are trying to move away from letting people access their apis for personal use. For most things facebook requires an id that they have to approve, google may do the same thing, so even if we can make this work now I think that there is a good chance that some change in the future would prevent it from being possible.

Even with that problem I would like to find ways to make tiddlywiki play well with everything, even if it is just through something like the widgets twitter uses.

[Alex Hough]

Jed,

I think the long term way / way of getting data into TW (for me) will be from a dropbox using node, not in one step from into a TW in the browser. I think its getting the plain text (written in the wonderful TW wikitext ) "safe" as quick as possible. I think the most resilient gene coming out of TW is the wiki text and how macros and trasculsion have crossed the coder / user barrier. 

I was interested to read an article about producing static websites though a template tiddler (I don't think it was your;s Jed).

I have been thinking about using TW for a new project, hosted on a "proper" URL. For the person familiar with facebook, flicking though stuff on a phone, they don't want to be closing tiddlers when they have read them, I think static sites for from TW is probably going to be the most sensible way of working with folk like this: they are scanning text all the time, swiping the screen, not clicking so much.

Turning it on its head again, a TW site could be static first, then link to tiddlywiki webpages with their own URL. These TW could be small TWs but a more detailed and linked part of the static. The reader gets supper simple HTML first, then can get the detail.... a comfortable ride though the complexity.

propperurl.com/hello-there.html -- static page

propperurl.com/hello-there/tw.html -- tiddlywiki from which static was generated.

I am staring to think that to be readable by a non TW user, static sites are the way to go... at least for the "first scan"

Alex

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/4c912725-bb80-4d9f-90aa-02c51fe20cdb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.