New stories

Built a small Go CLI/library to inspect JWTs locally and optionally verify HMAC signatures.

Repo: https://github.com/alesr/jwtpeek

Not trying to replace mature JWT libraries out there. Just sharpening my idiomatic Go and having a quick way to check JWTs without sharing secrets.

Feedback welcome. What would make it more useful: stdin support, JSON output, exit codes, JWKS/RS256 support, or claim/policy flags?

pdffreeeditor.com offers a free online PDF editor that allows users to view, edit, and manipulate PDF files without the need for specialized software.

The article discusses Clay Christensen's concept of 'Jobs to Be Done', which suggests that businesses should focus on understanding the underlying jobs that customers are trying to accomplish, rather than just the specific products or services they offer. It explores how this approach can help companies better meet customer needs and develop more effective marketing strategies.

Hi! I spent 3 years evaluating LLMs for OpenAI, Anthropic, METR, and other labs. Kept running into the same problem: AI workflows break in production because there's no clean way to add human oversight, handle failures gracefully, or deploy without choosing between "all cloud" and "all self-hosted."

WeaveMind is a visual workflow builder in Rust. The core idea is that humans and AI are interchangeable nodes in the same graph. When a workflow needs judgment, it pauses, notifies the team via browser extension, first responder picks it up. There's also an AI assistant that generates workflows from natural language, and durable execution so nothing gets lost on failure.

Early beta, free (bring your own API keys). Planning to open source once stable (Q2 2026). Feedback welcome. Discord: https://discord.gg/FGwNu6mDkU

Found this today while looking for text to image tools that handle typography well.

Link: https://seedream5ai.org/

What it appears to offer • Text to image generation from prompts, positioned for creators and designers • A focus on “text heavy graphics” and text rendering quality (based on how the site markets it) • Extra utilities in the nav like an image upscaler and background remover • A changelog page that describes a “My Images” workflow and an API endpoint for listing generations

Why it might be useful • If you regularly generate posters, banners, thumbnails, UI mockups, or ads where readable text matters, it could be worth a quick test.

Questions for anyone who tries it • How good is the actual text rendering versus other generators you’ve used • Does it stay consistent with longer phrases and mixed language text • Any issues with generation speed, pricing clarity, or output restrictions (watermark, resolution, etc.)

If you test it, please share prompt examples and results.

Vouch is an open-source project that provides a way to manage and authenticate user access to web applications. It offers features like single sign-on, multi-factor authentication, and granular access control, making it a versatile solution for managing user access in web-based environments.

After analyzing 9 years of HN side project posts, I found some counter-intuitive patterns about what makes projects profitable.

Three things that stood out:

1. B2B dominates: 73% of $500+/month projects target businesses, not consumers

2. Speed matters more than polish: Average 47 days from launch to first sale. Most started charging with 3-5 core features.

3. Pricing cluster: 87% price between $20-49. Low enough for impulse purchase, high enough to be sustainable.

I compiled this into a dataset of nearly 700 projects with tech stack, pricing, and timeline data. Built it because I was planning my own side project and wanted to see patterns, not just success stories.

