Samuel
@samuel.fm
we shipped v1.133 this week. nothing user facing but there were some interesting things in this one - using Metro as our bundler on web! no more webpack 🎉 - got the android crash rate down to a historic low - timestamps now preserve your device’s 24hr time preference
6 5 66
Sigvat
Looks like you fixed the app language selector while simultaneously breaking it on web? 🤔
Sigvat@sigvat.maanebedotten.no· 27 Sept
Whatever you've done to it now has just broken it completely for me. I used to default to the top choice, now I have to manually select it for every single post, before it defaults back to a single language. If you have to mess with this, at least allow multiple default languages.
The language selector from the composer window. I have no idea what Japanese, Portugese or German are doing on there, to my knowledge I have never posted in those languages. Norwegian Nynorsk + Norwegian Bokmål + Norwegian English Japanese Portuguese German Norwegian More languages ...
Samuel
okay dang there’s a bug in the runtime, my code is right but Intl.DateTimeFormat is wrong. guess I have to go try and fix that
2 15
Jeremy Tice
There's no better/worse feeling than realizing it's the platform or the library that has the bug
3
Barry Dorrans
Feature ask - for the web client, have it detect a new version and ask the user if they want to refresh/reload and use it.
1 2
NotNite
1.133 doesn't actually seem to be deployed in web? I was gonna look at the Metro changes to see if it broke nitesky but I don't have it even after a cache refresh
Build version: 1.132.0; Bundle info: 882741c (prod); Bundle date: 26090920; Platform: web; Platform version: 0.0.0; Device ID: c801ec1a-326f-43c4-8314-634bbf942f4e 1 5
Tim
>got the android crash rate down to a historic low
3