#Struct

believe or not, there is this vendor on h1 that has a strict rule on accepting vulns that only work on their scoped target (so far so good) but i've noticed since i've been delivering them pre-auth RCEs, the vendor keeps making the remote instance "offline" and sometimes put the device in a sort of "unreachable" state, first i wasn't suspicious, but then after getting a root shell on their device i did some digging and realized they're playing a nasty game of slowing me down on purpose and silently doing some patches behind the scene without putting the report in triage state and i got solid proof for their nasty configs and infra changes. I'm 90% close on saying "fuck it." and drop the remaining pocs just to teach a lesson, cause they keep playing it as "no we havn't touched anything, everything is normal" @Hacker0x01 do you give a shit if i go public and shame this vendor? cause fuck if i do.

final life spoilers . . scott flirting with bigb but the polycule strict as hell 😭

We have an update on dad. He’s been in the hospital since Friday night. He’s not showing any signs of improvement with his kidney numbers, they have unfortunately gotten worse. His doctors are keeping him under strict on site observation the next 48 hours. If they do not see improvement, the next step is dialysis. My dad is already in heart failure, dialysis would not be easy on him..

I just received the most devastating news, dad has been feeling weaker in his legs and knees and they have confirmed his Kidney Disease has advanced to Stage 5, which means Kidney Failure at the hospital today. I just hate that I can’t do anything for him and I can’t make it better. I am absolutely beside myself today in the worst way.

Excited to deploy this update, which now clearly shows the feeds which have unread threads. Moreover, you can now select "unread" from top to only show unread threads. #struct

As an Agentic AI Engineer, you must build these projects. 1.) Async Agent Orchestrator Build: A FastAPI + asyncio event loop handling 100+ concurrent agent tasks with non-blocking tool calls and graceful error recovery. Why: `while True` loops block the main thread. Real-world agents require event-driven concurrency to survive production traffic. 2.) Dynamic Context Budget Assembler Build: A pre-flight middleware that strictly allocates tokens across system prompts, retrieved docs and tool schemas per request. Why: Context overflow is the #1 silent killer of production agents. You must budget tokens like you budget cloud spend. 3.) Strict Pydantic Tool Router Build: A tool execution engine that forces LLM outputs into strict JSON schemas and automatically retries with the error trace on validation failure. Why: Agents hallucinate API parameters. Grammar-constrained decoding and Pydantic validation turn stochastic outputs into deterministic actions. 4.) 3-Tier Memory & Eviction Engine Build: A memory system with working scratchpads, episodic session compression and semantic vector search with automated TTL eviction. Why: Infinite context causes OOM errors and hallucinations. Memory must be actively managed, scored and pruned. 5.) Self-Healing ReAct Loop Build: An agent that reads its own stack traces, parses the compiler/API error, rewrites the failing tool call and retries up to 3 times. Why: Agents that fail on the first try are useless. Agents that debug themselves are digital employees. 6.) Typed Multi-Agent Swarm Build: A LangGraph state machine where a Researcher, Coder and Reviewer agent pass strictly typed state objects, never raw text. Why: Single agents fail on complex tasks. Swarms divide and conquer but raw text handoffs cause context drift. 7.) Async HITL Slack Gate Build: A workflow that drafts a high-stakes action, serializes its state and waits 3 days for a human to click "Approve" via a Slack webhook. Why: High-stakes automation requires human accountability. Agents must know how to pause, wait, and resume cleanly. 8.) Trajectory Eval CI Gate Build: A GitHub Action that replays 100 agent trajectories and blocks the PR if the tool-call sequence deviates from the golden DAG. Why: Grading the final text output hides the fact that the agent hallucinated an API call or skipped a safety check to get there. 9.) OpenTelemetry Agent Tracer Build: Custom tracing spans capturing every LLM hop, token count, tool latency and state mutation in LangSmith or Arize. Why: You cannot debug a 14-step agent workflow if you can't replay the exact sequence of events that led to the failure. 10.) Inter-Agent Sanitization Proxy Build: Middleware that intercepts messages between agents, stripping malicious instructions to prevent cross-agent prompt injection. Why: Multi-agent systems create internal attack surfaces. Agent A can be tricked into hijacking Agent B's tools. 11.) Sandboxed Code Executor Build: A code-interpreter agent that writes and executes Python in an isolated E2B or gVisor microVM with zero internet egress. Why: Letting an LLM run `os.system()` on your host machine is a catastrophic security risk. 12.) Cost Kill-Switch Middleware Build: A router tracking loop depth and projected spend that instantly halts the agent if it exceeds $0.50, falling back to a cheaper model. Why: A runaway agent loop is an outage with an invoice. It will burn $500 in API credits before you notice. 13.) API-to-Browser Fallback Agent Build: A routing layer where if the primary REST API 404s or times out, the agent seamlessly spawns a headless browser to finish the GUI workflow. Why: The real world is messy. 80% of enterprise software has no API. Agents must adapt to broken environments. 14.) Shadow Trajectory Comparator Build: A silent 5% traffic mirror that runs a new agent topology in the background, diffing tool-call paths and costs without affecting users. Why: You cannot A/B test non-determinism safely in production without shadow mode. 15.) Public Architecture Teardown Build: 3 published deep-dives detailing your swarm topology, state-machine design, inter-agent security and cost-per-task analysis. Why: Top AI labs hire Agent Engineers based on their system design judgment not their ability to import LangChain. Systems that prove you can orchestrate, secure & scale when autonomous agents touch your stack. Most people watch tutorials. Builders ship systems. Bookmark & Repost.

If I had 6 months to become an Agentic AI Engineer. I'd do this. Stage 1: Python + Async Foundations asyncio, FastAPI, event-driven architecture, error handling, API integration patterns. Stage 2: LLM Fundamentals for Agents Context management, model routing, token economics, latency tradeoffs, failure modes. Stage 3: Tool Calling + Structured Outputs Pydantic validation, function calling schemas, error recovery, dynamic tool discovery. Stage 4: Memory + State Management Short-term buffers, long-term vector recall, context compression, cross-session sync. Stage 5: Single Agent Workflows ReAct loops, plan-and-execute, self-reflection, iteration limits, graceful degradation. Stage 6: Multi-Agent Orchestration LangGraph/CrewAI, supervisor patterns, message passing, conflict resolution, handoffs. Stage 7: Human-in-the-Loop Systems Uncertainty detection, approval gates, audit trails, resume logic, intervention points. Stage 8: Evaluation + Quality Assurance Automated eval harnesses, LLM-as-a-judge, regression testing, hallucination metrics. Stage 9: Observability + Tracing Distributed tracing (LangSmith/Arize), cost dashboards, latency monitoring, alerting. Stage 10: Security + Guardrails Prompt injection defense, output filtering, PII redaction, sandboxed execution, compliance. Stage 11: Production Deployment vLLM/SGLang, Kubernetes scaling, CI/CD for agents, canary releases, rollback strategies. Stage 12: Open Source + Portfolio Ship autonomous agents publicly, write architecture docs, record demos, contribute to libs. Most people stay stuck watching tutorials. Builders get hired. (Bookmark it)

Derive more! 🔥 🦀 derive_more: Derive traits for structs and enums to avoid boilerplate. 📚 Docs: ⭐ GitHub: #rustlang #derive #struct #enum #boilerplate #programming #library #opensource

When your masonry blockwork is laid within strict plumb techniques, plastering becomes a accurate thin coat operation rather than an expensive structural correction.

Finish 100%

🦠𝙈𝙄𝙉𝙏 𝘽𝙀𝙂𝙄𝙉𝙎 𝙄𝙉 7 𝙃𝙊𝙐𝙍𝙎... 🧪𝙏𝙃𝙀 𝙄𝙉𝙁𝙀𝘾𝙏𝙄𝙊𝙉 𝙄𝙎 𝙎𝙋𝙍𝙀𝘼𝘿𝙄𝙉𝙂... 𝙍𝙞𝙙𝙞𝙘𝙪𝙡𝙚 𝙩𝙝𝙚𝙢... 𝘾𝙤𝙣𝙩𝙖𝙞𝙣 𝙩𝙝𝙚𝙢... 🖥️☄️💥 #Struct #MintingSoon #NFTdrops #NFTCommunity #NFTart #PixelArt #MintingNow

took a while to get these all collated together, but excited to share latest SlopCodeBench (scbench dot ai) findings. Shouts out @gorlanski for helping put this together - findings should make it into the main results leaderboard soon.

.@StructFinance : An Introduction to BTC.B-USDC Vaults Thread 🌟 1/ Bitcoin's dominance in the crypto industry is undeniable. As the heart of the market, its trend shifts guide investment decisions. We introduce a game-changing development in the crypto space: BTC.B-USDC Vaults

2/ Bitcoin ETFs have been a significant factor in the recent market surge. With asset managers applying for ETFs, it's clear that traditional finance is embracing Bitcoin on a new level. Struct Finance is leveraging this trend with its innovative product. #BitcoinETFs #Struct

BNB Chain is gearing up for a massive shift they are aiming straight for that trillion dollar TradFi capital but there is an obvious hurdle here. institutions require strict privacy we see layer 1 networks fighting hard for institutional TVL right now the main issue is public transparency. it is a complete roadblock for bank compliance teams they cannot expose their sensitive data on a public ledger for everyone to track this is exactly why BNB brought @primus_labs into their strategy PRIMUS plugs right into the BNB privacy ecosystem it allows these large funds to verify their offchain data while keeping everything confidential providing the exact security and compliance that big money demands before entering DeFi BNB is upgrading its whole infrastructure for this you can test this exact privacy layer right now and get ahead run your own data verifications on primus XP here

1) Avalaunch #Xava uzun süredir süren sessizliğini bozdu ve yaklaşan İdoları açıkladı. Bu haber bile Xava'nın hacimli bir yükseliş yapmasına yetti. #Deltaprime #struct #movement #levrbet #aethergames #pulsar #arcadegalaxy

雨が多かったので、いつから履こうか迷っていたblueover @struct_store の「mieky」を遂に履き下ろし👟高級な靴を履く機会が少ないので当分の間は緊張しなが歩きます💦 #blueover #struct #スニーカー #スエード #デザスプ #ボードゲーム #ボドゲ

おはようございます🌂 今朝は尊敬するご家族がご来店🙇欲しかったこちらの冊子を直接頂きました✨京町堀のstructさんで貰えます👟 本日もデザスプは22時まで営業🚪2テーブル空き。雨が降りそうですが雨宿りボドゲ是非‼️ #blueover #struct #日本製 #スニーカー #国内産業の継続 #渡利ヒトシ #デザスプ

صبح بخیر و اول هفته مبارک به خانواده Struct و #AVAX تلاش ادامه می یابد و تیم Struct مشغول قرار دادن کارهای نهایی بر روی خزانه های Auto-pool است چه کسی آماده و منتظر است👀🔥 #Avalanche #Struct

She came for shopping, but the streets had other plans. Never mistake kindness for weakness. Seedance 2.5 on @frameo_ai #MadeWithFrameo Prompt: Create a highly detailed, photorealistic character and outfit reference sheet for a beautiful 24-year-old Korean woman, designed for a cinematic 30-second action video. Character appearance: A young Korean woman with long, dark brown wavy hair, soft bangs, fair natural skin, expressive dark brown eyes, delicate facial features, and a confident yet elegant appearance. Add a small gold hair clip on the side of her hair. Use natural Korean-style makeup, soft pink lips, subtle blush, and realistic skin texture. Main outfit — keep identical in every scene: - Cream-colored knitted cardigan with long sleeves and small buttons. - White fitted inner top with a modest neckline. - High-waisted charcoal-grey pleated mini skirt. - White ankle socks. - Clean white chunky sneakers. - Small structured black leather handbag with short handles and a shoulder strap. - Minimal silver necklace and tiny earrings. - Small gold hair clip. Creator sheet layout: 1. Large front-facing portrait. 2. Face close-up from the front, side, and three-quarter angle. 3. Hairstyle reference from the front, side, and back. 4. Full-body front view wearing the complete outfit. 5. Full-body side view. 6. Full-body back view. 7. Detailed close-ups of the cardigan knit, buttons, white top, pleated skirt, sneakers, handbag, jewelry, and hair clip. 8. Seated pose inside a city bus. 9. Standing pose at a modern Korean bus stop. 10. Walking pose outside shopping stores. 11. Determined expression for the action scene. 12. Calm, confident final expression. Visual direction: Premium Korean movie character design, realistic fashion photography, neutral studio background, soft daylight, accurate fabric textures, natural anatomy, consistent body proportions, clean editorial layout, clearly separated reference panels, 16:9 landscape format, high resolution. Strict consistency rules: The character must have the same face, age, hairstyle, hair clip, outfit colors, skirt length, shoes, accessories, and handbag in every reference image. Do not randomly change the clothing between scenes. Only facial expressions, body poses, lighting, and camera angles may change. No extra fingers, distorted anatomy, duplicate accessories, logos, or watermarks.

#Rust makes it really easy to #initialize a #struct from another struct's data, by #filling in the gaps #automatically for you using the struct #update #syntax 😍 Collection of Rust #tips and #tricks: #tipoftheday #rustlang