get your refactor/hygience/tech debt proposals in by 12/2, tag them "refactor"

[hannahhoward]

No description provided.

[fforbeck]

• Enable scheduled backups for Dynamodb tables (we already have 35d PITR)
• Move w3cli package to w3up monorepo
• Set default Storacha Gateway for the authorizeGatewayServices in w3up-client.createSpace
• Define filecoin top level capability w3up#1554
• Update the w3 CLI to create the new delegation when a new space is created #196
• Update w3up-client to use the Filecoin top level capability: https://github.com/storacha/w3up/blob/main/packages/w3up-client/src/client.js#L330
• Add resolveDIDKey function type to the UcantoServerContext ucanto#359
• Fix flaky integration test (Egress Tracking)
• Refactor Console to create the recovery account using the latest w3up-client createSpace method
• Refactor Console to share space using the w3up-client: https://github.com/storacha/console/blob/main/src/share.tsx#L76
• w3up-client tests are not executed by the Github action w3up#1592
• Update Freeway to send the egress event to a CloudFlare queue instead of invoking the Upload API directly #192
• Create a feature in the Console App that lets users authorize our Gateway to serve content using the latest w3up-client version (authorizeContentServe function)

[volmedo]

this is the (Go) way!

Go is a very opinionated language and the community has clear ideas about how idiomatic Go code looks like. This has the advantage of removing a lot of bikeshedding when it comes to code style and also makes new code bases more approachable as reading the code is easy and you only need to focus on the logic.

We could make our Go repos more welcoming to new devs by looking for opportunities to make our code more idiomatic. Some examples I came across after working a bit on the indexing-service repo would be:

• use generics only when they add value (some times a bit of duplication is better than complex types)
• define interfaces only when needed

We can decide if getting a full task out of this is the best use of our time, or it's something we can do as drive-by changes when working on other things.

[BravoNatalie]

While working on the w3infra repo, I noticed that the DynamoDB table usage has different implementations across our packages. I believe it’d be helpful to standardize this to make things easier for new developers and simplify debugging. It’s not a top priority right now, but I think it’s worth adding to the backlog.