Got (un)liking working with instant UI feedback while the network request happens. All the while without duplicating a whole tweet's worth of state to store that 😌

Composer starting to look like something

Found out about Lucide which is basically Feather Icons but with more icons so that'll be perfect for placeholder(?) icons https://lucide.dev/

I wanted to implement a mentions column tonight but then I remembered I had to juggle between API v1 and API v2 types and: yeah no I'm not doing this tonight 😩

I also wanted to try to mock some UI up and: urgh yeah I'll figure this out later lmao

Stuck between a rock (copying current TweetDeck's UI) and a hard place (making something similar but different) and I think I'll just improvise as I implement more stuff.

(That said if you have ideas and want to help on the UI side of things, hmu)

A few helpers and a refactor later, we got mentions column baby

I'm a bit bummed out because I wanted to use the API v2 endpoint for mentions but it returns V2 tweets which dont contain as much as what you get from 1.1 so I use the mentions 1.1 endpoint and lookup tweets on API v2 to grab more things AND THEN make my own representation

I could probably do the opposite but, uh, I did it that way for the home timeline and that's how Tweetbot does it AFAICT so I went for the easy route for now. It wouldn't be too tricky to change anyway.

Not pictured but before taking the screenshot I had an hilarious bug that only manifested now.. I was sorting the tweet IDs in such a way that mentions from 6 years ago were showing up, basically running `_.sortBy(t=>t,['desc']` where some of the ids were shorter than the others

which I obviously didn't notice until now because the home timeline of my test account has recent tweets, good thing I'm using that test account for that because I 100% wouldn't have seen that until much later otherwise lmao

I DIDN'T GET THE SORTING COMPLETELY RIGHT EITHER because sorting big-ass integers as strings didn't work as intended. Anyway, sorting them as floats works fine, phew.

Anyway, likes column is working

I bit the bullet and used the API V2 likes endpoint as a base and then got hydrated V1 tweets to get full tweet objects (the opposite of what I do for mentions/home)

Made a lil' spinner

I had already made one for the character counter so, like, it's just the same component but animated *taps on forehead*

Column clearing: ✅

@Eramdam awoo

@Eramdam i feel like you're going to hit edge cases because of float precision

@codl maybe but i dont really see what else I could do short of using Big Ints lmao

@codl fuck you're right, hum, guess I'll need to sort by date as a last resort

@Eramdam hoping they dont have plans to kill off 1.1?

@dogo well, api v2 is supposed to replace 1.1 in the long term but it's not feature complete with it just yet so

@dogo like, the "deprecate legacy apis" is the very last item in the roadmap https://trello.com/b/myf7rKwV/twitter-developer-platform-roadmap