Twitter | Search | |
Charlie Croom
Web . Working with an awesome team to build the web's best PWA; DMs open to chat about it. Also Photography, aviation, gaming, comedy, and !
3,562
Tweets
523
Following
1,688
Followers
Tweets
Charlie Croom 33m
Our badge count api (not chrome's, sorry confusing), so if you have 5 notifications. But you read them on your computer, you now have 0 notifications. So the badge on your phone (with Background Sync) would go 0 -> 5 -> 0. Again, there's lag, but that's the idea
Reply Retweet Like
Charlie Croom 51m
So, true. But if people opt out of certain push notifications (or turn them off) then we'd still like the badging to be accurate. In addition, the badging api syncs cross client whereas push does not.
Reply Retweet Like
Charlie Croom 2h
I think so. Our use case would be, whenever we can: - fetch and set the badge count - fetch and cache the home timeline for next open Users might be upset that badge count lags too much. But I guess push notifications fill that gap
Reply Retweet Like
Charlie Croom 2h
Agree. I don't envy the job :) Could the contract be a no-promises type thing? I request a max/min interval, if it can't be fulfilled based on engagement, it fails or SW can read bounds like permissions and request accordingly.
Reply Retweet Like
Charlie Croom 2h
Do you know if Background Sync is still under consideration? For something like the Badging API, the example hacks around it by using the sync event, but it seems like a better fit in conjunction with BackgroundSync. Or for us, if we wanted to warm-up initial timeline data.
Reply Retweet Like
Charlie Croom 9h
Replying to @nekrtemplar
The other one now that I think about it is periodic sync
Reply Retweet Like
Charlie Croom 9h
I think it was mostly verbal hearsay. Not sure there's a filled issue that I've seen.
Reply Retweet Like
Charlie Croom 19h
Replying to @nekrtemplar
Saw this too on the Phone Number / SMS API and definitely some cool things in there. Excited to hear more...
Reply Retweet Like
Charlie Croom 19h
I think they know that's an issue
Reply Retweet Like
Charlie Croom Oct 13
This is a bug in Edge/Windows that should be fixed soon cc
Reply Retweet Like
Charlie Croom Oct 12
Oh man. I went far into that polyfill this week. Would love to hear what you are up to. Interested in scroll event quirks as well :-D
Reply Retweet Like
Charlie Croom Oct 12
Replying to @bleeman @zacbowden
There's always TweetDeck if you wanna really fill up that side-to-side space :)
Reply Retweet Like
Charlie Croom Oct 12
Hmmm. Kk. And what kind of device/browser?
Reply Retweet Like
Charlie Croom Oct 12
Replying to @bleeman @zacbowden
Not yet. That would require us to keep the entire tweet history on disk like the Android and iOS apps. Possible in the future, but still working on higher priority features first.
Reply Retweet Like
Charlie Croom Oct 12
Are you actually enabling notifications or dismissing? Do you log out or use multiple accounts? I've heard some reports of this so may need to look into it.
Reply Retweet Like
Charlie Croom Oct 12
Still daily closures, but it's a step in the right direction towards making those less necessary.
Reply Retweet Like
Charlie Croom Oct 12
Replying to @Daniel_Rubino
It certainly won't hurt. Let me know it if seems a little better in the next week, the Edge input slowness may be something else still. But I can send you some test builds to see how different things feel if it's still present, we have an idea or two.
Reply Retweet Like
Charlie Croom Oct 12
Today we greatly improved performance of the Twitter PWA when it's open for long periods of time. Hopefully this should resolve some issues people have reported, let me know over the weekend if it's snappier Or in more direct technical terms: we fixed a really bad memory leak :)
Reply Retweet Like
Charlie Croom Oct 12
Virtual scrolling web API would be very helpful :-D
Reply Retweet Like
Charlie Croom Oct 10
Cc , mentioned you had some experience with migratory pig collars and might be able to advise Colin.
Reply Retweet Like