Ridgeline subscribers — A little note to begin: A buddy of mine, Nick Dwyer, is running a Kickstarter campaign for his A Century in Sound documentary. He’s looking at 100 years of Tokyo history through its music cafés (classical, jazz, rock, noise, etcetera). He’s collaborated with photographer Lee Chapman on a companion book. I am a backer. Nick handed me the book in person last week — it’s stunning. They nailed it. What makes this project extra special is that Nick has truly put in the shoe leather for cultivating intimate relationships with all the shops they feature. He’s been working on this documentary series for a decade. The shop owners adore the hell out of him. (I’ve seen it in person.) I also got a sneak peek at half of the doc in August — it’s fabulous, and deserves to be seen all over. Consider giving it a back and grabbing the book. It’s a good’un. Six days left, and they’re almost at their goal.

ARTE TOKYO is a new citywide festival of arts and culture that transforms public spaces across the Japanese capital into an expansive outdoor gallery, bringing together artists, architects, designers, and creative technologists. Running through December 31, the festival centers on three major areas: the waterfront district around Odaiba, the business and cultural hub of Hibiya […] Related posts: House NA by Sou Fujimoto Cones of Light Create Abstract Trees in Sou Fujimoto’s Interactive Forest 2013 Serpentine Pavilion to be designed by Sou Fujimoto

Big news! ETS is upgrading you to Royale The post Edmonton, meet your new favourite app appeared first on Transit.

You’re welcome to all developers that user Render.com. I recently discovered that their interactive shells in the dashboard had a memory leak. Memory would not be returned to your service if a shell crashed in your browser. And those shells did not play well with ad blockers like uBlock Origin. As such I’ve found Render in-browser shells could crash quite often. For several years we noticed that server memory grew over time in ways we could never explain, even with a lot of troubleshooting. Sometimes the leak would saturate all of our server’s memory. A server restart would clear things out, so eventually we even had background jobs set up to restart our servers a few times a day to “fix” the memory leak. Last week I finally sat down and dug a little deeper when a lesser-used server started crashing right as I was taking a rare chance to work on it. Processes galore! I’m told this has now been fixed up. Perhaps now I can reduce some of our serve allocation… Reply by email