Trying to fetch all messages or all blogs will pretty unfailingly give me 
the red screen with something about iframe.

I think it is hiccuping because it's reading my own card, but not sure. 

Is the "-" on the various view messages supposed to allow you to see all?  
There doesn't seem to be any practicable way to see all messages at once. 
Trying to review every to/from combo would quickly become unsupportable.

In the posts section, I'm finally able to see activity from Jed's test 1 
and Birthie. I've posted comments. I've also posted two blog entries, but 
haven't seen any comments. Then again, maybe I don't know how to fetch them.

In the post view section, having to select every author in order to check 
if there are new posts will become tiring when there are more than a 
handful of authors.

Good luck!
Mark

On Wednesday, May 25, 2016 at 1:28:48 PM UTC-7, Jed Carty wrote:
>
> At the moment everything is ready but automation and documentation. If you 
> want to poke it and see what happens I have the most recent version here 
> <http://ooktech.com/jed/ExampleWikis/TWederation/>.
>
> To make up for the near complete lack of documentation, here is a quick 
> run down of how it works:
>
> Make a copy of the wiki wherever you want your TWederation wiki to be (or 
> just put a wiki there and import the plugins, all 4 of the plugins that 
> start with $:/plugins/inmysocks/TWederation-)
>
> Fill out the form that appears as the default tiddler 
> ($:/plugins/inmysocks/TWederation/Initial Configuration/Create twCards) and 
> click on 'Create twCard' at the bottom. Then go to to the Communication (in 
> the table of contents tab on the right)
>
> In that tiddler, go to the Fetch Communication tab, next to What to Fetch 
> select All Wiki twCards and next to Select Wiki select TWederation, ignore 
> the other things and click on 'Request Bundle'
>
> In a moment there should be a link under the Request Bundle button, open 
> that tiddler. In that tiddler click on Unpack All
>
> Then in the Communications tiddler change What to Fetch to All Identity 
> twCards and click on Request Bundle again, a new link will appear in a 
> moment (so now there are two of them), click on the new one and click on 
> Unpack All in the tiddler that opens.
>
> You now have what you need to leave or fetch messages from whoever else 
> has been listed. It may just be me.
>
> Then in the fetch communication tab you can switch to blog posts, messages 
> or whatever you want to try fetching. Under the other tabs you can view 
> messages or posts or make posts and leave messages for other people.
>
> Note I said 'leave' not 'send', this is a distributed system, not a 
> client-server architecture. So you need to fetch messages or posts from 
> people and they need to fetch them from you. In the future that will be 
> automated so there will just be a 'check message' button that will get them 
> for you.
>
> You can fetch the twCards from TWederation again later to check if other 
> people have been added. Right now without the automation it is all a bit 
> tedious, but it works.
>
> Some other notes:
>
> When you make the twCard at first it also sends an xmlhttprequests that 
> submits some information in a google sheet so that I can then retrieve that 
> data and make the twCards from it. So I have made a widget to submit google 
> forms and one to retrieve data from a google sheet. Unfortunately they 
> aren't very flexible at the moment so if you want to do something else with 
> them you will have to play with the code a bit.
>

-- 
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 [email protected].
To post to this group, send email to [email protected].
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/e8e8595e-3149-499f-9b53-f2ceb75995da%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to