Skip to content

Instantly share code, notes, and snippets.

View jerlendds's full-sized avatar
💭
🦷🧵🦾

jerlendds jerlendds

💭
🦷🧵🦾
View GitHub Profile

Open Source is Not About You

The only people entitled to say how open source 'ought' to work are people who run projects, and the scope of their entitlement extends only to their own projects.

Just because someone open sources something does not imply they owe the world a change in their status, focus and effort, e.g. from inventor to community manager.

As a user of something open source you are not thereby entitled to anything at all. You are not entitled to contribute. You are not entitled to features. You are not entitled to the attention of others. You are not entitled to having value attached to your complaints. You are not entitled to this explanation.

If you have expectations (of others) that aren't being met, those expectations are your own responsibility. You are responsible for your own needs. If you want things, make them.

@jerlendds
jerlendds / sh
Created January 7, 2026 17:38
delete all artifacts
USER="jerlendds" # Replace with your GitHub username
# Fetch all repos with write/admin access
REPOS=$(gh api /user/repos\?affiliation=owner,collaborator,organization_member --paginate | python3 -c "import sys, json; repos = json.load(sys.stdin); [print(repo['full_name']) for repo in repos if repo['permissions']['admin'] or repo['permissions']['push']]")
for REPO in $REPOS; do
echo "Processing repository: $REPO"
# Optional: List recent workflow runs
echo "Listing recent workflow runs for $REPO"
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>Pure CSS Dotted Aurora</title>
<style>
:root {
--bg: #05060a;
--dot: rgba(255, 255, 255, 0.11);
@jerlendds
jerlendds / electron_drag_disable.css
Created November 9, 2025 10:55 — forked from msuchodolski/electron_drag_disable.css
Disable dragging and selecting html elements (like links, images etc...) in Electron
/**
* MAKE ELECTRON APP FEEL MORE NATIVE
*
* * Prevent dragging all HTML elements, specially:
* - images
* - links (anchors)
*
* * Prevent text selection
*/
@jerlendds
jerlendds / .gitconfig
Created October 15, 2025 19:44
~/.gitconfig
$ cat ~/.gitconfig
[user]
name = jerlendds
email = email
signingkey = /home/jerlendds/.ssh/id_github
[init]
defaultBranch = main
[alias]
pushall = !git remote | xargs -L1 -I R git push R
lg3 = log --color --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue)<%an>%Creset' --abbrev-commit
@jerlendds
jerlendds / settings.json
Created October 14, 2025 12:56
.config/zed/settings.json
// Zed settings
//
// For information on how to configure Zed, see the Zed
// documentation: https://zed.dev/docs/configuring-zed
//
// To see all of Zed's default settings without changing your
// custom settings, run `zed: open default settings` from the
// command palette (cmd-shift-p / ctrl-shift-p)
{
"context_servers": {
@jerlendds
jerlendds / codex-notifier
Created October 14, 2025 12:17
~/.codex/config.toml
#!/usr/bin/env python3
import json
import subprocess
import sys
def main() -> int:
if len(sys.argv) != 2:
print("Usage: notify.py <NOTIFICATION_JSON>")
@jerlendds
jerlendds / filebrowser.service
Created October 13, 2025 21:07
Filebrowser (github.com/filebrowser/filebrowser) .config/systemd/user/filebrowser.service
[Unit]
Description=Filebrowser (github.com/filebrowser/filebrowser)
After=network.target
[Service]
Type=simple
ExecStart=filebrowser --port 13377 -r /home/jerlendds/
ExecStop=killall -q filebrowser
[Install]
@jerlendds
jerlendds / ddd.md
Created September 5, 2025 12:50 — forked from zsup/ddd.md
Documentation-Driven Development (DDD)

Documentation-Driven Development

The philosophy behind Documentation-Driven Development is a simple: from the perspective of a user, if a feature is not documented, then it doesn't exist, and if a feature is documented incorrectly, then it's broken.

  • Document the feature first. Figure out how you're going to describe the feature to users; if it's not documented, it doesn't exist. Documentation is the best way to define a feature in a user's eyes.
  • Whenever possible, documentation should be reviewed by users (community or Spark Elite) before any development begins.
  • Once documentation has been written, development should commence, and test-driven development is preferred.
  • Unit tests should be written that test the features as described by the documentation. If the functionality ever comes out of alignment with the documentation, tests should fail.
  • When a feature is being modified, it should be modified documentation-first.
  • When documentation is modified, so should be the tests.
@jerlendds
jerlendds / killport
Last active September 3, 2025 21:54
killport
#!/bin/bash
echo "Killing PID $(fuser -k $1/tcp)on $1"
fuser -k "$1/tcp"