You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As seen in the image below, the timeline flows upward for days, but within a single day, the order of ingestion times flows top-to-bottom. I understand the design choice so maybe I'm alone in this, but it feels inconsistent and confusing to me at least.
The text was updated successfully, but these errors were encountered:
I see what you mean and dont know a better way to do it because I think its intuitive that the ingestions are sorted top to bottom but if experiences were also sorted top to bottom that means the oldest and least relevant experience would be on top and users would have to scroll all the way to the bottom to see it. Usually people like the scroll content like feeds, notes, ticktocks etc towards the bottom with the most relevant thing on top.
As seen in the image below, the timeline flows upward for days, but within a single day, the order of ingestion times flows top-to-bottom. I understand the design choice so maybe I'm alone in this, but it feels inconsistent and confusing to me at least.
![Screenshot_20241221_140945_Journal.jpg](https://private-user-images.githubusercontent.com/68711133/397929658-349cff9b-5d03-4901-8a12-2c90c8a11684.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkzODczNzYsIm5iZiI6MTczOTM4NzA3NiwicGF0aCI6Ii82ODcxMTEzMy8zOTc5Mjk2NTgtMzQ5Y2ZmOWItNWQwMy00OTAxLThhMTItMmM5MGM4YTExNjg0LmpwZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEyVDE5MDQzNlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWRhZGQ3NWUyZTAwMjk0Y2YxYWE5ZjFiYWU5YmRiMDFlNGRiZmMxMjI2MDQ0MWEyODA2M2E0YjFmMDQ3MDM3YzcmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.VoAFQ5fcF_qVO3PBSiCqYokZDKSQQsvYfGpMNAKwsDQ)
The text was updated successfully, but these errors were encountered: