Omar A. Alani

introducing pierrejo for all the brotherin struggling to migrate off of github an open-source fully-functional pierre diff integration for PRs in forgejo consumable via nix flake instantaneous diff loading using pierre SSR enjoy

Noir v1 has been released 🥳 It’s been about four years since Noir started as my personal project and became an @owasp project. There have been many improvements along the way, and today we’re finally making the official 1.0 release! The goal of the tool is clear. to give humans, DAST, and AI clear endpoints and rich context information, while providing useful hints throughout the security analysis process. Several new features have been added, and most usage patterns from the v0 releases remain compatible. ◽️github.com/owasp-noir/noi… ◽️owasp-noir.github.io/noir/blog/noir…

@badlogicgames @mitsuhiko Ahh okey! Looks like overmind github.com/DarthSim/overm…

@omarluqq @mitsuhiko that's pipi's internal logs

the one thing @mitsuhiko taught me: merged client & server logs. very useful.

@buildwithsid github.com/omarluq

kindly share your github profile i wanna judge you

@broady @skvark Oh this is actually a really cool idea!

@skvark yeah! I mount all of GitHub in a VFS github.com/broady/ghfs

Wanna make your coding agent feel truly limitless? Give it access to all open source code so that it can grep, glob and read through it. Currently, it sees only your local system. That's what unlocked the current tier of capabilities. The next step is to let it see also inside all the dependencies.

@caps_raunak Hey 👋 Building zunesha.ai We are giving agents a full linux sandbox with root lvl access!

looking to connect people on twitter if you're into - building SaaS - vibe coding - AI tools - shipping in public - figuring it out as you go - designer - startup founders say Hi or drop what you're working on looking to follow active ones

@htmx_org I refuse to waste brain cells on such lost cause

lads, people are still defending graphql, it's go time

Composition over Inheritance in Go: The Design Choice That Makes #Microservices Boring in the Best Way #golang #dormosheio #architecture #backend dormoshe.io/trending-news/…

Should I add @_HermesAgent support to @Zuneshaai tonight? Ticket been on our backlog for a month now 😅😆

Types are intent, encoded. In the age of agentic coding, that makes them the highest leverage tool we have. The clearest way to tell an agent what you actually mean. I want them everywhere now.

@MicroLaunchHQ find me an early stage VC lol! building zunesha.ai we are going crazy giving agents full linux machines with root level access

Builders, how can we help you this weekend? Please be crazy.

@kushmergedeck Ore wa sandbox ou ni naru!

@omarluqq Mugiwaara interesting project

What are you building this weekend? Drop your project URL Let’s drive some traffic

> listen to what they are saying > trust me

@kamikaz1_k @ibuildthecloud Agents are where it bites. For untrusted, stateful, long lived runs the pod is the wrong unit. I’d want microVM or system container isolation, Firecracker, Kata, or Incus, under a thinner control plane.

@kamikaz1_k @ibuildthecloud Fair, training and agentic are different shapes and you’d stack them differently. For training, k8s + Volcano or Kueue with topology aware scheduling is solid

The cost of k8s makes sense for AI. I've always struggled with the cost of k8s for web workloads.

Opinion: Vibe coding only works well if you already know how to code

k8s was built to bin pack a huge fleet of workloads onto shared machines, run them, and let them die gracefully. Portability came free with the declarative API, it wasn’t the goal. And that ephemeral workload DNA is still in k8s, which is exactly why stateful gang scheduled AI feels forced.

@omarluqq @ibuildthecloud k8s is a scheduler / orchestrator of computational resources it was designed to make cloud lock-in less of a lock Could there be a more agent native orchestration system, probably, but it’ll still probably run atop of k8s…for now