Jonathan Gamble

Timmy, just letting you know: I had to borrow some wired earbuds to reproduce this but there is definitely an issue and it is exactly how you describe. (Was skeptical...

There is no data on whether users aside from lakin & nojoke want it. This issue can be closed. I did implement the functionality, and I will retain the branch...

[Here are some thoughtful PWA suggestions from the_mindset I didn't want to get lost.](https://lichess.org/forum/lichess-feedback/progressive-web-app-great-so-far-some-minor-issuesquestions) Adding this to the pile...

It's definitely still happening, but don't know if more recent occurrences are due to Firefox cache or not. The latest report is [missing knights & bishops using Firefox on Windows...

Among people who regularly give onboarding advice, benedikt (1vader on discord) is probably a good one to bounce your embedding ideas off of. Also - friendly heads up re lichess...

I wonder if you guys would be interested in working on e-board support for the new lichess mobile app. Say hi in the lichess-mobile-app discord if you're interested.

I coded this once, but then discarded it on discovering the lila-ws path already notified on game start. But you've got to have a connected tab for that.

The user was asking for a game start notification, not a notification that the tournament started, btw.

Just so I understand. Gray, orange, yellow can hopefully be determined automatically by lila, and someone with special broadcast perms could see and toggle a switch that turns it red...

Can at least a part of this be isolated to a minimum set of steps to reproduce an undesired behavior? Example: 1. Create a broadcast 2. Add a round 3....