dexit

site:*/sign-in
site:*/account/login
site:*/forum/ucp.php?mode=login
inurl:memberlist.php?mode=viewprofile
intitle:"EdgeOS" intext:"Please login"
inurl:user_login.php
intitle:"Web Management Login"
site:*/users/login_form
site:*/access/unauthenticated
site:account.*.*/login

mxpanf

# Static ASCII Arts
curl -L git.io/ricex       # Rice
curl -L git.io/unix        # Unix logo
curl -L git.io/taco        # Taco
curl -L git.io/pizzza      # Pizza
curl -L git.io/pancakes    # Pancakes
curl -L git.io/poptart     # Pop-Tart
curl -L git.io/waffles     # Waffles
curl -L git.io/burger      # Burger
curl -L git.io/rice        # Rice (alternative)

martinwoodward

```mermaid
sequenceDiagram
    participant dotcom
    participant iframe
    participant viewscreen
    dotcom->>iframe: loads html w/ iframe url
    iframe->>viewscreen: request template
    viewscreen->>iframe: html & javascript
 iframe->>dotcom: iframe ready

ilblackdragon

# ClawHouse: Friend.tech for Trading Agents

## One-Line Pitch

**ClawHouse is a 30-day social trading arena where people buy access keys to AI trading agents, copy their trades with private risk controls, and share verified profit receipts—turning NEAR's agent stack into a viral consumer game.**

---

# Why This Exists

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.

bagder

Slop

This collection is limited to only include the reports that were submitted as security vulnerabilities to the curl bug-bounty program on Hackerone.

Several other issues not included here are highly suspcious as well.

Reports

1. [Critical] Curl CVE-2023-38545 vulnerability code changes are disclosed on the internet. #2199174

aarondfrancis

Audit this entire codebase for materially useful simplifications in its data structures, state representation, control flow, algorithms, and ownership.

This is an audit-only exercise. Do not edit files, run tests, implement recommendations, commit, or push. Read-only inspection commands are allowed.

You are the coordinator. Continue until the complete codebase has been reviewed and the final audit is validated.

1. Establish the coverage contract

Inspect the repository and inventory every identifiable subsystem.

dillionverma

declare module 'lucide-react' {
  export * from 'lucide-react/dist/lucide-react.suffixed'
}

whitequark

#define WIN32_LEAN_AND_MEAN
#include <tchar.h>
#include <stdint.h>
#include <windows.h>
#include <shellapi.h>

COLORREF rgbText = 0xffffff;
LPTSTR pchFontName = _T("Times New Roman");
INT iFontSizePt = 24;
LPTSTR pchText = _T("InstallSword Wizard");

geoffreylitt

name	explain-diff-html
description	Use when the user asks for a rich explanation of a code change, diff, branch, or PR. Produces HTML output.

Explain Diff

Please make me a rich, interactive explanation of the specified code change.

It should have these sections: