Weekly Wiki News

I announce our Wednesday video chat on twitter with a sentence or two of things discussed or even implemented over the week. I started maintaining this list so as to not repeat myself.

We consider "ephemeral content" using wiki types in support of easily curated chat history.

We explore a wiki workflow for creating dynamic content and freezing it for later reference.

For some communities wiki offers a doorway to be entered while for others it is just a hurdle to be jumped. Maybe the difference is what one expects to find on the other side?

Wiki supports many workflows including some unique to our model of sharing. How do these align with underserved human capabilities?

Federated wiki was conceived with five personas in mind: activist, organizer, data scientist, journalist and manager.

We seek plasticity such that all we create can thrive in new contexts.

Activity in the federation spikes after we explore sharing workflows in our Sunday morning wiki dojo.

Wiki now provides more ways for plain html scripts to interact with our Frame plugin.

Computational plasticity might imbue tangled layers of data and algorithms with individual intention to find productive configurations.

If wiki were a database then the scripts we've been writing would be called views.

We've used Scriptable to feed data into wiki from the phone.

Now browsing the federation with 200 line "smallest" federated wiki.

At its core wiki finds pages and finds plugins to render them. We're broadening both searches.

Federated wiki extends sitemap with list of links on every page. Now supports "who links here" that points to the very paragraph.

A headless lineup enables a fresh look at tests for our new implementation.

Wiki is 25, Wikipedia 20, and Federated Wiki almost 10.

Federated wiki's algorithmic drawing follows links from site to site going both ways.

Swarm-like activities can precede conventional reflection and synthesis in new workflows hosted by read-only sites.

As federated wiki becomes more computationally dynamic we find more need to freeze results for posterity.

Wiki's improved graphics supports visualization of complex systems.

The Frame plugin, our version of that old-school sandbox, now interacts gracefully with the lineup for input and output.

Graphviz plays nicer with federated wiki every week.

A new site collects the embedded documentation of 50 plugins making text and examples searchable.

Two new wiki sites collect and run code snippets useful for plugins and 3d graphics.

We explore wiki sites as "team players" in automation.

Javascript at the edge does for infrastructure what federated wiki does at the application level.

We will continue developing a wiki plugin in installments.

Data, graphs and social capital.

We've improved our workflow for cellphone storytelling about place.

We're testing wiki with headless robotic browsing driven by content pragmas.

Coding against integrated functional tests has us feeling young again.

We make plugins to do as much as possible as quickly as possible.

We're developing an incremental approach for importing books into federated wiki.

Wiki plugins discover each other looking left but once connected are free to do whatever works.

We visit a summer "bridge" program for incoming high school students based on methods developed in wiki.

Observable notebook pages integrate well and soon better with the wiki lineup.

We're excited about Deno Deploy's approach to sharing from which we can make a page portal.

Ephemeral page sharing "chat" plugin ready for our Ten Year Anniversary, not yet used.

Tag scanning to replace DOM queries for batch import workflow.

New hypertext to pdf strategies emerging that support a layered approach to organization.

We add application specific scripts to wiki's lineup that decompose and then reassemble causal loop diagrams.

A few pages and html scripts that work together make a "starter kit" for specific use wiki.

A team member can rollup status sprinkled over pages while an administrator rolls up the rollups and visualizes that.

Download to share is emerging as a hands-on way to publish aggregations.

We're reviving image metadata search using our asset rollup workflow.

Can wiki features beyond links help useful structure emerge in large projects?

We've found that we can plot the moments of discovery on a map using squiggles.

Federated wiki can participate with other creative spaces when it gives up some of its special features.

Our newest wiki sites have pages supporting three roles: browsing, authoring, and automating.

Wiki's shared scripted workflows finds host, site and origin serve distinct purposes.

We may continue exploring group decision making at various scales or turn to other wiki dev/user news.

We improve support for wiki's "friends" login as we chafe agains OAuth limitations from internet giants.

We have renewed interest linking old and new wiki now that we have a vision for resolving writing styles.

We like arrows.app and find it happy to work with our software.

When we are successful collecting, sharing and visualizing better data, will we have done anything? Maybe not.

Google disappoints once again, this time with OAuth. In some cases we are finding life better without them.

SVG images from a variety of sources now interact with the wiki lineup thanks to other recently developed mechanisms.

We find our on-page scripts increasingly in the functional style invoking one line const lambdas.

We incrementally and selectively merge system perspectives as a form of query.

The winter break has developers busy posting wiki pull requests.

Our old and new wiki are now loosely joined.

Wiki authors have new tools for modeling and managing attention.