frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

OpenClaw ClawHub Broken Windows Theory – If basic sorting isn't working what is?

https://www.loom.com/embed/e26a750c0c754312b032e2290630853d
1•kaicianflone•1m ago•0 comments

OpenBSD Copyright Policy

https://www.openbsd.org/policy.html
1•Panino•2m ago•0 comments

OpenClaw Creator: Why 80% of Apps Will Disappear

https://www.youtube.com/watch?v=4uzGDAoNOZc
1•schwentkerr•6m ago•0 comments

What Happens When Technical Debt Vanishes?

https://ieeexplore.ieee.org/document/11316905
1•blenderob•7m ago•0 comments

AI Is Finally Eating Software's Total Market: Here's What's Next

https://vinvashishta.substack.com/p/ai-is-finally-eating-softwares-total
1•gmays•8m ago•0 comments

Computer Science from the Bottom Up

https://www.bottomupcs.com/
1•gurjeet•8m ago•0 comments

Show HN: I built a toy compiler as a young dev

https://vire-lang.web.app
1•xeouz•10m ago•0 comments

You don't need Mac mini to run OpenClaw

https://runclaw.sh
1•rutagandasalim•10m ago•0 comments

Learning to Reason in 13 Parameters

https://arxiv.org/abs/2602.04118
1•nicholascarolan•13m ago•0 comments

Convergent Discovery of Critical Phenomena Mathematics Across Disciplines

https://arxiv.org/abs/2601.22389
1•energyscholar•13m ago•1 comments

Ask HN: Will GPU and RAM prices ever go down?

1•alentred•13m ago•0 comments

From hunger to luxury: The story behind the most expensive rice (2025)

https://www.cnn.com/travel/japan-expensive-rice-kinmemai-premium-intl-hnk-dst
2•mooreds•14m ago•0 comments

Substack makes money from hosting Nazi newsletters

https://www.theguardian.com/media/2026/feb/07/revealed-how-substack-makes-money-from-hosting-nazi...
5•mindracer•15m ago•1 comments

A New Crypto Winter Is Here and Even the Biggest Bulls Aren't Certain Why

https://www.wsj.com/finance/currencies/a-new-crypto-winter-is-here-and-even-the-biggest-bulls-are...
1•thm•15m ago•0 comments

Moltbook was peak AI theater

https://www.technologyreview.com/2026/02/06/1132448/moltbook-was-peak-ai-theater/
1•Brajeshwar•16m ago•0 comments

Why Claude Cowork is a math problem Indian IT can't solve

https://restofworld.org/2026/indian-it-ai-stock-crash-claude-cowork/
1•Brajeshwar•16m ago•0 comments

Show HN: Built an space travel calculator with vanilla JavaScript v2

https://www.cosmicodometer.space/
2•captainnemo729•16m ago•0 comments

Why a 175-Year-Old Glassmaker Is Suddenly an AI Superstar

https://www.wsj.com/tech/corning-fiber-optics-ai-e045ba3b
1•Brajeshwar•16m ago•0 comments

Micro-Front Ends in 2026: Architecture Win or Enterprise Tax?

https://iocombats.com/blogs/micro-frontends-in-2026
2•ghazikhan205•19m ago•0 comments

These White-Collar Workers Actually Made the Switch to a Trade

https://www.wsj.com/lifestyle/careers/white-collar-mid-career-trades-caca4b5f
1•impish9208•19m ago•1 comments

The Wonder Drug That's Plaguing Sports

https://www.nytimes.com/2026/02/02/us/ostarine-olympics-doping.html
1•mooreds•19m ago•0 comments

Show HN: Which chef knife steels are good? Data from 540 Reddit tread

https://new.knife.day/blog/reddit-steel-sentiment-analysis
1•p-s-v•19m ago•0 comments

Federated Credential Management (FedCM)

https://ciamweekly.substack.com/p/federated-credential-management-fedcm
1•mooreds•20m ago•0 comments

Token-to-Credit Conversion: Avoiding Floating-Point Errors in AI Billing Systems

https://app.writtte.com/read/kZ8Kj6R
1•lasgawe•20m ago•1 comments

The Story of Heroku (2022)