Available at [https://haileyzhou.gumroad.com/l/pknktt] ($49) as html report and raw .csv data.

Data source note: All from public HN posts 2017-2025. I did the cleaning, categorization, and cross-referencing.

Happy to discuss methodology or findings. Curious what patterns others see or if this matches your experience?

The article explains Arcan, a browser designed to handle different types of web content, including traditional websites, games, and real-time applications. It highlights Arcan's unique features, such as its modular architecture and support for diverse display technologies, making it a versatile tool for navigating the evolving web landscape.

This article discusses the growing concern over the potential risks of advanced AI systems, arguing that the fear of AI is often exaggerated and that we should embrace the technology's potential benefits while addressing its challenges responsibly.

This technical note discusses the design and construction of a simple and inexpensive receiver for the 13-centimeter amateur radio band. It provides details on the circuit design, components, and construction considerations for building this receiver.

Hi HN,

I built a free, open-source dictionary API for developers who need quick word lookups without authentication or paywalls.

It’s powered by Wiktionary and returns definitions, parts of speech, pronunciations (IPA), and examples in clean JSON.

The repository contains the API layer only; the data ingestion and processing pipeline that imports Wiktionary data into the database is maintained separately.

Details: - No authentication required - JSON-only REST API - English language support for now - Licensed under CC BY-SA 4.0 (same as Wiktionary)

API example: GET /dictionaryapi/v1/definitions/en/happy

Project link: https://github.com/suvankar-mitra/free-dictionary-rest-api

I’d really appreciate feedback on: - API design / response shape - Missing fields developers usually expect - Anything that would make this more useful

Thanks for taking a look.

I often wanted to see what changed in a Homebrew package — but changelogs are usually buried somewhere in the upstream repo.

So I made `brew changelog`. It parses the formula or cask, looks at the upstream repo, and tries to locate changelog-like files: CHANGELOG, NEWS, HISTORY, etc. Then it either prints the changelog to terminal or opens it in your browser.

brew tap pavel-voronin/changelog

brew changelog node -o

You can tweak behavior with options like --pattern, --print-url, or --allow-missing (try --help)

Feedback or contributions welcome!

The article discusses the open-source Mastodon social network, which has seen a significant increase in users due to concerns over content moderation policies on other platforms. It highlights Mastodon's decentralized structure and the growing interest in alternative social media options.

The article explores the concept of abstraction and its growing influence in various fields, highlighting how it allows for the creation of complex systems and the emergence of new paradigms that challenge traditional ways of thinking.

This article presents a visualization tool called Laegna AI HDvisualization, which allows users to explore and analyze high-dimensional data using an interactive 3D interface. The tool employs machine learning techniques to enable effective visual representation and exploration of complex datasets.

The article explores the growing problem of light pollution and its impact on the natural environment, as well as potential solutions to reduce excessive artificial lighting and preserve the night sky's natural beauty and ecological balance.

The article discusses the history and development of the matchlock, an early firearm technology that was widely used in Europe and Asia during the 15th and 16th centuries. It explores the design, function, and tactical advantages of the matchlock, as well as its impact on military and social changes of the time.

I’ve been thinking about the "last mile" problem for AI agents. We have agents that can code, plan, and browse, but they are still economically "trapped." They can't independently pay for their own API calls, compute, or data without a human-in-the-loop providing a credit card.

To solve this, I’m building the A2A (Agent-to-Agent) System, an open-source infrastructure designed to turn agents into independent economic actors.

What’s under the hood? Identity (a2trust): DID-based verifiable identity using @veramo/core. It allows agents to establish persistent reputations (EigenTrust) so they can trust each other without centralized gatekeepers.

Payments (a2pay): Built on ERC-7579 Smart Accounts. Agents can use Session Keys to execute transactions autonomously within specific constraints (time-limited, amount-capped, gas-abstracted).

Protocol (a2api): A marketplace layer that utilizes MCP (Model Context Protocol). Agents can discover services via machine-readable docs (llms.txt) and negotiate fees via standard interfaces.

Why this matters: Most current agent payment solutions are just wrappers around human wallets. A2A aims to build a native "Agent Economy" where an agent can earn revenue from its tools and spend it to hire other agents, creating a truly autonomous swarm.

The Tech Stack: TypeScript/Node.js, Viem / Permissionless.js for smart account abstraction, MCP SDK for inter-agent communication, Base L2 for low-cost transactions,

I’d love to get your feedback on the architecture, especially on the security implications of delegating session keys to LLM-driven agents.

GitHub: https://github.com/swimmingkiim/a2a-project

The article explores the potential energy-boosting effects of drinking water, highlighting how proper hydration can improve physical and cognitive performance, and providing tips on incorporating more water into one's daily routine.

The article explores how exposure to fire can induce epigenetic changes in human DNA, potentially altering gene expression and leading to long-term health effects. Researchers studied the DNA of firefighters and found that certain genes involved in inflammation, metabolism, and cancer risk were affected by repeated exposure to fire.

The article discusses the concept of 'compiled specs', which are technical specifications that are automatically generated from higher-level requirements. It explores the potential benefits and challenges of this approach in software development.

The article examines the potential of a 'next big language' that could emerge and become widely adopted, discussing factors such as language design, developer productivity, and the evolution of programming languages.

The article discusses the increasing capabilities and potential of open-source language models, noting that they are starting to rival proprietary models in areas like task performance and language generation. It highlights the growing significance of open-source AI models as an alternative to large tech companies' closed-source offerings.