mstdn.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A general-purpose Mastodon server with a 500 character limit. All languages are welcome.

Administered by:

Server stats:

15K
active users

#bigredbutton

0 posts0 participants0 posts today
Brad Romance<p>For now I’ll select the holiday manually, but when I automate that I might set it to use a calendar instead. That way I don’t have to create automations to change the input select for whichever holiday, I just have to use the calendar event as a condition in my automations. <a href="https://toot.chez.gay/tags/HomeAssistant" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HomeAssistant</span></a> </p><p>I also need to figure out how to select different folders for music for the <a href="https://toot.chez.gay/tags/BigRedButton" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BigRedButton</span></a> so we have suitable music for the <a href="https://toot.chez.gay/tags/BathroomDisco" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BathroomDisco</span></a> for whichever holiday it is.</p>
Newsmast Foundation<p>Tumbling down the internet's memory lane led us to an iconic find: This spring is the 30th anniversary of the Really Big Button That Does Absolutely Nothing! 🔴</p><p>At the time, Paul Mitchell observed: "I think there’s something wrong with the Big Red Button. It doesn’t seem to do anything."</p><p>You have no idea what this is? We're here to help. It's a '94 relic is the epitome of internet randomness. Experience it here: <a href="https://krystalrose.com/rosewood/library/BigButton.htm" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">krystalrose.com/rosewood/libra</span><span class="invisible">ry/BigButton.htm</span></a></p><p><a href="https://newsmast.social/tags/InternetHistory" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>InternetHistory</span></a> <a href="https://newsmast.social/tags/Internet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Internet</span></a> <a href="https://newsmast.social/tags/BigRedButton" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BigRedButton</span></a> <a href="https://newsmast.social/tags/mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>mastodon</span></a></p>
Lisa Lorenzin (she/her)<p>Since we're telling <a href="https://infosec.exchange/tags/BigRedButton" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BigRedButton</span></a> stories...</p><p>Very early in my career, I was a SOC monkey for a small local Internet &amp; data center hosting provider. Our Big Red Button was mounted on the wall of the data center, just beyond the door, a little over 6' off the ground - low enough to reach up and hit it, high enough to avoid accidentally bumping into it... Or so we thought.</p><p>The company was small enough that our founder and CEO was still very hands-on - to the point that he was helping a brand-new employee carry a heavy server into the data center for installation one day. $newGuy - who was about 6'4" - walks backwards through the door into the data center, backs up against the wall so $CEO can swing the server around to go down the aisle... And hits the Big Red Button with the back of his head.</p><p>Instant unplanned production-outage-recovery drill, all hands on deck!</p><p>IIRC, our recovery procedure documentation improved a *lot* over the next few days. 🙄 $newGuy totally expected to be fired, but $CEO took full responsibility (one of the reasons I loved working there - the two founders were both fantastic people as well as visionary technogists). And the Big Red Button got a mollyguard, since "high enough to be out of the way" was clearly relative. 🤣</p><p>RE: <a href="https://dood.net/objects/6b030cfe-14d3-40b4-976a-5a08f0e1c72d" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">dood.net/objects/6b030cfe-14d3</span><span class="invisible">-40b4-976a-5a08f0e1c72d</span></a><br><span class="h-card" translate="no"><a href="https://dood.net/users/rossgrady" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>rossgrady</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.laurenweinstein.org/@lauren" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>lauren</span></a></span></p>
Brad Romance<p>Our dogsitter is Not At All Online and hasn’t visited us since we installed the <a href="https://toot.chez.gay/tags/BigRedButton" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BigRedButton</span></a>. He doesn’t know about it. He’ll just see it sat on top of the toilet cistern.</p><p>He’s arriving shortly. How long before <span class="h-card"><a href="https://toot.chez.gay/@hal" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>hal</span></a></span> toots about <a href="https://toot.chez.gay/tags/BathroomDisco" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BathroomDisco</span></a>? 🕺🏻</p>
Continued thread

So V2 does things differently. Here's how it works:

When #HomeAssistant starts up, an automation populates a dropdown selector with a shuffled list of songs, pulled from a sensor which monitors the contents of a folder.

When the #BigRedButton is pressed, a virtual toggle is turned on.

An automation watches for when that toggle’s state changes to “on”, and triggers a script which changes the lighting and plays the song selected in the dropdown. The automation is only interested in the toggle, so if it's already on, subsequent button presses are ignored. No skipping tracks with multiple button presses!

Another automation watches for when the bathroom speaker stops playing at the end of a song, and checks to see if the virtual toggle is on (ie the song was started from a button press, not from my phone or whatever). If so, it triggers a script that changes the lights back to normal, selects the next item in the dropdown, and turns off the virtual toggle, ready for the next button press.

V2 of our #BigRedButton is up and running. From the outside, it seems absolutely no different, but the stuff behind it is waaaay more complicated.

Previously, a song was selected at random every time the button was pressed. So if someone panicked and pressed the button again it would stop the current song and start another one, and then another, and another... not the experience I wanted.

Also, the random selection was not random in the right way. Each time, it picked from the entire list. This meant that it was possible for the same song to be selected on subsequent presses, and some songs never got picked.

It seemed to really like "Let's Get Loud" by JLo.