stenuto

#!/bin/bash

# Function to display usage information
usage() {
    echo "Usage: $0 /path/to/input.mp4 [ /path/to/output_directory ]"
    exit 1
}

# Check if at least one argument (input file) is provided
if [ $# -lt 1 ]; then

adamkiss

<?php

use Kirby\Cms\App;
App::plugin('adamkiss/simple-snippets', []);

if (! function_exists('s')) {
	/**
	 * Short, auto-return snippet call with support for auto-merging certain parameters
	 *
	 * @param string $snippetName

kiding

<!-- 
  When an input element gets focused, iOS Safari tries to put it in the center by scrolling (and zooming.)
  Zooming can be easily disabled using a meta tag, but the scrolling hasn't been quite easy.

  The main quirk (I think) is that iOS Safari changes viewport when scrolling; i.e., toolbars shrink.
  Since the viewport _should_ change, it thinks the input _will_ move, so it _should_ scroll, always.
  Even times when it doesn't need to scroll—the input is fixed, all we need is the keyboard—
  the window always scrolls _up and down_ resulting in some janky animation.

  However, iOS Safari doesn't scroll when the input **has opacity of 0 or is completely clipped.**

marco79cgn

// dm Klopapier Widget
//
// Copyright (C) 2020 by marco79 <marco79cgn@gmail.com>
//
// Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted.
//
// THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL
// IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT,
// INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER
// IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE

stettix

Things I believe

This is a collection of the things I believe about software development. I have worked for years building backend and data processing systems, so read the below within that context.

Agree? Disagree? Feel free to let me know at @JanStette.

Fundamentals

Keep it simple, stupid. You ain't gonna need it.

Merott

This is a simple Tailwind plugin to expose all of Tailwind's colors, including any custom ones, as custom css properties on the :root element.

There are a couple of main reasons this is helpful:

• You can reference all of Tailwind's colors—including any custom ones you define—from handwritten CSS code.
• You can define all of your colors within the Tailwind configuration, and access the final values programmatically, which isn't possible if you did it the other way around: referencing custom CSS variables (defined in CSS code) from your Tailwind config.

See the Tailwind Plugins for more info on plugins.

rsms

Fixing macOS 10.14, 10.15, 12

Dark main menu without the rest of dark mode

1. Set Light mode
2. defaults write -g NSRequiresAquaSystemAppearance -bool Yes
3. Log out and log back in
4. Set Dark mode

vktr

function (user, context, callback) {
  user.app_metadata = user.app_metadata || {};

  if ('stripe_customer_id' in user.app_metadata) {
    context.idToken['https://example.com/stripe_customer_id'] = user.app_metadata.stripe_customer_id;
    return callback(null, user, context);
  }

  var stripe = require('stripe')('sk_....');
  var customer = {

szydan

ffmpeg -i input.aiff -f mp3 -acodec libmp3lame -ab 192000 -ar 44100 output.mp3

szabba

elm-stuff/