m0wer's avatar
m0wer
m0wer@sgn.space
npub1w3va...4c5c
JoinMarket NG
m0wer's avatar
m0wer yesterday
Cloudflare's coding-agent skill for multi-phase security audits A coding-agent skill that turns your agent into a security auditor. It orchestrates isolated agents through reconnaissance, coverage-led hunting, candidate validation, structured output, independent record verification, and target-neutral reporting. This is the skill that seeded Cloudflare's vulnerability discovery harness, described in [Build your own vulnerability harness](https://blog.cloudflare.com/build-your-own-vulnerability-harness). The harness grew into a multi-stage, fleet-wide system; this skill is the single-repo starting point it evolved from.
m0wer's avatar
m0wer 2 days ago
linus-torvalds-skill: Distilled Code Reviewer skills/soul from 32k~ emails Distills Linus Torvalds' code-review methodology from his LKML emails into a reusable, language-agnostic Skill (and Soul) from various LLMs. Built from **38,293 real review moves** extracted from 31,397 of his emails (2002–2026) on the Linux kernel mailing list, plus 67 interview transcripts.
m0wer's avatar
m0wer 4 days ago
FCC ISM Rules May Shatter Lora Mesh Communities Meshtastic and MeshCore’s default U.S. radio settings may violate **existing, not new, FCC rules**, prompting a shift to 500 kHz bandwidth that cannot communicate with nodes using the old settings. That migration, compounded by interference problems seen in urban testing, could fracture LoRa mesh communities into incompatible networks.
m0wer's avatar
m0wer 6 days ago
m0wer's avatar
m0wer 1 week ago
m0wer's avatar
m0wer 1 week ago
Would it be better if Bitcoin was "completely confidential"? Let's skip the "shitcoins" debate. Would it be better if Bitcoin was "completely confidential" ™️? Assuming it was like that from the beginning and that we had certainty of no inflation bugs being possible. Lots of hypotheticals, but to center the debate around full confidentiality vs. the state. The idea comes from https://stacker.news/items/1571256/r/m0wer. The thought behind it is whether "privacy" coins are a bad idea because they become a clear target for the state or actually the opposite because they "force" people to opt-out. Maybe there are many other considerations. The question is, if you had a magic wand and could make Bitcoin have been completely confidential from the beginning without bugs, would you?
m0wer's avatar
m0wer 1 week ago
Zcash: EU AMLR prohibits anonymisation-enhancing coin accounts Controversial(?) opinion: "privacy" coins are a bad idea because they become a clear target for the state. Or maybe the opposite because that would mean "forcing" people to opt-out?
m0wer's avatar
m0wer 1 week ago
A Severe Misalignment of AI in Mathematics TLDR: Tao and 24 other Fields Medalists warn that AI companies are optimizing for “solving” famous math problems, while mathematics is really about developing understanding, ideas, and new methods. Rapidly mass-producing solutions risks destroying the human process that turns problems into lasting knowledge, while creating serious attribution and plagiarism issues. They’re not against AI in math; they argue it should accelerate understanding rather than turn research into a benchmark race.
m0wer's avatar
m0wer 1 week ago
The AI Language We Can't Read: Neuralese - YouTube First, we gave models a scratchpad: instead of forcing a one-shot answer, let them spend more tokens reasoning through a problem. In a sense, you get more capability out of the same model by giving it more serial computation. That reasoning is also useful because humans can read it. You can inspect how the model reached an answer, spot mistakes, and potentially debug or monitor it. But there’s an obvious incentive to make that reasoning cheaper. Compress it, shorten it, remove redundant words. The problem is that if you keep optimizing for efficiency, the reasoning can drift into shorthand or “Neuralese” that still works for the model but becomes gibberish to us. So there’s a tradeoff: more efficient reasoning vs. preserving one of the few windows we have into how the model reached its conclusion.
m0wer's avatar
m0wer 2 weeks ago
github-backup: backup a github user or organization It's never a good idea to put all your eggs in one basket, so don't let GitHub have the power to take away all the issues, PRs, and discussion history of your project! Even if you have repo mirrors and local copies, that's just the code. But everything else around it is just as valuable. This is a tool that allows you to easily backup all your user or organizations repos, including the code, and all comments in issues PRs or wherever. Basically everything that you have in GitHub. It supports incremental backups and just needs a read access token with as many permissions as things you want to back up. Don't leave it for when it's too late!
m0wer's avatar
m0wer 2 weeks ago
JoinMarket NG 0.39.0 and 0.39.1 are out. Comes with supply chain attack hardening. 0.39.1 TLDR: Pre-release workflow (to pevent releases with all needed signatures), rescan bug loop fix, local installer for updates (supply chain hardening), UTXO selector redesign, and local up to date config.toml.template reference copy. 0.39.0 TLDR: Bug fixes, security hardening, and privacy improvements. Takers now consider only quantized maker offers by default, with an optional equalized payment policy. New features like jm-wallet delete and improved usability and logs noise.
m0wer's avatar
m0wer 2 weeks ago
Found a vulnerability in some LN software with hundreds of stars in GitHub. The repo has no security policy and does not accept private reporting. The maintainer does not advertise his email but managed to found it in some commits. The GPG used to sign them and other stuff is expired but still being used. I did not manage to convince neomutt to encrypt an email with the expired key, because if I changed the system time, then my key was not yet valid xD Anyway sent an email asking for a fresh GPG key for the report, the maintainer has not answered after a few days. Do I just open the issue openly? Or what does one do in this cases?
m0wer's avatar
m0wer 2 weeks ago
Implicit Deletions and Improvements in Utreexo IBD The interesting idea is that Utreexo IBD can exploit something live validation normally can’t: during historical sync, you already know which outputs will eventually be spent. That means you can avoid inserting those outputs into the accumulator only to later download proofs and delete them, and instead build the accumulator as if those deletions had already happened. Combined with Swift Sync-style spentness hints that remain verifiable, this cuts a large chunk of Utreexo’s IBD proof overhead and also makes block processing much more parallel, potentially turning sync into a mostly bandwidth-bound problem even on low-end hardware.