Weirdest thing about @atproto/api by far is how hard it is to get the post text. It’s typed as {} for some reason, aka “any object”
I’m sure there’s a reason behind it but like, it’s the most important field in the whole damn post! why isn’t it string!
I'm more than happy to add a setting for changing the sort order of replies. I did not expect it to be that controversial of a change. The most-recent-first sorting was burying a lot of good conversations and banger replies, so I figured this would be a nice QoL improvement
I see the flaws. I also think it’s weird that likes on reply like, don’t do anything. Surely if you’re looking at a popular post you wanna see the best riff, not just the most recent reply
📢 1.49 is here! It has some big updates to the Web app.
• Threads now sort replies by likes
• Fixes to the sync of moderation settings (adult content) between devices
• Improvements to the logged out UI on web
• The web app now correctly resizes for narrower screens
• Additional bugfixes, of course
so funny that Versailles is like, right there. When I watched the 2015 show I assumed it was a super long way from Paris
I know, horses, Paris has grown, etc etc
it’s just a hint, clients should not trust it and cap the size if it’s silly. But since 99% of posts are just coming from the official app, which will give accurate sizes, 99% of posts will not have the jitter any more. Basically the worst thing you can do with it is recreate the current behaviour
Q: What's all this about then?
A: It lets clients know what shape to draw the box on the screen to put the image in before it downloads the image. Currently we have to guess, download the image, then resize the box to fit the image. This causes the feed to jitter as image embeds get resized!