Hacker News

Article URL: https://altertable.ai/blog/2026-07-15-lakehouse-as-context-store

Comments URL: https://news.ycombinator.com/item?id=48932378

Points: 1

# Comments: 0

Article URL: https://busy.app/

Comments URL: https://news.ycombinator.com/item?id=48932341

Points: 1

# Comments: 1

Article URL: https://blog.frankrousseau.fr/15-years-of-free-software-projects-a-review/

Comments URL: https://news.ycombinator.com/item?id=48932317

Points: 2

# Comments: 0

Hey HN,

Something I've been tinkering with in the background is a system to manage the "messy-middle" of TypeScript toolchains. Quite often, when I'm using Biome or any of the other linter / formatters, there will be repo conventions that I want to enforce (especially with AI agents), but which aren't supported by them, such as:

- Enforcing lines-of-code limits in modules - Never using custom TailWind colors - Only using lowercase underscores in filenames

Like, this is quite "random" but also bread-and-butter stuff that it's easy to think or talk about when you're working by yourself or with a few other human teammates, but I've found that agents consistently miss these conventions if I put them in an AGENTS.md file for example.

I wanted to make my esoteric repo conventions less stochastic, and more deterministic. I realised that agents are adept at writing the kind of code needed to run arbitrary checks on the TypeScript AST or workspace environment -- the kind of code that is cumbersome to write as a human.

So, I've made Pokayoke (https://pokayoke.codes) and would like your feedback! It's a small library that gives agents a place to test and store rules for enforcing conventions, and provides a skill to create those rules super easily. So you can come up with any arbitrary rule you like, get your agent to write a piece of code that enforces it, and then have it be included in your Pokayoke checks that get done (with one command) next to your other linting and formatting checks!

Fun fact: the name comes from the Japanese term for "mistake-proofing" or "error-prevention"[0].

[0] - https://en.wikipedia.org/wiki/Poka-yoke

Comments URL: https://news.ycombinator.com/item?id=48932314

Points: 1

# Comments: 0

Article URL: https://master.dev/blog/ai-generated-ui-is-inaccessible-by-default/

Comments URL: https://news.ycombinator.com/item?id=48932310

Points: 1

# Comments: 0

Article URL: https://investor.uber.com/news-events/news/press-release-details/2026/Uber-Announces-Acquisition-Offer-for-Delivery-Hero/default.aspx

Comments URL: https://news.ycombinator.com/item?id=48932277

Points: 3

# Comments: 0

I started working on this project last year and open-sourced it this year.

It’s a library to scan byte payloads within JS using YARA-syntax rules, enabling YARA malware detection rules to run anywhere that JS runs (e.g. browsers, email clients, Office add-ons etc). However, it goes beyond core YARA by adding runtime context signals to the rule evaluation, so users can write detections like “encrypted PDF being downloaded from an unfamiliar website” or “executable downloaded from service-worker enabled site”. It started for security applications, but can also be applied to DLP and compliance.

I come from the EDR and web security world, so I take inspiration from gaps that I find there. In this case, I wanted to improve threat detection in payloads downloaded via the browser.

File scanners sit outside the browser and rely on OS notifications to trigger a scan when a file is downloaded. The file scanner knows it came from Chrome but doesn’t know the website, referral chain or user interaction preceding the download. This context information could be useful in identifying 0-day threats where signatures are not yet available. I started exploring if it were possible to embed an inline scanner within the browser to use flexible rules and block downloads before they materialized on disk. I did not want to invent a new rule language, so I picked YARA as it is well-established and open-source. I first coded the YARA engine in vanilla JS, including modules, so it could be run in any JS runtime. I thought of cross-compiling to WASM but stuck with vanilla JS because I wanted to add runtime-specific customizations, which were easier to do in vanilla JS. Once the YARA engine was ready, I added an extra metadata object that could be passed and used in the rule syntax. This was done using the custom module route, to maintain compatibility with YARA. This became Intercept.js.

The open-source repo includes a lot more information about the implementation, videos, some coding examples and a hosted instance on Cloudflare Workers to try out

It would be great to find collaborators interested in refining the project. I am presenting this at BlackHat Arsenal and DEFCON Demo Labs, so I’m happy to meet folks there to dive into more technical details.

Thanks!

Comments URL: https://news.ycombinator.com/item?id=48932269

Points: 1

# Comments: 0

Article URL: https://www.bargo.ai/research/slow-takeoff-fast-spending

Comments URL: https://news.ycombinator.com/item?id=48932261

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=48932259

Points: 1

# Comments: 1

Article URL: https://www.flanner.io/

Comments URL: https://news.ycombinator.com/item?id=48932248

Points: 1

# Comments: 0

Article URL: https://github.com/Skyvern-AI/rustwright

Comments URL: https://news.ycombinator.com/item?id=48932230

Points: 2

# Comments: 0

Article URL: https://www.smh.com.au/business/workplace/no-hiring-if-an-ai-can-do-the-job-staff-at-mining-giant-told-20260713-p60eth.html

Comments URL: https://news.ycombinator.com/item?id=48932218

Points: 2

# Comments: 1

Article URL: https://research.mozilla.org/browser-competition/over-the-edge-2/

Comments URL: https://news.ycombinator.com/item?id=48932214

Points: 1

# Comments: 0

Article URL: https://zayenz.se/blog/post/gecode-6-3-and-6-4-released/

Comments URL: https://news.ycombinator.com/item?id=48932205

Points: 1

# Comments: 0

Article URL: https://micro.mu/blog/post?id=build-your-own-apps

Comments URL: https://news.ycombinator.com/item?id=48932198

Points: 1

# Comments: 0

Article URL: https://blog.codacy.com/ai-code-review-is-not-enough-how-engineering-leaders-should-gate-ai-generated-code

Comments URL: https://news.ycombinator.com/item?id=48932183

Points: 1

# Comments: 1

Article URL: https://8bit.gioorgi.com//

Comments URL: https://news.ycombinator.com/item?id=48932178

Points: 1

# Comments: 2

Article URL: https://play.google.com/store/apps/details?id=com.gpsmapcamera.gpscameratimestamp.photo.video&hl=en_US

Comments URL: https://news.ycombinator.com/item?id=48932168

Points: 1

# Comments: 0

Hi, I don't have a long history as OSS builder but I'm now focusing on a project which is keeping me busy and I want to maintain it in the long term.

The problem I'm facing is that I have the OSS part (code, public docs, etc) but also some private assets (private docs primarily, my personal notes, AI iterations, etc) which I don't want to push publicly. At the same time I don't want to keep the private stuff local only as they are valuable assets and they might get lost, so gitignore is not a solution.

So I am now maintaining 2 repos, one private and one public, I push to private then with a script I copy over (public) assets into the public one. But this is a lot of overhead and it's giving me headaches for many reasons.

Have you ever faced this before? What could be a smooth solution?

Cheers

Comments URL: https://news.ycombinator.com/item?id=48931944

Points: 1

# Comments: 0

Article URL: https://seatunnel.apache.org/blog/modern-data-stack-to-agentic-data-stack/

Comments URL: https://news.ycombinator.com/item?id=48931935

Points: 1

# Comments: 0