Neighborhoods, AD4M/Flux, and The Weave all do similar things. I know it's frustrating. I've got a group that wants to use these tools and each time we look into one, one of the others pops up again to investigate. This is a period of time with DWeb where there will be lots of different approaches to experiment with. At least there is some cooperation and collaboration. I've been told that Flux my incorporate a Weave browser similar to Moss in its tools, and/or make Flux components available in the Weave
I thought the same thing, so I'm glad @stevenmorris5562 replied here. Even if Holochain is a means of creating a weave or a neighborhood or a flux, these groups created viewers for their Weave, for their Neighborhoods, and for their Flux, each of which has different user models. When I see SecureScuttleButt as a protocol, I see manyverse as a viewer for the structure created upon that protocol. This is likely why I don't need to run a Holochain server to use The Weave via Moss, I could run my own Weave on my own Holochain server and change the urls I put in Moss, if I understand this all. I know "who's in" can already be implemented just via one web interface, so it may be possible to reverse proxy any of these other Moss apps, when authorized, to a specific web host. 🤔 This seems more accessible to devs, and as a abstractable to users as they wish. (time to make sure about this in the Holochain discord for now :)
Suggestion rather than building tools .... why not build a "container type" app that allows the import of any Holochain based happ into Moss🤔So for example.. this demo vdo would not be using Vines but would use Relay as its chat Happ and select it from the Holo store. Once selected on store Moss would incorporate the chat Relay function. I recognize this may need re-engineering the structure and development of Happs but wouldnt it be fantastic ... the benefits we were all sold of object orientated programming coming to life👍
🚀
Juiiiceeee!!!!
Its working👍
I'm confused, isn't this what Neighbourhoods does? Are we fracturing already?
@@parodoxis Yeah, I'm wondering about that too
Neighborhoods, AD4M/Flux, and The Weave all do similar things. I know it's frustrating. I've got a group that wants to use these tools and each time we look into one, one of the others pops up again to investigate. This is a period of time with DWeb where there will be lots of different approaches to experiment with. At least there is some cooperation and collaboration. I've been told that Flux my incorporate a Weave browser similar to Moss in its tools, and/or make Flux components available in the Weave
I thought the same thing, so I'm glad @stevenmorris5562 replied here. Even if Holochain is a means of creating a weave or a neighborhood or a flux, these groups created viewers for their Weave, for their Neighborhoods, and for their Flux, each of which has different user models. When I see SecureScuttleButt as a protocol, I see manyverse as a viewer for the structure created upon that protocol. This is likely why I don't need to run a Holochain server to use The Weave via Moss, I could run my own Weave on my own Holochain server and change the urls I put in Moss, if I understand this all.
I know "who's in" can already be implemented just via one web interface, so it may be possible to reverse proxy any of these other Moss apps, when authorized, to a specific web host. 🤔 This seems more accessible to devs, and as a abstractable to users as they wish. (time to make sure about this in the Holochain discord for now :)
Suggestion rather than building tools .... why not build a "container type" app that allows the import of any Holochain based happ into Moss🤔So for example.. this demo vdo would not be using Vines but would use Relay as its chat Happ and select it from the Holo store. Once selected on store Moss would incorporate the chat Relay function. I recognize this may need re-engineering the structure and development of Happs but wouldnt it be fantastic ... the benefits we were all sold of object orientated programming coming to life👍