Skip to content

Instantly share code, notes, and snippets.

@deepakpk009
deepakpk009 / media.json
Created November 8, 2017 14:02
sample free video urls
{
"categories": [
{
"name": "Movies",
"videos": [
{
"description": "Big Buck Bunny tells the story of a giant rabbit with a heart bigger than himself. When one sunny day three rodents rudely harass him, something snaps... and the rabbit ain't no bunny anymore! In the typical cartoon tradition he prepares the nasty rodents a comical revenge.\n\nLicensed under the Creative Commons Attribution license\nhttp://www.bigbuckbunny.org",
"sources": [
"http://commondatastorage.googleapis.com/gtv-videos-bucket/sample/BigBuckBunny.mp4"
],
@karakoo
karakoo / README.md
Last active January 21, 2026 05:50
Retrieving Auth Token (with Playwright)

Retrieving Pixiv Auth Token (with Playwright)

使用 Playwright 来登录 Pixiv ,从而获取 token

使用方法

  1. 下载本脚本 pixiv_auth.py
  2. 安装 playwrightpyotp(两步验证):
pip install playwright
pip install pyotp
╭─── Claude Code v2.1.12 ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ │ Tips for getting started │
│ Welcome back Jonny! │ Run /init to create a CLAUDE.md file with instructions for Claude │
│ │ │
│ │ ───────────────────────────────────────────────────────────────── │
│ ▐▛███▜▌ │ Recent activity
@yowmamasita
yowmamasita / claude-cleanup.md
Last active January 21, 2026 05:40
Claude Code CLI leaves orphaned background processes that consume CPU/memory. This launchd daemon auto-kills processes not attached to a terminal (TTY) every hour, keeping only your active sessions.

Auto-cleanup Orphaned Claude Code CLI Processes on macOS

Claude Code CLI can leave orphaned background processes that consume CPU and memory. This solution automatically kills Claude processes that are no longer attached to a terminal.

How it works

Active Claude sessions are attached to a TTY (e.g., s001, s002). Orphaned processes show ?? in the TTY column. This script kills only the orphaned ones.

/**
DISCLAIMER: DO NOT COPY & PASTE RANDOM JAVASCRIPT SCRIPTS INTO YOUR BROWSER'S CONSOLE WITHOUT UNDERSTANDING WHAT THEY ARE DOING. THEY CAN STEAL YOUR PERSONAL INFORMATION!!!
What this script does?
Based on an external library in immich, it goes through all the folder of it, and creates albums for each one
How it works?

🚨 CRITICAL SECURITY ANALYSIS REPORT 🚨

Analysis Date: January 20, 2026
Analyst: Automated Security Scan
Verdict:CONFIRMED MALWARE / JOB SCAM


Executive Summary

@waynemsmith
waynemsmith / WORKSTATION-SETUP.md
Last active January 21, 2026 06:29
Ops Workstation Setup Guide - Concurrent Systems

Ops Workstation Setup

Canonical laptop configuration for ops team members.

Prerequisites

Before starting, ensure you have:

  1. USB memory stick - 8GB+ for bootable Fedora installer
  2. GitHub account - create at github.com if needed
@greenmoss
greenmoss / certbot-dns-mailcow
Last active January 21, 2026 05:13
This script renews letsecnrypt SSL certificates using Cloudflare dns-1 renewal. It assumes you are using Mailcow.
#!/usr/bin/env bash
# This script renews letsecnrypt SSL certificates using Cloudflare dns-1 renewal
# It assumes you are using Mailcow
set -euo pipefail
# REQUIRED set these:
[email protected]
your_domain=mail.your.domain # only tested with single domain
cloudflare_ini_path=/root/.cloudflare # add your Cloudflare file here, called cloudflare.ini
@luismts
luismts / GitCommitBestPractices.md
Last active January 21, 2026 05:11
Git Tips and Git Commit Best Practices

Git Commit Best Practices

Basic Rules

Commit Related Changes

A commit should be a wrapper for related changes. For example, fixing two different bugs should produce two separate commits. Small commits make it easier for other developers to understand the changes and roll them back if something went wrong. With tools like the staging area and the ability to stage only parts of a file, Git makes it easy to create very granular commits.

Commit Often

Committing often keeps your commits small and, again, helps you commit only related changes. Moreover, it allows you to share your code more frequently with others. That way it‘s easier for everyone to integrate changes regularly and avoid having merge conflicts. Having large commits and sharing them infrequently, in contrast, makes it hard to solve conflicts.