🤔
Due to the slower queue clears Pinafore is slipping 'new' messages into the TL at the 'proper' timestamp location which...
Every time i click 'see new toots' i gotta scroll about hunting for the new one
@f0x would you be open to investigating an option that puts 'unseen but maybe a few minutes late' posts at the very top of the column so we dont have to scroll about to see new [to us] posts?
(I plan on deploying your ui when i have the spoons 😉 )
fuchsiaaaaaaaaaaaaaaaaa
@kemonine oh, well currently it's all ordered just based on the order it's received from the server, so I think that solves your issue?
@f0x actually...
if i checkout the code what do i need to do to hack on the code and/or run the code for testing purposes?
i dont see a full launch/setup detail anywhere and am unfamiliar with std js toolchains
@kemonine latest should be fine yes, not sure how much docker really adds here though
@f0x if i deploy i need docker as i only run apps in isolation and if i deploy the static pages I still need a way to build it as i dont install node on my servers and my main os is windows 😉
looks like node index.js is erroring on "could not parse location from string" ; looks like something in validatem
setting the env to development does seem to work in initial tests
🤔
@kemonine try a git pull && yarn install, which includes some dependency upgrades. What's the actual validation error when running without an env?
@f0x :salute_emojo_goes_here:
@gled @kemonine it's https://git.pixie.town/f0x/fedifox/ but it's a very new project, so functionality is limited (currently read-only for example)
@f0x its fixed w/ the dep updates
@f0x awesome, ty very much
ill likely be looking at a docker container setup ; is the latest node/yarn safe for this one (iirc js apps can be picky about node version)