fnky

[hub]
  protocol = https

[user]
  name = Christian Petersen
  email = humanoidism@gmail.com

[credential]
  helper = osxkeychain

karpathy

LLM Wiki

A pattern for building personal knowledge bases using LLMs.

This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.

The core idea

Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.

timvisee

Falsehoods programmers believe about time

This is a compiled list of falsehoods programmers tend to believe about working with time.

Don't re-invent a date time library yourself. If you think you understand everything about time, you're probably doing it wrong.

Falsehoods

• There are always 24 hours in a day.
• February is always 28 days long.
• Any 24-hour period will always begin and end in the same day (or week, or month).

WildSiphon

4.0.0:
  Windows: https://desktop.docker.com/win/main/amd64/67817/Docker%20Desktop%20Installer.exe
  Mac with Intel chip: https://desktop.docker.com/mac/main/amd64/67817/Docker.dmg
  Mac with Apple chip: https://desktop.docker.com/mac/main/arm64/67817/Docker.dmg
  release_date: '2021-08-31'
4.0.1:
  Windows: https://desktop.docker.com/win/main/amd64/68347/Docker%20Desktop%20Installer.exe
  Mac with Intel chip: https://desktop.docker.com/mac/main/amd64/68347/Docker.dmg
  Mac with Apple chip: https://desktop.docker.com/mac/main/arm64/68347/Docker.dmg
  release_date: '2021-09-13'

kprotty

Currently, the std.Io interface isn't too optimizable:

1. All forms of concurrent execution goes through io.async/asynConcurrent(f) and io.await which can't be statically aware of when .await will be called, so it must dynamically allocate the context needed to run f.
2. The main api for blocking/unblocking on an arbitrary state is through Mutex & Condvar which require locking a mutex to wait (& wake correctly) + restrict implementors to only a usize with a biased representation for each state.
3. It ties cancellation to the task/concurrency model instead of to blocking operations (which are really the ones getting cancelled); To cancel a set of operations, they must be wrapped in a new spawned Future. It's also unclear, due to the racy nature of io.cancel, if a blocking operation consumes the stored cancellation request, or if it persists & causes all future blocking ops in that Future to return Cancelled.

I've thought of some ideas on how to address these + the all-encompassing nature of th

Maciejdziuba

Kimi Everywhere — Cheat Sheet

One Kimi Code subscription key. Every harness. Copy-paste and go.

Endpoints & key

What	Value
Anthropic-compatible base URL	https://api.kimi.com/coding/
OpenAI-compatible base URL	https://api.kimi.com/coding/v1

hhanh00

var http = require('http'),
    httpProxy = require('http-proxy'),
    express = require('express');

// create a server
var app = express();
var proxy = httpProxy.createProxyServer({ target: 'http://localhost:8080', ws: true });
var server = require('http').createServer(app);

// proxy HTTP GET / POST

rdakar

namespace CpfCnpj
{
    public static class CpfCnpjUtils
    {
        public static bool IsValid(string cpfCnpj)
        {
            return (IsCpf(cpfCnpj) || IsCnpj(cpfCnpj));
        }

        private static bool IsCpf(string cpf)

usapremiumaccess

Apple Developer Account: 12 Common Mistakes and How to Avoid Them (2026)

Signing up for an Apple Developer Account seems straightforward — until you hit an unexpected rejection, a 10-day processing delay, or a payment failure with no clear explanation. Most of these problems are completely avoidable with the right preparation.

📩 Need Immediate Support or Fast-Tracked Solutions?

If you are facing continuous verification rejections, regional registration restrictions, or need immediate assistance with Apple or Google developer setups, feel free to contact us:

• Website: USAPremiumAccess Official Portal
• Telegram: Chat on Telegram
• WhatsApp: Message on WhatsApp
• Email: usapremiumaccess@gmail.com