Re: [tw] Re: Federation and TiddlyServer

2017-06-30 Thread @TiddlyTweeter 
Ciao tutti

Mat wrote:
>
>  IMO the perfect use case should be a community "plugin store".
>

I strongly agree. One of TW's great strength lays in customisation and 
anything that can deliver easily *accessible aggregation* to ease the 
process of customisation would be a major plus.

I also think there is a role for extending this process to include Curated 
Bundles (PMario still has The Bundler at early stages, but its more than 
suggestive already) which can effectively deliver an entire application 
setup.

Best wishes
Josiah

-- 
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/3456f769-d09c-46f7-8dc1-a00d58ed35c9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Federation and TiddlyServer

2017-06-30 Thread Mat 
Jeremy Ruston wrote:
>
> The piece that is still missing is support for Node.js wikis to fetch 
> content from other Node.js wikis using the API rather than retrieving the 
> entire html file. (Jed’s robot work might yield a useful start for this).
>


Isn't a missing - but implementable piece - also for single file TWs to be 
able to fetch individual .tid tiddlers from node.js wikis?

...or, are perhaps nodejs wikis really also one file at the stage when 
tiddlers are fetchable?

@Arlen, that might be something TiddlyServer could otherwise enable; i.e if 
single tiddlers are served then they should be fetchable, I think.

(...I also cannot let go of the thought that much more ought to be possible 
with iframes when we're in control of designing the server side and how it 
behaves. I want to be able to at least click on a tiddler link in a served 
tiddler and have it open that tiddler in my local TW...)

...

Further, Jeremy wrote:

So, I think we already have sufficient primitives for experimentation with 
> federation. The challenge has been figuring out a compelling use case and 
> then building a usable user interface on top of it. We started by exploring 
> recreating a conventional threaded discussion forum. The logic was to try 
> to prove that the federation model was sufficiently rich to subsume 
> existing collaboration tools. In practice, common feedback was to be 
> puzzled why we were excited about an inferior copy of something that 
> already exists.


It was also not very 'touted'. Jed (and I) intentionally didn't want many 
participants because of its early dev stage and its obvious scalability 
problems.

However, IMO the perfect use case should be a community "plugin store".


<:-)

-- 
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/eb6e451c-5bcb-4f20-97bd-def8cf428bdc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Federation and TiddlyServer

2017-06-30 Thread Lost Admin 
If I could find really cheap raspberrypi hosting I might be one of them. 
Although i may not count as a true "enthusiast". I only have 2.

On Friday, June 30, 2017 at 5:47:35 AM UTC-4, Danielo Rodríguez wrote:
>
>
> I really think that a mesh network is the best way to go. The 
> beakerbrowser seems like a good thing for regular users that want to 
> contribute. Something that will help a lot too will be to create a 
> tiddlywiki distribution that can act as a node of such mesh on a headless 
> server. *This will allow lot of raspberrypi enthusiast to participate in 
> such mesh*. In my case, I have a couple of single board computers 
> running, I would love to contribute spawning a daemon on any of them.
>
> Regards 
>

-- 
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/e04f21b7-0deb-482b-aa79-5389432d611a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Federation and TiddlyServer

2017-06-30 Thread Stephen Wilson 
'intertwingled'

Good word!

