Notices by Sorin Davidoi (sorin@toot.cafe), page 14

@shel Might stick with them after all - just noticed that sync can be turned off (hopefully that means that it does not get sent to their servers for analytics...).

@bea I've been hacking on this for the last few days https://github.com/sorin-davidoi/cobalt

I don't usually post pictures of food, but I had worms with chili today for the first time, and they were quite good! https://toot.cafe/media/OFjZqpFNjKXhix0iJ48

#MastodonMemory @bea helping me test the push notifications for like two weeks full of rebases and welcome notifications 🐌

@nightpool browser.tabs.tabMinWidth just landed in Nightly (https://www.reddit.com/r/firefox/comments/74hf2y/this_is_fine/)

@bea If those are not set, I think the browsers may cache sw.js for up to 24 hours. I guess it failed to update for some reason and you got stuck with the initial one.

@bea 1.5 got a bug in the Service Worker which got corrected in 1.5.1. But it should have fixed it for good, no idea if this is related to that bug or something else.

@bea Can you try logging out and going to chrome://serviceworker-internals/ and unregistering the Service Worker?

@fn_aki @fn_aki For reference, this is where that happened: https://github.com/tootsuite/mastodon/pull/3677

@fn_aki Was the easiest way to port to React Router 4.

@ashkitten @bea @nolan @unarist Last time I looked over the code that is what happens.

@ashkitten @bea @nolan @unarist Yes, and that's big enough for mobile devices. Not unrendering the columns would increase the number of DOM nodes by 3/4 times, which would make the entire experience even slower. I think the way to go is to optimize the animations (e.g. like it was done here https://github.com/tootsuite/mastodon/pull/5135).

@ashkitten @bea @nolan Secondly, React unrenders the previous column before rendering the new one. This combined with the DOM diffing delays the rendering of the new column. @unarist tried to optimize this (https://github.com/tootsuite/mastodon/pull/3995), but it involves some tradeoffs (e.g. more memory consumption) that we did not feel comfortably making.

@ashkitten @bea @nolan It's mostly caused by two things. First, the library we use for swipe animation is kind of slow (it animates things that are expensive to compute by the browsers). Chrome is not impacted that much by this since is handles this use-case better, but Firefox suffers.

@schestowitz Yeah... no. Looks more like those APIs should request permission (like geo-location, notifications etc.) to be used.

@nightpool Yes, they are hit and miss, both on Desktop and Android.