https://leerob.com/heroku
1•tosh•20m ago•0 comments

Obey the Testing Goat

https://www.obeythetestinggoat.com/
1•mkl95•21m ago•0 comments

Claude Opus 4.6 extends LLM pareto frontier

https://michaelshi.me/pareto/
1•mikeshi42•22m ago•0 comments

Brute Force Colors (2022)

https://arnaud-carre.github.io/2022-12-30-amiga-ham/
1•erickhill•25m ago•0 comments

Google Translate apparently vulnerable to prompt injection

https://www.lesswrong.com/posts/tAh2keDNEEHMXvLvz/prompt-injection-in-google-translate-reveals-ba...
1•julkali•25m ago•0 comments

(Bsky thread) "This turns the maintainer into an unwitting vibe coder"

https://bsky.app/profile/fullmoon.id/post/3meadfaulhk2s
1•todsacerdoti•26m ago•0 comments
Open in hackernews

Ask HN: Are you / should we be preparing for "cyberattack"

4•lifeisstillgood•3mo ago
Jaguar Land Rover was attacked, presumably by a ransomware attack (https://www.bbc.co.uk/news/articles/cy9pdld4y81o) costing an estimated 2Bn dollars.

What mistakes are such IT departments making? What actions are you taking to prevent it?

Comments

lhmiles•3mo ago
IP whitelist!
wowowoasdf•3mo ago
close server!
Bender•3mo ago
- Secure backups protected from being tainted by malware replicated to multiple locations and only ever shared as read-only.

- Treat most servers and clients as cattle, keeping end-user data on backed up and redundant hardened specific purpose servers in small very secured networks.

- Enable detailed logging in auditd and set it immutable to change conf requires reboot. Send important alerts to multiple SIEM servers.

- Avoid sending "noise" events to syslog/SIEM to prevent alert fatigue.

- Enable spooling and TLS TCP transport in the local syslog.

- Enforce mandatory access controls such as SELinux or AppArmor. Ensure all applications are fully enforced.

- All applications, 3rd party libraries go through strict security review, change control.

- No real time connections to 3rd party networks for dependencies. Everything is local in the datacenter or Cloud account after being code and security reviewed.

- Have a manifest per code deployment of all known checksums of all files. Use an in house tool to periodically verify checksums and alert real time on anything that is unknown.

- Run a tool to verify "Full RELRO", "Stack Canary", NX/Pax, "PIE" for all running daemons. Force teams to recompile anything missing these settings.

- Disable SSH multiplexing on bastion nodes and clients outside of development. Multiplexing empowers logless phishing

- Do not allow direct access to production servers just because there is a VPN. Require a highly logged jump host. If that is too much friction for someone move them elsewhere.

- Hire 3rd party code penetration testers to find "all the things". Fix all the things.

- Hire 3rd party penetration testers to find every real world weakness in the infrastructure. Have them sit with members of every org. Tell employees to volunteer anything they see as a weakness. Fire any C-Level that objects to this. Have buy-in from board members.

- Perform extensive background checks on all FTE candidates and executives. Limit access to contractors by default.

- Perform extensive background checks on all 3rd party vendors. Be ready to explain findings to customers, auditors, regulatory bodies, etc...

- Restore an entire production environment from scratch using only backups and code in a staging environment. Have volunteer customers that signed additional NDAs test the restoration. Do this on a regular schedule and ensure a non-technical manager with the appropriate access can follow the instructions.

- Perform chaos monkey testing killing random nodes, unplugging random things and ensure teams can either self-heal or be quickly remediated by novice engineers.

- Encourage red-team penetration testers to break things in a production-like staging environment. Have executives and board members make it clear there are no reprisals, no consequences for bringing up taboo topics around security due to in-house politics.

- Require a top-down culture of treating everyone equally. This includes treating executives that leave their laptop unlocked and unattended exactly the same as an FTE.

I could keep listing best practices but I think we know most will not do 5% of these checklist items. Alternately stock up on pens, pencils, physical notepads. Have printed out lists of phone numbers and addresses.

jakabia•3mo ago
Very good summary, thank you!
lifeisstillgood•3mo ago
Thank you