-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: simplify archived post indicator #7466
base: main
Are you sure you want to change the base?
feat: simplify archived post indicator #7466
Conversation
Also see discussion on #6707 |
I concur that this update to the poor current experience has been highly sought after by those of us who had our Twitter history migrated over. It does an excellent job of maintaining a visual cue that a record is imported but corrects the date indexing / sorting problem that the current backdate implementation introduced. Please consider this a strong plus vote. |
@estrattonbailey @mozzius Apologies for reaching out directly but would love your consideration for getting this PR merged? |
Fixes #6707
Proposal
This PR has been raised as a follow up for #6156
Whilst I appreciate the potential necessity to indicate whether a post has been backdated in the past, when the above feature was added this did then conflict with the way I personally use Bluesky (and previously X/Twitter) as a microblog diary of my family life etc. Having bulk loaded all my old Twitter (and Facebook) history into Bluesky I was keen to maintain the original dates and scroll back chronologically to read them.
This is a proposal for a kind of half-way solution where, rather than having two dates appear on a post, we only show one (the 'createdAt' date) but make it more obvious (i.e red) that is is not the original 'indexedAt' date. Not only does this mean the post looks less cluttered, but I think it is more obvious.
Changes
Example screenshots:
Current Post:
Proposed Post (consolidate down to 1 date):
Archived Message (remains the same):
Non-Backdated Post (remains the same):
Current Feed (shows indexed_at date):
Proposed Feed (shows created_at date):
I appreciate this is somewhat undoing the previous feature, but I just wanted to raise this PR if only for discussion as to the impact to my diary kind of use case for Bluesky. See my profile for example where you will see my diary (imported from Twitter) going back to 2003 by all posts at the moment now mostly all say '2mo' (2 months).