pull down to refresh

157 sats \ 9 replies \ @k00b 16 May 2022 \ on: Daily discussion thread
Still working on profile photos ... Hoping to finish that up today. Then I'll probably go back to WoT improvements/research/experiments.
write
preview
63 sats \ 3 replies \ @k00b 16 May 2022
profile photos are done
reply
10 sats \ 0 replies \ @gmd 16 May 2022
whoa! very cool!!!
reply
21 sats \ 1 reply \ @nout 17 May 2022
It would be great to set some browser caching headers on those images, currently those seem to refetched every time - at least from what I can tell. Does S3 have a setting for that?
Does the image URL change when user uploads a new version? If yes, then you could essentially cache those forever:
cache-control: public, max-age=31536000
It would also probably be good idea to gzip (or ideally brotli) those images on response ;)
reply
21 sats \ 0 replies \ @k00b 17 May 2022
Iā€™m going to put a CDN in front of them with long expiries. We ship incrementally around here šŸ˜‰
reply
53 sats \ 4 replies \ @k00b 16 May 2022
Also added 16m sat outbound channel to the node today ... mempool is still binanced, so might be awhile to get confirmed.
reply
10 sats \ 1 reply \ @BlokchainB 16 May 2022
Good I gotta balance this channel with ya node
reply
41 sats \ 0 replies \ @k00b 16 May 2022
Should be good now. Have almost as much outbound as inbound.
reply
21 sats \ 1 reply \ @k00b 16 May 2022
avg response time is back >200ms ... ugh. Performance is probably going to have to be routinely revisited.
reply
21 sats \ 0 replies \ @k00b 16 May 2022
Just pushed a fix. Turned out to be an issue where jobs sat payment records are numerous and my query wasn't specific enough to filter them out ... so lots of records were getting scanned that didn't need to be = lots of time.
reply