stephancill / opencast Goto Github PK

The 'Add Account' button in the account switcher component maps directly to sign in with warpcast component. Instead, it should map to a modal which lets the user select a method to sign in.

Signer attribution needs to be updated to support indexed on-chain signers.

This will require the database schema to be updated to support the latest replicator, this can be done using Prisma's db pull command. Each signer has a requester FID in its metadata, which points to the application that authorized the signer. This FID needs to be resolved after the signer is looked up in the /api/tweet/<id> API handler and the app's name needs to be passed in the client attribute of the response.

The topics page should be able to load more topics by scrolling instead of only returning the top N topics.

This will also require a change to the cast editor- which is currently downloading all topics and filtering client side - and the introduction of a topics search endpoint in the API

The small screen responsive state of the app doesn't provide access to the search bar. I recommend creating a search page at /search and adding it to the sidebar

A brand new signer keypair is generated on mounting of the sign in with warpcast/ethereum component. This means that if the modal closes for some reason while waiting for the new signer transaction to be confirmed/the warpcast API to respond, the key will be lost.

This key should be persisted with an expiry time and loaded while the expiry time is not in the past. On mount, the component should check if the key in localstorage has been indexed, and if so, should add it to the list of signers and skip the step of registering it as a new signer.

You should be able to browse content without having a signer for the app

Will require view-only states for the components that trigger write actions and might require disabling features that depend on the signed-in user's FID

Pulling down when at the top of a feed should behave like other apps on mobile where it forces new content to be fetched

Instead of unilaterally sorting all replies to a cast by date in the cast detail, cast replies should show author replies to the parent cast above other user replies, similar to other platforms

The mobile sidebar should contain the account switcher component to expose that functionality on mobile

Save a draft of the current cast in the local storage to prevent it from being lost as soon as the cast editor is closed

The draft should be stored in local storage in a JSON object where the key is the hash of the cast that is being replied to so that drafts can support different contexts

It should also be cleared once the cast has been posted

Currently the topics (aka channels) page's icon in the sidebar is a speech bubble. A # is a more widely recognized symbol for what topics represent.

The topic detail page should show some of the top users in the channel based on the amount of engagement that they get on their casts in this channel

This can be implemented in the form of a ?full=true query parameter on the /topic API endpoint and the introduction of a new TopicFull type which returns some extra details about a topic, only to be loaded on the topic's details screen.

The extra details in this case would be an array of User objects, topUsers, which is the top 5 users in the channel.

It can be displayed in the header of the topic detail in a way similar to the 'followers you know' component on the user profile detail/tooltip with the overlapping user profile images