Skip to content

Export Tisty - #23

Open
rgdevment wants to merge 8 commits into
mainfrom
feat/export-tisty
Open

Export Tisty#23
rgdevment wants to merge 8 commits into
mainfrom
feat/export-tisty

Conversation

@rgdevment

Copy link
Copy Markdown
Owner

No description provided.

A store signs itself once with an alias that
  lives in its own log, and every document is sealed with the name in force when it was written: changing the alias later leaves yesterday alone and
  offers, once and by hand, to re-sign what came before. What arrived from somebody else keeps their name whatever you call yourself, coming home under
  your own name is not coming home a guest, and the guide is signed by Tisty. Archiving a document closes it to writing, from the window, the terminal and
  an assistant alike.
… a stranger

The cache keeps the signature, so
  reopening no longer forgets who you are. Every document carries the alias it was written under inside its own event, which makes authorship independent
  of the order two machines happen to replay in, and re-signing a document is no longer marked optional because dropping it would show two different
  names. A parcel is judged by the store it came from and not by the name written inside it, so one from somebody who never signed lands without an author
  instead of under yours. Archiving closes a document to writing through its own door, leaving the lock to mean what it meant: syncing stops calling
  every archived document a conflict. The manifest's own names now go through the door every other name goes through, it is read under a ceiling, and what
  cannot be carried is counted rather than dropped in silence. The docs say all of this, including what a name in a parcel is worth.
…where it goes

Export and import speak the way
  they always did, for Tisty and from Tisty, and Settings offers them beside the backup rather than only behind a right click. What goes out and what
  comes in are counted the same way, singulars included, and a partial success says how much made it instead of a red line without figures. The notice
  about the alias no longer claims it travels inside a plain markdown file, because it never did. A document that arrived from somebody else says so in
  the list, and the PDF preview shows what the PDF will hold.
…wards

A document said it was edited by whoever
  happens to be signing now, so one brought in from somebody else claimed your name without you ever opening it. The note a save writes carries the alias
  it was written under, and the card reads that. An alias this store signed with before reads as the one it signs with now, because it is the same hand;
  anybody else's stays theirs. The author still moves only when you re-sign what is yours, and only when the alias actually changed. Away from the window,
  a store written by a newer build now says to update rather than only naming the schema.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant