__Publons__ is a website and free service for academics to track, verify and showcase their post-publication peer review and editorial contributions for academic journals.
David interprets the request and the answer as passing each other – from languages that are not connected. In his opinion, it is a (design) mistake to interpret the signal as a statement of fact. This misses the point of wiki. The truth is hidden somewhere in the question, which deserves to be heard more carefully.
This transport takes a Fedwiki Lineup url, and looks at the wiki-page that is furthest right in the lineup - returning a ghost page containing a version of the same page but with a stripped down journal.
We seek to understand the problems our Journal Tools expose. We will dig deeper with some ad-hoc analysis in specific cases.
Journal Checker is a lightweight agent whose sole job is to scan FedWiki pages after we edit them and report structural issues in the `journal` (out-of-order entries, missing create events, impossible revisions). It doesn’t fix pages automatically; it just emits warnings so we can repair the JSON ourselves.
There is currently considerable Noise in the journal. The history reported there is tied closely to the operation of the interface, not the thought processes that lead to that operation. Can intent be mechanically discovered from action?
jon via matrix 
refactor: Journal type alias to an empty record,
A Wiki Page has a journal that records the history of how the page was made and where it has traveled.
Here we look at strategies for cleaning, and processing Fedwiki Journals.
We send a message to the Frame asking it to send us info about the page surrounding it. mdn
Add spacers to the journal for hour ⌚, day ☀, week ☽, month ⚪, season ⚘ and year ❄. Also separate actions with no date data ✇. Add these to Activity plugin headings as a key.
Wiki is an editor. It need not figure out what others have done. It needs only to remember what it has done. That makes reconstructing history easy.
The Journal is a beautiful concept, and an ugly implementation. The fact that it has remained so ugly for so long is a testament to the lack of care taken to the aesthetic of design by software architects. Beauty is in the eye of the beholder as they say, and beautiful code does not render into beautiful pixles automatically.
We ask two questions: can a story be recreated from the journal, and if not, why not.
A collection of tools to help with the identifying pages with problems, and for addressing some of them.