Open Issues Need Help
View All on GitHubAI Summary: This issue requests a UI improvement to standardize the spacing of the 'Load More' button on the content list page. Currently, its spacing is inconsistent with the individual content items, leading to a less polished user interface. The proposed solution is to adjust the button's spacing to match the consistent spacing used between content items, aiming for improved visual harmony and user experience.
AI Summary: The search results page currently uses Chakra UI's `Highlight` component, which interferes with Markdown rendering when keywords are highlighted. The proposed solution is to switch to using the HTML `<mark>` tag for highlighting. This involves replacing keywords with `<mark>` tags in `content/body.jsx` and configuring `ReactMarkdown` to correctly render these tags.
AI Summary: This issue proposes improving the user authentication experience by eliminating a UI flicker. Currently, the client fetches auth status asynchronously after page load, causing a delay. The proposed solution is to leverage existing Server-Side Rendering (SSR) to determine and inject the user's authentication status directly into the initial page payload, allowing the client to read it immediately upon hydration and removing the need for a separate API call.
AI Summary: This issue aims to improve UI consistency by unifying empty states and the not-found page. It proposes replacing the custom empty state on the `/connections` page and refactoring the `not-found.jsx` page to both use the Chakra UI `Empty State` component, ensuring a consistent user experience. Additionally, the `not-found.jsx` page will be refactored to be a React Server Component for better efficiency.
AI Summary: The current `/verify` page performs client-side verification, leading to security and performance concerns, and lacks internationalization due to hardcoded text. This issue proposes refactoring it into a React Server Component (RSC) to handle all verification logic server-side. The RSC will extract a token from search parameters, call the verification API, redirect on success, and display internationalized error messages on failure.
AI Summary: This issue proposes implementing skeleton screens on pages such as `/publications` and `/connections` to address the problem of blank pages during data fetching. The goal is to improve user experience by providing visual placeholders, making the application feel faster and more polished than using a generic loading spinner.
AI Summary: The "Quote Publication" feature currently renders all `FILE` type posts as simple text links, even when the file is an image. This improvement requests that the system inspect the `mimetype` of the quoted file; if it's an image (e.g., `image/jpeg`), it should be displayed inline using a Markdown image tag, otherwise, it should remain a text link.
AI Summary: This improvement request aims to unify publication access by merging the functionality of the `/redirect?content_hash=` endpoint into the primary `/publications/:id` route. The proposed change will allow the `/publications/:id` endpoint to accept both traditional IDs and content hashes (identified by a `0x` prefix) along with an optional timestamp, with all lookup logic handled server-side to provide a consistent user experience.
AI Summary: This issue proposes a redesign for content cards with `type=FILE` to provide a more distinct and visually optimized layout, featuring edge-to-edge media at the top, followed by author information and then the file description. Additionally, it aims to fix a dark mode bug where the description text for file content displays with an incorrect color.
AI Summary: This issue proposes aligning the terminology used in EIP-712 data structures with the concepts defined in the project's whitepaper, specifically "Proof of Source" (PoS) and "Statement of Source" (SoS). The current implementation uses different terms (e.g., `ContentSignature` for SoS), causing confusion for developers. The request is to rename the `PrimaryType` fields in relevant EIP-712 messages and conduct a comprehensive review for consistent terminology across all related data structures.