ChronSyn

{
  "customizeUI.stylesheet": {
    // Sets the styles for the active tab, such as background color and border
    ".monaco-workbench .part.editor>.content .editor-group-container>.title .tabs-container>.tab.sizing-fit.active": {
      "background": "linear-gradient(to right, #ff6f00, #ffca28) !important;",
      "border-bottom": "2px dotted #6200ea !important;",
      "border-top": "2px dotted #6200ea !important;",
      "color": "black !important;",
    },
    ".monaco-workbench .part.editor>.content .editor-group-container>.title .tabs-container>.tab.sizing-fit.active.dirty": {

ChronSyn

I'm not the only person who is increasingly frustrated with Spotify and their determination to ignore the community while they COMPLETELY FUCK UP THE USER EXPERIENCE of their apps.

Some time ago, they added 'Smart Shuffle'. The community has clearly voiced their dislike of this feature, and yet still it remains in the app. Smart shuffle wouldn't be so bad if it wasn't combined with the regular shuffle button.

They also recently introduced the 'DJ' playlist which has no reliable way to be removed and is adding extra clutter we didn't ask for.

This is the third revision which removes the default shuffle button and replaces it with one which is visually identical but which only toggles shuffle functionality without smart shuffle.

1. Install Spicetify
2. If you want to remove smart shuffle: Place the contents of the remove-smart-shuffle.js file below in a file in your Spicetify extensions folder. For example, on Windows, place this file at %APPDATA%/spicetify/Extensions/remove-smart-shuffle.js. Run `spice

ChronSyn

ESPHome sound monitor using ESP32 and KY-037

I read a lot of reports online of these sensors being unreliable, or being difficult to tune. The latter part is partly true, but there's a lot of misunderstanding about how to interpret the data. Once you understand how you should interpret it, it becomes much clearer how you should calibrate it and how to configure your ESPHome device to use the data it provides.

My first thought was higher measured voltage = louder noise. After all, every sensor I'd worked with worked in this way, but most of them reported the 'human friendly' value - e.g. temperature, CO2, humidity, etc.

Sound is different. You probably know that sound is made up of waves, and you've probably seen a waveform corresponding to audio.

Louder sounds aren't represented by just a higher peak, but by a higher deviation. For example, your baseline is set at 0. When a sound happens, the waveform starts and you have values that are positive and negative - so shouting might be represented as many po

ChronSyn

while ($true) {
    $processes = Get-Process spotify
    $title = (Out-String -InputObject $processes.mainWindowTitle) -replace "`n","" -replace "`r",""
    $song = $null
    $artist = $null
    $songTitle = $null
    $jsonOutput = $null
    $jsonOutputAsJson = $null
    if (-Not $title.Contains('Spotify')) {
        $song = $title

ChronSyn

import { StorybookConfig } from "@storybook/react-native-web-vite";
import { InlineConfig, mergeConfig } from "vite";

const main: StorybookConfig = {
  stories: ["../components/**/*.stories.@(js|jsx|ts|tsx)"],

  addons: ["@storybook/addon-docs", "@chromatic-com/storybook"],

  framework: {
    name: "@storybook/react-native-web-vite",