标签:#hack
找到 8339 篇相关文章
LLM spambots liked my Show HN post more than real people did
Washington blocks Kalshi's sports prediction market over state gambling law
Escape IntelliJ: Scala and Kotlin LSPs on Emacs Eglot
A Device Hidden in Cars Across the US Leaves Them Vulnerable to Hacking and Paralysis. Patch It Now
Dealerships installed alarms in millions of vehicles—and left them in even if the buyer didn’t want them. Now researchers warn they can be hacked to unlock, track, and disable cars.
Qwen-Image-3.0: Rich Content, Authentic Details, Deep Knowledge
Ask HN: Claude Code or Codex?
And why? I'd genuinely like to understand who is on which side and why. I'd also like to know, if you use one of them, what kind of subscription plan you have. (For example, I use Claude (max) [...])
Palantir in Europe: 40 documented customer relationships across 14 countries
What if they are all wrong? (2020)
Escape Analysis in Go: Stack vs. Heap Allocations Explained
ANSI escape injection in MCP servers: Hidden from humans, visible to AI
What I changed after building small-business calculator pages
I’ve been building a small set of calculator pages for freelancers and small-business owners. The first version was pretty simple: put the formula on a page, add a few inputs, show the result. That works for a demo. It does not always work for a real user. The more I worked on it, the more I realized the hard part is not the math. The hard part is making the page feel trustworthy when someone is using it for a business decision. Here are the changes that mattered most. 1. Explain the assumption close to the input At first I wrote explanations below the calculator. Most people never read them. So now I try to put small notes near the input itself. For example, if a calculator asks for payment processing fees, the user should not have to scroll down to understand whether that means percentage fee, fixed fee, or both. This is boring UI work, but it reduces bad inputs. 2. Show intermediate numbers A single final result can feel like a black box. For business calculators, I’ve found it helps to show a few intermediate numbers: subtotal estimated fees estimated tax net amount break-even number Even if the final number is the same, users trust it more when they can see how the result was built. 3. Avoid pretending the answer is exact Small-business math has a lot of messy edges. Taxes vary. Fees vary. Local rules vary. Some people include owner salary in cost. Some do not. A calculator should not act like it knows every detail. I now prefer wording like: estimated monthly amount or rough break-even point That feels less flashy, but it is more honest. 4. Make the empty state useful A blank calculator page is not very helpful. I started adding realistic default numbers or examples where it makes sense. Not because the default is “correct”, but because it helps the user understand what kind of number belongs in each field. This is especially useful for people who are not spreadsheet-heavy. 5. Keep the result easy to copy A lot of users are not trying to stay on the page. They
Linux kernel will support $ORIGIN, sort of
Modula-3 History Collection on Computer History Museum
Show HN: Ex Situ – Open-source spatial index of displaced cultural artifacts
Hi, I designed and developed a spatial index that maps museum artefacts as connecting arcs/hyperlinks from their origin site to institutional location/sources. The Index specifically looks at western/euro-american institutions and maps their collection categorised by them under Islamic art, Asian/African art, ethnological collections, Middle East, South America etc. Started as my MA thesis in 2022, kept building since, mostly solo with a little funding. Fully open source, self-hosted, AGPL-3.0,