On Apr 23 2021 at 9:20 PM, Colby Russell wrote:

Taking this; related to existing work to eliminate references to "static pages" in user-facing docs, etc., in favor of "pinned pages". I should have something to show for this (in terms of changes) next week.

It would be helpful to see when someone replies to one of your replies

Deployed

There is one bug: uploading an avatar and then pressing "Save" erases the avatar_url saved to the user.

The Café covers this basic idea. It only shows posts that have at least one comment, so it's more focused.

Deploying on Write.as soon; WriteFreely PR is here: #531.

This is pretty easy to tackle.

In T883#15281, @matt wrote:

To finish this, we need to be able to indicate that an image is an "avatar" in Snap.as.

Note: these shouldn't show up in the user's Photos.

Implementation came out a little differently: now applications can supply both a key and an id, e.g. avatar and 1, where 1 corresponds to a profile or collection ID. This should make it more usable across our apps, while also supporting Organizations.

To finish this, we need to be able to indicate that an image is an "avatar" in Snap.as.

Just deployed on Write.as, and seems to be running smoothly. The real test will be tonight through tomorrow morning, when we see our normal influx of traffic.

This is more important on Write.as now, especially with replica MySQL databases that have become increasingly laggy.

@heyakyra Yep, we can do that. Was thinking that might be a future task and we would hard-code the term for now, but we can probably make it customizable out of the gate.

Can the /posts be customizable too, so it would be /{custom subpath}/{slug} this way we could call ours articles, and other publishers might call them chapters, stories, etc