On Friday, 30 June 2017 08:57:12 UTC+1, Jeremy Ruston wrote:
>
> Hi Arlen
>
> The primitive operation underlying federation is the ability to pull in 
> tiddlers from an external wiki, potentially with the ability to transform 
> them as they are imported (eg, to add a title prefix or a tag).
>
> Jed’s work supports standalone wikis to fetch content from other 
> standalone wikis (with some restrictions on matching http vs. https). 
> Rather than using a straightforward xmlhttprequest, it avoids CORS issues 
> by using a mechanism first developed for the implementation of the plugin 
> library: the remote wiki is loaded into an iframe and then 
> window.postMessage() is used to request and extract tiddlers from it.
>
> Earlier this year, I added the “fetch” command which allows Node.js wikis 
> to fetch content from standalone wikis:
>
> http://tiddlywiki.com/#FetchCommand
>
> The piece that is still missing is support for Node.js wikis to fetch 
> content from other Node.js wikis using the API rather than retrieving the 
> entire html file. (Jed’s robot work might yield a useful start for this).
>
> I’m also now interested in an implementation of federation based on the 
> peer-to-peer Beaker Browser (https://beakerbrowser.com). It would allow 
> us to build a community of intertwingled, sovereign wikis without any 
> centralised hosting.
>
> So, I think we already have sufficient primitives for experimentation with 
> federation. The challenge has been figuring out a compelling use case and 
> then building a usable user interface on top of it. We started by exploring 
> recreating a conventional threaded discussion forum. The logic was to try 
> to prove that the federation model was sufficiently rich to subsume 
> existing collaboration tools. In practice, common feedback was to be 
> puzzled why we were excited about an inferior copy of something that 
> already exists.
>
> Best wishes
>
> Jeremy
>
> On 30 Jun 2017, at 08:19, Jed Carty  
> wrote:
>
> What currently exists is almost entirely based on the single file version. 
> Last year Jeremy made the start of what we would need to extend it to use 
> the node version and I am working on some supporting things for my robot 
> that will hopefully help with federation.
>
> -- 
> 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 https://groups.google.com/group/tiddlywiki.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywiki/52cf75b5-62fe-4cd9-a30d-353f198a1a82%40googlegroups.com
>  
> 
> .
> For more options, visit 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/4691da84-134b-47d5-93b0-78bd6305cc49%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Federation and TiddlyServer

2017-06-30 Thread Danielo Rodríguez 

I really think that a mesh network is the best way to go. The beakerbrowser 
seems like a good thing for regular users that want to contribute. 
Something that will help a lot too will be to create a tiddlywiki 
distribution that can act as a node of such mesh on a headless server. This 
will allow lot of raspberrypi enthusiast to participate in such mesh. In my 
case, I have a couple of single board computers running, I would love to 
contribute spawning a daemon on any of them.

Regards 

-- 
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/41d55f62-dd3c-40ea-8b8a-a2ba18e366fc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: Federation and TiddlyServer

2017-06-30 Thread Jeremy Ruston 
Hi Arlen

The primitive operation underlying federation is the ability to pull in 
tiddlers from an external wiki, potentially with the ability to transform them 
as they are imported (eg, to add a title prefix or a tag).

Jed’s work supports standalone wikis to fetch content from other standalone 
wikis (with some restrictions on matching http vs. https). Rather than using a 
straightforward xmlhttprequest, it avoids CORS issues by using a mechanism 
first developed for the implementation of the plugin library: the remote wiki 
is loaded into an iframe and then window.postMessage() is used to request and 
extract tiddlers from it.

Earlier this year, I added the “fetch” command which allows Node.js wikis to 
fetch content from standalone wikis:

http://tiddlywiki.com/#FetchCommand 

The piece that is still missing is support for Node.js wikis to fetch content 
from other Node.js wikis using the API rather than retrieving the entire html 
file. (Jed’s robot work might yield a useful start for this).

I’m also now interested in an implementation of federation based on the 
peer-to-peer Beaker Browser (https://beakerbrowser.com 
). It would allow us to build a community of 
intertwingled, sovereign wikis without any centralised hosting.

So, I think we already have sufficient primitives for experimentation with 
federation. The challenge has been figuring out a compelling use case and then 
building a usable user interface on top of it. We started by exploring 
recreating a conventional threaded discussion forum. The logic was to try to 
prove that the federation model was sufficiently rich to subsume existing 
collaboration tools. In practice, common feedback was to be puzzled why we were 
excited about an inferior copy of something that already exists.

Best wishes

Jeremy

> On 30 Jun 2017, at 08:19, Jed Carty  wrote:
> 
> What currently exists is almost entirely based on the single file version. 
> Last year Jeremy made the start of what we would need to extend it to use the 
> node version and I am working on some supporting things for my robot that 
> will hopefully help with federation.
> 
> -- 
> 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/52cf75b5-62fe-4cd9-a30d-353f198a1a82%40googlegroups.com
>  
> .
> For more options, visit 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/A17B77B5-4F88-4E9C-B81C-30C698927A44%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Federation and TiddlyServer

2017-06-30 Thread Jed Carty 
What currently exists is almost entirely based on the single file version. 
Last year Jeremy made the start of what we would need to extend it to use 
the node version and I am working on some supporting things for my robot 
that will hopefully help with federation.

-- 
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/52cf75b5-62fe-4cd9-a30d-353f198a1a82%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.