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: ✅

(And implicitely, column updates on the back-end but that's not as fun to show)

Starting to need to do weird things with my json schema validation (tagged unions) and...yeah no choosing ajv wasn't wise. It's neat but it's really slowing me down having to basically write my schemas twice 😵‍💫

Ended up going with `superstruct`. It's neat, a bit less verbose than io-ts and has better type inference in some places.

Native enums support is not there yet but can be worked around https://github.com/ianstormtaylor/superstruct/issues/993

https://docs.superstructjs.org

And now I'm tired and didn't end up doing the thing I wanted to which was union types shenanigans. Tomorrow... 🥲

Relatedly idk what i'll do re: open-sourcing the app because I do want to somehow monetize it but:
A) it feels weird to monetize and have the source open
B) I do like having the code open because BTD wouldn't have been where it is rn without contributors

huuuuum

(I'm not gonna do a crazy monetization scheme, don't worry)

I'd go the "open source it and let it be completely free and hope people donate/support" route but 8 years of BTD told me that people barely do that so idk

I was fine with not getting much because BTD didn't cost anything to run because, well but there _will_ be a cost for me to run Skyla so idk

Welp, I wanted to do my Enum-based union types stuff with superstruct and it falls apart because of the lack of support for native TS Enums.

_sigh_

Onto io-ts I go lol

Finally got to do it and having neat union types for columns 😌 (code cut down for the screenshot)

Feels bonkers that I had to write this myself but

Like, the only useful Google hit for "validate express with io-ts" is a blogpost with a snippet of code I had to use as a base, wild that there isn't any packages for this.

Lil list with lil icons

I should make an actual bit of UI to like, add columns and such but I dont wanna do that tonight 😩

Also I was thinking the layout of the sidebar could be like this:

____
header button(??)
____
composer
______
column list item1
column list item2
_____
more buttons??

I'd need to figure out a collapsed state for it but,

It's annoying because I'm really used to TweetDeck's sidebar layout but I dont want to copy it exactly for obvious reasons 😬

Multi accounts drifting

Used the accounts mode switcher thingy as an excuse to make myself a hook to easily save user settings to the Redux state/server as easily as using `useState` 😎

I'll have to look into a better debouncing/request cancellation mechanism but that'll wait ~ later ~

I completely caved in lol

I also put a system in place for dialogs/tooltips so I'll finally add a column picker, but probably tomorrow because today is Sunday and i want to be lazy

It looks ugly for now but! Column picker!!

(This also made me notice a bug in my HTTP request caching code so there's that)

I really need to either find someone willing to help me on the UI side or, hum, plan a bit more ahead and mock stuff up. I'm starting to hit the limits of "design in the browser as I go" 😅

@Eramdam what do you want to do ?

@Palingenae comment ça? 😅