Dutch 'idealist' bank ASN blocks non-Google Android, including GrapheneOS

Gemini Omni 1.2 Flash

Blender's UI and Runtime: Much Faster Than GPUI

Claude Code sends your email address to websites

We've built an open-source feature flag server for 11 years

Living beyond the limits of survival: wood ants trapped in a gigantic pitfall (2016)

Related:<a href="https:&#x2F;&#x2F;hachyderm.io&#x2F;@damienmiller&#x2F;117563026759098135" rel="nofollow">https:&#x2F;&#x2F;hachyderm.io&#x2F;@damienmiller&#x2F;117563026759098135</a> &#x2F; <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=50377221">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=50377221</a><a href="https:&#x2F;&#x2F;www.openssh.org&#x2F;releasenotes.html#10.6p2" rel="nofollow">https:&#x2F;&#x2F;www.openssh.org&#x2F;releasenotes.html#10.6p2</a><a href="https:&#x2F;&#x2F;alpinelinux.org&#x2F;posts&#x2F;2026-11-05-openssh-password-authentication-bypass&#x2F;" rel="nofollow">https:&#x2F;&#x2F;alpinelinux.org&#x2F;posts&#x2F;2026-11-05-openssh-password-au...</a>

sshole

Kugelblitz – Mac-Native Google Earth Alternative

Tesla winds down Cybertruck production after years of poor sales in few markets

Mbodi AI (YC P25) Is Hiring Research and Robotic Engineers

MS Paint Remote Code Execution Vulnerability

From Linux to Wikipedia: How Volunteers Build the Internet

Pwn.college

The Hackintosh Reborn

Multiplayer tanks that demolish real buildings from OpenStreetMap

Nvidia Kubernetes Engine (NVKE)

Hardcoded credentials and other issues in Tata Motors App

Inkling 2 Small

Britain to make salary disclosure in job ads mandatory

Window Sweaters

Chomsky and the Two Cultures of Statistical Learning

Can Democrats effectively abolish Electoral College after midterm wins?

Hi HN, we have been developing with Firebase for a long time, and the only way Firebase developers can build apps without directly costing them is using the official Firebase Emulator Suite.However, the issue with this suite is, it&#x27;s dependent and running on Java with a old Console UI (not updated in years), that was not built to support tons and millions of data and has pretty bad developer experience. For a long time, we were hitting Out of Memory on even high specs laptop while developing and the worst part is while this happens all the persists data keep getting lost.We were honestly frustrated with this, and thought what if we built the Firebase Emulator Suite the right way, as it always should have been.Introducing Firenook, a faster drop-in replacement for Firebase Emulator Suite for Firebase developers. It&#x27;s 40x faster writes and needs 10x less RAM to run it. We took the right approach of first building it Rust as a single engine, so that there will be no Java dependencies and built from scratch a new Console UI using modern web stacks.The result is, now we were able to run 2 millions datas loaded to Firenook with only taking around 2GB ram compared to 22GB of the official suite. Things are way faster and rebuilt Console UI gives best developer experience from logging Firebase Functions, to editing Firestore documents in JSON and many more.We developed this throughly for around 2 months now and ran this internally for a month before we decided it&#x27;s time to release it to public so that other devs can make use of Firenook and also contribute it to make it better.Firenook is still new and I&#x27;m sure it misses things. So please try it our on your project and let us if there are any issues.Thank you.

Show HN: Firenook – Firebase emulators in Rust: 40× faster writes, 10× less RAM

Motorola Signature 27 with GrapheneOS support

