bluesky-social / social-app Goto Github PK

The website https://www.socialroots.io/ managed to show a spinner for a long time, as well as an empty state in one case. Make sure this control is consistent!

You can get to profile from your picture, but there should be the word "Profile" that navs you there too.

The photo crop technically works, but it's awkward and unwieldy. I think it's fine to leave crop up to users, but we should try to make it nicer.

My main complaint is it's hard to resize the default square crop box, especially horizontally. Often I'll take a screenshot and pre-crop it down to just the line of text I want. This produces a long rectangular picture, and the default square crop box only gets the very center of it. It's then very hard to drag the left & right edges of the square crop box out to fit my horizontal screenshot.

The other day I deleted a post to re-post a different version (something I do quite often), and saw the old deleted version show up in my feed. When I clicked on it, it gave me a "post not found" message, but still hung around in feed.

Need to replicate.

Two detected issues:

• "e.g." detected as domain
• Filenames ("foo.jpg")

This includes:

• View/screen transitions (always render a skeleton/loading view)
• UI actions (upvote, repost, etc)

In particular, the app needs to:

• Only request permissions when the user is expressing intent to upload a photo
• Inform the user if permissions are not available

Currently pagination is not being provided for:

• Liked by
• Reposted by
• Followers list
• Follows list
• Members list

Tasks:

• Create an embed card by fetching info on the receiver side
• Create an embed card by fetching info on the publisher side (should replace receiver side)
• Include an image in the embed

Photos are unbearably grainy. I'd categorize this as a bug and not an enhancement because it's bad enough to violate basic user expectations of photo quality.

CAR file export tooling should do the trick here.

And an accessible option to do so in settings for the user

_APP-481

This appears to occur when:

1. Edit profile flow is completed
2. Post composer is used

Blocker for app store review.

This requires an update in the PDS and the frontend:

• PDS: Add a route, or update getAccountsConfig, to host these documents. Introduce some config for the admin to set the TOS and Privacy Policy.
• Frontend: Fetch these documents and provide links & a viewing UI.

Do a pass in which the font-sizes are made more consistent and perhaps a bit denser, while also increasing the sizes to touch targets.

The composer needs to embed a view of the reply topic

Saw Feross's bio ends in "..."

This violates user expectations because there's no way to see the rest of it, and no preview that tells you it'll look like this.

Instead, the bio field should tell the user when they've run out of characters, and impose a hard cutoff.

Sometimes scrolling over or clicking on a photo will cause a blank black screen to pop up.

Let's do a pass over fonts, ideally with an external product designer with some expertise here, and refine.

My opinion is that post text is too large relative to name/handle. Can copy Twitter's ratios here. Smaller post fonts allow more information density on the feed.

_APP-478

This appears to happen when loading finishes too quickly, leading the spinner UI to get into a confused state.

Add an image uploader tool to the post composer.

Should support:

• Image cropping
• Up to 4 images
• Ability to remove images from draft after adding

Image cropping can be a v2 if needed.

The bsky.app website needs to host social metadata for content. This means fetching information from the ATP network and hosting it in the page. Doing so enables links shared in other social apps to show a preview of the content.

If the service document fails to fetch during login, it needs to give a screen for attempting to refetch it.

Need tools for:

• Reporting DMCA violations (app)
• Handling the full DMCA report & appeal process (app & admin)
• Applying moderation labels accordingly (protocol)

_APP-477

Post deletion is complete, but currently has a number of issues:

• After deleting, the UI needs to consistently update so that it's clear something has changed. (Eg if on the screen for the post, make sure the view refreshes.)
• When you navigate to or visit a deleted post, the "404" needs to produce an intelligible UI state and not look like an error.

They're a bit easy to miss because they happen too fast

I've looked into this and discovered that text-selection in React Native isn't easy, which is unfortunate. We should either use a custom native element to support text-selection, or we should add an easy flow to copy the full text of the post.

Users usually expect to be able to zoom in and then nav the zoom window around a picture. Ours only zooms in on the center.

Check into techniques for reducing the React Native cold boot time

There's some state that's created during the process of publishing a post with images attached. If the post fails to actually upload, that state conflicts on subsequent attempts to upload.

To reproduce, modify the publishing flow to throw an error right before the post record is created, then try to reupload. You will see an error about a file already existing.

Duplicate posts show up in the feed due to how we handle replies. If there are multiple replies to the same post, we need to figure out how to only show the original post once. Otherwise popular original posts take over a user's entire feed.

I think a post trending in scenes might also get pushed to the feed twice -- there might be more than one avenue causing the duplicate post issue.

null

_APP-482