Lmao I guess I locked myself out by logging in too much while debugging, oops
Tweetbot to the rescue (and the previous post was made with my mastodon cross poster)
Spent all my evening debugging session issues that would only happen in a production environment so this calls for a celebration. First deploy on a prod environment that actually works lmao 🎉
Had to dig GitHub issues because `shrink-ray` is dead, its maintained fork requires old dependencies that don't build on macOS (seemingly), so I ended up `compress-next` which is a fork of `compression` w/ brotli compression https://github.com/Econify/compression-next
Network is shit but I got basic gif/video playback working and looking alright.
Media working inside of quote tweets and I didn't have to change any styles (yet) for it to look nice
Later this week I want to get tweet actions working somehow (minus reply) which also means I'll need to think about how to _not_ duplicate tweets in my Redux store whilst being able to have a different RT/liked state for each account/column. Should be fun 😅
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 😌
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)
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.
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)
I had already made one for the character counter so, like, it's just the same component but animated *taps on forehead*
(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 😵💫
Might go back using io-ts. I had chosen ajv because it's supposed to be super fast but I probably don't need to worry too much about performances of my schema validation in my case lol
And, like, I need to do tagged unions for the types of my columns and boy ajv doesn't make that any easier 😭
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
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)
@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 what's wrong with BigInts? also idk how you're sorting but you could split the id into a top and bottom part, compare top parts as integers, and only compare bottom parts if the top parts are equal
@codl well,
A) they're not widely supported yet iirc
B) they're not free to use.
That said, I checked a bit more and:
- IDs are sequential but I feel like edge cases could be possible but very unlikely
- I checked how current TweetDeck does its sorting and... it's not that much more complex lmao
@codl (code is deobfuscated and i renamed the variables for clarity)
@Eramdam oh that's clever. length comparison first then lexicographic comparison if they match
sony teenyDog
@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
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