zipang

import { useEffect, useLayoutEffect, useState, type RefObject } from "react";

type Direction = "top" | "bottom" | "left" | "right";
type Vector = [number, number];

interface UseSwipeOptions {
	/**
	 * Callback for swipe events
	 */
	onSwipe: (direction: Direction, vector: Vector) => void;

zipang

#!/bin/bash

# Name of the playlist file to generate/use
playlist="playlist.m3u"

# Check if the playlist file doesn't exist
if [ ! -f "$playlist" ]; then
    # Enable nullglob to handle patterns with no matches
    shopt -s nullglob
    

julianlam

Provisioning and usage of unprivileged LXC containers via indirect login or script

As I've discovered, managing LXC containers is fairly straightforward, but when building out a system for provisioning out user maintained instances of NodeBB, it was imperative that unprivileged LXC containers were used, so that in the event of shell breakout from NodeBB followed by privilege escalation of the saas user, the root user in the LXC container would only be an unprivileged user on the host machine.

During the course of development, I ran into numerous blockers when it came to managing LXC containers in unexpected circumstances. Namely:

• Using LXC in a subshell is not directly supported. This usually happens under one of the following two circumstances:
  • After switching users via su or executing lxc-* commands as another user via sudo
  • Executing lxc-* commands via a program, application, or script. In my case, a Node.js application.

ericelliott

Essential JavaScript Links

I no longer mantain this list. There are lots of other very comprehensive JavaScript link lists out there. Please see those, instead (Google "awesome JavaScript" for a start).

PixnBits

/*
 * http://www.myersdaily.org/joseph/javascript/md5-text.html
 */
(function (global) {

  var md5cycle = function (x, k) {
    var a = x[0],
      b = x[1],
      c = x[2],
      d = x[3];

mckamey

/*
 * Copyright (C) 2008 Apple Inc. All Rights Reserved.
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 * 1. Redistributions of source code must retain the above copyright
 *    notice, this list of conditions and the following disclaimer.
 * 2. Redistributions in binary form must reproduce the above copyright
 *    notice, this list of conditions and the following disclaimer in the