Hey HN, this is Nathan and Nicholas from Rivet (<a href="https:&#x2F;&#x2F;rivet.dev">https:&#x2F;&#x2F;rivet.dev</a>) – a fast, high-density, and scalable orchestrator for agentic workloads using the actor model. Rather than running a heavyweight sandbox per agent, each agent gets a lightweight actor backed by S3.Actors provide a long-lived process for long agent turns, in-memory state for context, a WebSocket server for multiplayer, durable SQLite storage backed by S3, and hibernation when idle.It&#x27;s a similar model to Cloudflare Durable Objects, but it’s open source and self-hostable.Here’s a video walkthrough: <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=3Ev6I7DOV9c" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=3Ev6I7DOV9c</a>When we went through YC in 2023, we were building infrastructure for multiplayer games like Diep and Krunker. This involved heavily optimizing high-throughput matchmaking, real-time player messages, and blitz scaling. Through that process, we spent a lot of time on workloads where Postgres couldn&#x27;t keep up with our throughput. We started out by hacking together Lua scripts on top of Redis, but this became too cumbersome to maintain and upgrade. This led us to extend our game server orchestrator to support what we call Rivet Actors today: many lightweight workers with in-memory state and durable storage. By using actors, we were able to serve tens of millions of monthly active users.As agents grew in popularity, it became clear that running agents in sandboxes is inefficient. Sandboxes are expensive, mostly idle, and slow to start. Developers started using actors because they are far more memory efficient (72 KB baseline for actors vs 512 MB for a minimal sandbox) and fast to start (4.9 ms p99 for actors vs 1.7 s p99 for sandboxes).For example, Amp is using Rivet to orchestrate multiplayer agents. They originally tried to build on Cloudflare Durable Objects, but couldn’t launch because of the platform’s limitations and unresponsive support. They migrated to Rivet Actors in a weekend and deploy on-prem. Rivet’s flexible architecture lets them adapt it to their own use cases without being constrained by a framework or the memory, storage, and runtime limits of Cloudflare Durable Objects.Under the hood, Rivet is backed by S3 while maintaining SSD speeds.Why S3? Previously, Rivet ran on FoundationDB. However, we were surprised to find that companies are storing orders of magnitude more data on Rivet Actors than in Postgres, such as large session transcripts, agent artifacts, and full POSIX filesystems. As their data grew, they had to start paying for SSDs that sat mostly idle with old transcripts. This led us to double down on S3 as our primary storage medium without sacrificing performance. This choice means that data stored on Rivet is 10× cheaper than on EBS gp3 while maintaining SSD speeds.It’s not as simple as writing data straight to S3. Lots of PUTs for tiny blobs of data are slow and expensive. Instead, we use an SSD tier to optimize speed and cost:When you write data to an actor’s SQLite database, the write is acknowledged once SSDs in 2 of 3 availability zones have it. Then, the data is batched to S3 in the background. This means that S3 is never on the write path, which lowers latency and cost. When reading data or waking an actor, Rivet reads from SSDs if already cached and falls back to S3 if not. SSD caches can be tuned to meet your needs, giving you configurable tiered storage for your actors.This architecture lets Rivet provide 1.07 ms durable writes (3 AZ, p99), 1.36 ms reads (p99), and 138 ms reads from object storage (p99).We’ve spent a lot of time making sure that Rivet can run wherever you need it. Self-hosting requires deploying a single Rust binary with S3 as the only dependency, Rivet Cloud lets you deploy dedicated clusters on AWS or GCP in any region, and BYOC lets us deploy Rivet to your VPC without having to operate it yourself. Rivet also runs identically in local dev as in production, since Rivet is a lightweight binary that runs anywhereRivet Actors can be written in TypeScript or Rust. Out of the box, they support agents (Pi Durable), workflows, real-time, multiplayer, running AI-generated code, Durable Streams, and integrations with tools like Vercel’s Eve and Turso. See all of our available guides, or point your agent at them: <a href="https:&#x2F;&#x2F;rivet.dev&#x2F;docs&#x2F;#guides">https:&#x2F;&#x2F;rivet.dev&#x2F;docs&#x2F;#guides</a>Try it out now, by reading our quickstart guides (<a href="https:&#x2F;&#x2F;rivet.dev&#x2F;docs&#x2F;">https:&#x2F;&#x2F;rivet.dev&#x2F;docs&#x2F;</a>) or ask your agent: “Run npx skills add rivet-dev&#x2F;skills, then build a multiplayer chat agent and run it locally.”We’d love to get feedback on your experience with Rivet! We’re deeply invested in making Rivet an easy-to-self-host, flexible, and efficient way to run agentic workloads.GitHub: <a href="https:&#x2F;&#x2F;github.com&#x2F;rivet-dev&#x2F;rivet" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;rivet-dev&#x2F;rivet</a>Architecture: <a href="https:&#x2F;&#x2F;rivet.dev&#x2F;docs&#x2F;architecture&#x2F;">https:&#x2F;&#x2F;rivet.dev&#x2F;docs&#x2F;architecture&#x2F;</a>Benchmarks: <a href="https:&#x2F;&#x2F;rivet.dev&#x2F;docs&#x2F;benchmarking&#x2F;">https:&#x2F;&#x2F;rivet.dev&#x2F;docs&#x2F;benchmarking&#x2F;</a>Self-hosting: <a href="https:&#x2F;&#x2F;rivet.dev&#x2F;docs&#x2F;deploy&#x2F;self-host&#x2F;">https:&#x2F;&#x2F;rivet.dev&#x2F;docs&#x2F;deploy&#x2F;self-host&#x2F;</a>

Launch HN: Rivet (YC W23) – Scale and Orchestrate Agents on S3

My brother and I run a 2-person lab that trains our own generative video models from scratch. The ultimate goal is a set of creative tools that make it easier for anyone to make animation.Video models today are too slow&#x2F;expensive and lack sufficient controls. Creativity is an iterative process. You make, you tweak, you get better. In our opinion, they&#x27;re not usable yet for storytelling.When we set out to build Linum v3 (our next video model) earlier this year, the primary goal was to bring the cost envelope of inference down significantly. If our model is fast and cheap, it&#x27;s the first step (of many) towards useful creative tools.Typically, you see &quot;latent diffusion models&quot;. A VAE (Variational Autoencoder) compresses the input data into a smaller &quot;latent space&quot; and the diffusion model learns how to generate within this subspace.Over the past few months, we&#x27;ve been publishing our work on efficient pixel-space diffusion models. These throw away the VAE, having the diffusion model learn a latent-space optimized for its exact task.This serves 3 purposes:
1) Simplify Architecture (no 2-stage model training)
2) Faster Convergence (11x faster convergence vs. our latent diffusion counterpart)
3) Cheaper Inference (4x more aggressive token reduction in attention context-windows, without significant loss in quality)This past month we were pressure testing our latest architecture (Pyramid-JiT) by training a text-to-image model longer than the typical one-off experiment. Specifically, we trained it for ~$20K on 660M samples.We were surprised by the quality of results, so we thought we&#x27;d release it as open weights for the community (Apache 2.0). The research itself is already public, on our website.For us, it&#x27;s a big stepping stone towards cheaper video models, since pretty much all video models start as image models. We like to say these models have to learn nouns before they learn verbs.

Show HN: A decent text-to-image model trained for ~$20K (Apache 2.0 Weights)

I wish tech companies knew more about me

September in Servo: <progress>, rounded rectangles, and more

Cuban: Facebook knowingly runs AI deepfake scam ads; docs say $16B fraud revenue

Download your favourite YouTube videos