2019 11 02 - fedwiki & ValueFlows?

The exciting experience of fedwiki. Mikorizal's project of open value networks. Can open value apps have exciting UX?

--- **Boosted email** From: mike hales Subject: fedwiki and OO/P2P protocols Date: 2019 11 02 To: Lynn Foster, Bob Haugen Cc: Dil Green, Oliver Sylvester-Bradley, Strypey Lynn, Bob / Continuing to hack fedwikis . . and beginning to make fewer mistakes now! As I begin to understand the OO/federating principle of Ward C’s architecture, I begin to see the connections with **Scuttlebutt/Holo/Dat/Solid**. And thus begin to wonder whether anything in WC’s architecture has any bearing on what you folks are aiming to build with **Valueflows/RAE** under various protocols. I’m way out of my depth with this codewise and protocolwise . . but wonder whether there’s anything you folks know and can speculate on here? This is the query of a non-hacking user. Who just happens to be a designer/architect.

Has fedwiki ever been mooted in the OAE group, for example? Are the fedwiki folks seen as kindred in that community, or are they a different mob? **OAE = Open App Ecosystem:** webpage

The thing I find most impressive in fedwiki - and it’s the basis of much of the exciting UX that I get - is the way in which all the fedwikis in the world (and all the individual pages, in all the fedwikis) exist as distributed objects (object-farms) and my browser is equipped (thro JSON *app-objects* installed as plugins in my browser window’s workspace, and thro pulled *catalogs* from all the wikis it ‘knows’ of: ’the neighborhood') to process whatever any of them publishes. My browser becomes a self-contained custom factory for operating on anything in the fedwikiverse. And publishing whatever I make. Sounds kinda Scuttlebuttish? Is this Holo rationale too?

What’s brilliant is the way this underlying protocol/architecture combo manifests directly in the UX. Seems to me, this is a quality of UX that you would wish to have in your own Mikorizal **open value network** environment . . every economic actor, maintaining their own object farm (= wiki farm), using tools (plugins) to collate and massage what’s published by every other object farm. Is that anything like the architecture that you in fact operate with? I ought to know the answer to that from your documentation, but haven’t done my homework, sorry ;-) **Mikorizal, value network software:** webpage

Is this just very obvious and straightforward, and if I were a proper FOSS hacker I would already know it? Or this this actually quite hard to implement under any currently widespread protocol - and to make an elegant, dynamic UX out of? Whatever, I have this hunch that the fedwiki solution - protocol + - JSON codebase + - shared (cult?) literacy of federating producer/users within the fedwiki community may hold helpful versions of code, and git-ish working practice, that could be harvested. Mikorizally. Does this make any sense? And sound interesting? Cheers / mike

PS: fedwiki plugins process and publish numeric data as well as text/markdown/html. Draw graphs (maps?), do live calculations, analyse scraped traffic data. Etc. Maybe this is one way to begin developing the democratic/federated/fediversal **data-analytic capability** for ‘wild’/harvested/scraped data that I keep blasting off about, from time to time (as a counter to the centralist secret back-office data analytics of Facebook and the military).

PPS: Copying to Dil. And Strypey and Oli @ OAE. Is fedwiki well known and exploited? Oli, is this related to PLANET? webpage

>Begin forwarded message: From: mike hales >Subject: Re: [NonCorporate.org] Comment: "Understanding the REA / Value Flows model: Lynn Foster of Mikorizal (Part 1)" Date: 30 October 2019 >To: Lynn Foster Cc: Bob Haugen, Dil Green, Silke Helfrich > >Lynn Foster wrote: <snip> >*\[mh] Do you or Bob have a presence in fedwiki at all?* >No we don't. Maybe we'll let you blaze that trail. :) <snip>

>I’m intrigued by fedwiki. It feels much closer to what I need than conventional wiki (or a normal website, or a gitBook), as a place to think out-loud and share and accumulate work and curate a resource base. I love the way Ward C has turned the web architecture upside down - instead of one server, many users, he’s made it many servers (individual wikis), one user, with the integration all happening in the user’s browser. That seems brilliant. And nice coding too, I imagine! A real hack.

>I feel fedwiki can be like a very personal (though public) journal - which is one of the ways WC uses it, to write memos to his future self. I really like that. It can be a hyper-collection of a whole bunch of very diverse stuff. But it presents in a simple, phone-shaped interface, which encourages dealing with things in small chunks. I love all these features.

>However there’s a real geeky set of steps to climb - to open a wiki, to manage a wiki, to correct the errors you make, to manage a farm of wikis or a distributed family of content. WC has an interesting take, on just how easy (or difficult) a really powerful tool ought to be. I resonate with that. But that means it’s not for everybody? So how much effort is it worth investing, building a family of fedwikis? I guess everyone can READ a fedwiki, even if they don’t WRITE them (which is what they really are for). Watch this space. Best wishes / mike