@madebygoogle @googlenest would be great if temperature sensor scheduling would allow for custom hour setup, not selection of 4 predetermined hour groups. Also, would be awesome to specify the sensor on the weekly schedule entry 💡
@GoLinks Yes, that does provide a way to parameterize a default, but if the default URL is too different, it won’t work. Maybe I want to take users to a help page
@GoLinks feature request: add a “default URL” field for parameterized GoLinks. Why? Sometimes the base URL of the destination URL is slightly different than the default you’d want, or simply, I just want it to go somewhere else. Mostly the former. Thanks 👍🏼
I feel like @CocaCola used to have more CO2 in it years ago. I miss that fizzle, refreshing taste. Now sodas taste like very sugary water with a splash of gas…more like a sugary sparkling water, not a soda to me. Disappointed every time I buy soda now.
Had an awesome time this week at @AllThingsOpen! Can't wait till next year. Saving October 15 – 18 in downtown Raleigh, NC : All Things Open #AllThingsOpen https://t.co/xDnrcE8d6f
@iRobot , sell outs. You sold to @Meta so they can own our mapped homes? Sell out. Why is everything bought out these days? Also, Meta has nothing to do with vacuums. SMH
@NotionHQ how are files saved and secured when uploading? I see an AWS S3 URL but I can access that if I have the link directly. How do you prevent access by anyone else?
@BrowserPerson@code Still though, the new merge conflict UI is more cumbersome than helpful. It’s confusing and takes way too much space with the bottom “Result” pane. I don’t care for this pane.
How can I change @code’s new git merge conflict UI back to it’s previous version? This new side-by-side is confusing as to what I want to accept. Doesn’t even play well with manual git checkout —theirs or —ours. Confusing. Only plus is it now properly uses “theirs”