If graph-store is fast enough, eager storage not necessary

If it isn't, R&D for eager storage

Link Bridge-specific actions as new tabs in Bridge, passing empty transactions (see thread below).

Requires some coordination with infra.

Discussed with @ixv out of band: for better stability guarantees would be nice if publish resubscribes only pulled in content starting at the last timestamp you heard anything happen.

(Marcom wants this for upcoming public notebook.)

I just get a blank white page.

In the console I see this for links:

and this for chat:

Describe the bug
groups: sigil color field is left-aligned on firefox. occurs in both default and group-centric profiles

Screenshots

Desktop (please complete the following information):
OSX Firefox

• Starting with /lib/ folder
• Componentising the /lib/ folder without boundaries work

More intense version:

• Starting with skeleton.js
• Working down through the more top-level components, reorganising as you go

Single concern components, but not composable (not generic; very specific views) — might be worth re-evaluating component organisation

Gavin and I are working on a single-page application rearchitecture of the codebase. It lives on feat/spa. We are starting on a joint merger of Chat, which involves the basics of integrating an API. We will then move onward to migrating the other apps independently.

• Contingent on #40.
• Pending state is a pre-existent loading indicator; after 40, we'd know if it hit our Urbit ship, too and we could surface that.

Dependent upon #20 outcome

• First class citizen apps
• Third parties linking to their own endpoints
• New "landscape" or etc. back-end to wildcard route our first class apps to the same bundle
• FE for this in the SPA

If you try to create a notebook in the SPA, the invites field allows you to select ships, but not groups.

Describe the bug
dojo: scrollbar overlaps popout icon

Screenshots

Desktop (please complete the following information):

• OS X Chrome

Contingent on #49 as first graph-store app.

Describe the bug
props.api is not passed to Settings in publish
To Reproduce
Try editing metadata on settings screen

Describe the bug
comment edit/delete does not work in publish, failing with cannot read property 'action' of undefined

Includes placement for

• Managing S3 keys
• Tile order for Launch
• Serving Publish content publicly

"If I'm running older version of chat-store and it's important to know that" — version number in subscriptions, pokes, updates

Describe the bug
Line height on publish comments is too low

Screenshots

Talking with @Fang-:

• Links and Chat already have on-peeks, but maybe not for stuff web interface wants; however, the logic for writing the subscription's initial logic as an on-peek is guaranteed to be in there already to migrate
• Basically, anywhere we do an initial subscription can be a scry

When Chat opens and gets the first 20 messages from every room — that can be a scry. Clicking on a room and getting the backlog, also a scry.

Metadata can be a scry; loading contacts data for a group can be a scry; getting a Publish post can be a scry.

We would be eliminating "initial subscriptions" in favour of scrying; and then subscribing to updates after our initial scry.

The gains are small at first but would pay off going forward.

Back-end (@baudtack)

• s3-store

• metadata-store

• group-store

• graph-store

• launch

• Might have to double-check to define a mark to json conversions.

• Change subscription paths to updates, instead of initial (src/logic/subscription/global.ts) and call scry instead of the initial subscription.

• In the global.ts you could call scry instead of opening a subscription. You can find the scry function in src/logic/api/base.ts.

• It assumes a certain path. We don't know if that correlates with on-peek yet, but you can see an example in the base-hash scry inside file-server.

Front-end (?)

• s3-store
• metadata-store
• group-store
• graph-store
• launch

• dedupe chat components (header-bar, settings components)
• all text -> text
• high level layout (requires breakpoint changes)

Describe the bug
Setting fields on default identity in groups does not work

To Reproduce
Attempt to set a field on the default identity in groups
The poke appears to go through fine, although the change is not persisted at all.

• Eyre should provide poke-acks when you send it a poke, or subscription-acks when you send it a subscription, such that you can provide all kinds of functionality (sent and delivered indicators)
• Eyre supports it, but channel.js does not support that.

Bargain with @Fang-.

Channel.js lives in pkg/arvo/landscape/js/channel.js.

https://gist.github.com/belisarius222/7c36c61ed7455c5056ef114daa062d1f

Handoff information

Current codebase:

Handled by @timlucmiptev

https://github.com/timlucmiptev/btc-agents
https://github.com/timlucmiptev/urbit-bitcoin-rpc

Work to pick up

• Cleanup code to be idiomatic with userspace architecture
• Plan and implement ability to hand off from Landscape to sign BTC transactions via Bridge (optionally, hardware wallet) — @pkova has started this
• Build interface for wallet via mocks

@tacryt-socryp:

• finishing graph reducer
• integrating graph updates and scry fetching into the current store / subscription architecture
• refactoring UI to use graph data
• finishing graph hooks
• coordinating with Ted to get Links data and subscriptions migrated into graph
• Add archival parameters (see #37).

@belisarius222:

• Writing state adapter to migrate link collections into graph-store
• tombstone links (send archive pokes)
• unarchival functionality (generators to import graphs for the group owner to surface)

Describe the bug
Groups don't show up in publish invite field

Expected behavior
Groups should show up in publish invite field, when creating a notebook

Describe the bug
chat and publish: hide sidebar button does not work, does nothing

Can be closed once all apps have had namespacing improvements.

• back-end migration
• front-end API migration

LA: Links work slightly easier — moving it to push/pull hook library

Chat is to move the option for federation into the push/pull hook

Describe the bug
settings page on publish overflows border on small screen
To Reproduce
Open the settings page on a small screen
Screenshots