- arch: mostrar la arquitectura de la máquina (1).
- uname -m: mostrar la arquitectura de la máquina (2).
- uname -r: mostrar la versión del kernel usado.
- dmidecode -q: mostrar los componentes (hardware) del sistema.
- hdparm -i /dev/hda: mostrar las características de un disco duro.
- hdparm -tT /dev/sda: realizar prueba de lectura en un disco duro.
- cat /proc/cpuinfo: mostrar información de la CPU.
- cat /proc/interrupts: mostrar las interrupciones.
Discover gists
| # Rails + PostgreSQL Performance Audit Playbook | |
| A field-tested method for finding what's actually burning your database CPU, built for a | |
| Rails monolith on managed PostgreSQL (Cloud SQL / RDS / etc.). It assumes no APM — just | |
| `pg_stat_statements`, `pg_stat_activity`, and discipline. It pairs well with an LLM: point | |
| one at this file plus your query results and let it do the attribution; the queries below | |
| are ordered so a human can run them and paste results back. | |
| ## The core idea |
A complete cookbook for building a self-hosted mail stack with single sign-on across webmail and desktop clients — no app passwords required.
Stack:
- Stalwart — mail server (JMAP, IMAP, SMTP)
- Authentik — identity provider (OIDC, LDAP)
- Bulwark Webmail — JMAP-native webmail client
- thunderbird-custom-idp — Thunderbird OIDC add-on
- Cloudflare Tunnel — public access without open inbound ports
Статья опубликована под лицензией Creative Commons BY-NC-SA.
Три месяца назад здесь на Хабре я опубликовал статью "Интернет-цензура и обход блокировок: не время расслабляться", в которой простыми примерами показывалось, что практически все популярные у нашего населения для обхода блокировок VPN- и прокси-протоколы, такие как Wireguard, L2TP/IPSec, и даже SoftEther VPN, SSTP и туннель-через-SSH, могут быть довольно легко детектированы цензорами и заблокированы при должном желании. На фоне слухов о том, что Роскомнадзор активно обменивается опытом блокировок с коллегами из Китая и блокировках популярных VPN-сервисов, у многих людей стали возникать вопросы, что же делать и какие технологии использовать для получе
| # npsol.nim | |
| # Compile & run: | |
| # nim c -r -d:release -d:opencl -d:blas=openblas --mm:refc npsol.nim | |
| import std/[math, strformat, sequtils, os] | |
| import arraymancer | |
| import arraymancer/tensor/tensor_opencl | |
| import arraymancer/tensor/backend/opencl_backend | |
| import numericalnim | |
| import opencl | |
| import datamancer |
| #!/opt/homebrew/bin/bash | |
| # Thank you to [NerdyDeedsLLC](https://gist.github.com/NerdyDeedsLLC) for this | |
| # | |
| # LICENSED UNDER | |
| # https://gist.github.com/NerdyDeedsLLC/28b9157c36b195efd103a5e3aaf85eea | |
| set -euo pipefail | |
| SHELLDOT="$HOME/shelldot" |
| { | |
| "name": "Dental clinic speed to lead", | |
| "nodes": [ | |
| { | |
| "parameters": { | |
| "httpMethod": "POST", | |
| "path": "00000000-0000-4000-8000-000000000001", | |
| "options": {} | |
| }, | |
| "type": "n8n-nodes-base.webhook", |
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.
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.