feat: block changes

[iPaulPro]

1. Stops hiding posts and comments from accounts that have blocked the authenticated user

   In my opinion, this doesn't really make sense considering that all posts on Lens are public, and you can simply open a private window or change accounts to view the post.

2. Adds ability to temporarily view a quoted post from a blocked account

   hey-view-blocked-post.mp4

[Copilot]

Pull request overview

This PR aims to change the blocking behavior by removing the hiding of posts from accounts that have blocked the authenticated user, and adds the ability to temporarily view posts from blocked accounts. The changes recognize that all Lens posts are public and can be viewed through alternative means anyway.

Key Changes:

• Removes the getBlockedMeMessage helper function as it's no longer needed
• Updates PostWarning component to include a "Show post" button that allows users to temporarily bypass block warnings
• Implements state management in FullPost and QuotedPost to track when users choose to ignore blocks
• Removes hasBlockedMe checks from the account view page

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
apps/web/src/helpers/getBlockedMessage.ts	Removes the getBlockedMeMessage function that displayed messages when the authenticated user was blocked
apps/web/src/components/Shared/Post/PostWarning.tsx	Adds "Show post" button and accepts setIgnoreBlock callback to enable temporary viewing of blocked content
apps/web/src/components/Post/QuotedPost.tsx	Adds state management for ignoring blocks and fixes typo in variable name (isBlockededByMe → isBlockedByMe)
apps/web/src/components/Post/FullPost.tsx	Adds state management for ignoring blocks in full post view
apps/web/src/components/Account/index.tsx	Removes hasBlockedMe checks and related message display logic from account profile view

Comments suppressed due to low confidence (1)

apps/web/src/components/Account/index.tsx:77

• The hasBlockedMe property is still being used in the Details component to conditionally hide UI elements (follow button, tip button, bio, etc.), but it's no longer being passed from the parent Account/index.tsx component. This will cause the hasBlockedMe parameter in Details to always be false (from the default value), which means users who have blocked the authenticated user will now be able to see these UI elements.

If the intention is to stop hiding content from users who have blocked the authenticated user (as stated in the PR description), then the hasBlockedMe parameter should be removed from the Details component entirely and all checks for hasBlockedMe should be removed from that component as well.

  const isDeleted = isAccountDeleted(account);
  const isBlockedByMe = account?.operations?.isBlockedByMe;

  const accountInfo = getAccount(account);

  const renderAccountDetails = () => {
    if (isDeleted) return <DeletedDetails account={account} />;

    return (
      <Details
        account={account}
        hasBlockedMe={account?.operations?.hasBlockedMe || false}

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.