Not sure I'd read it as-written. But I'd love a statistics book whereby the chapters are real case studies. I personally learn best when I can apply new theory to a tangible problem (not just an example problem that's been reduced to almost nothing).
However going the 'visual' route might be enough for me to pick it up.
Anubis is significantly better than Cloudfare from a ux perspective because it doesn't require interacting with the page. Being gated by turnstiles and having to stop what youre doing while you're waiting is infuriating. To say nothing of Google hard blocking people it doesn't like out of websites and alluding to moving towards ID verification for its captchas.
You sound like a child throwing a tantrum. Before throwing around insults calling people post-teenager, you should maybe look at your own behavior. Is adult behavior getting angry to the point of swearing because you saw a cartoon character?
People like you are why keeping the anime furry in Anubis is a soft requirement. You can really sort the wheat from the chaff by deliberately pissing off the wrong people.
It's funny, because on the scale of things that are annoying an uncool, I find someone saying the word "retarded" as a pejorative in the year 2026 to be far, far more annoying and uncool than a harmless anime-inspired mascot for an open source project.
> Wow. @Meta settled for $18B, also agreeing to implement significant protections for teens. They'll of course choose the weakest / least effective implementation possible but even so - governments are beginning to force change.
>
>2 years ago, it looked hopeless. Big moment.
That Tweet shows that he is pro "protecting minors from social media", and "governments should do that protecting"
Ignore my account if you wish. The handling of memories as the corruption through conflation and obfuscation of the original is widely accountable.
The part of the holographic memory is unexplored for obvious reasons (beyond modern scientific reach.) Many individuals extraordinary behaviors may be explained by the lack of neurological access by others, not information storage availability.
I've met you (Steve) and hung out with him for a few hours after oxidize. He's none of those things, and in fact was one of the most pleasant people I've met at conferences. So not only are they brazen and vulgar allegations but I can't see even a distant parallel universe where they're even close to true.
Also no need to install or commit to a guild or clan or whatever. You could just log in, screw around for an hour or ten, and log off. Then log in again from somewhere else. It was miraculous for a kid like me.
ARM is great. Love it. There are tons of chips that all do things differently, much more so than x86. Plus the booting mechanisms are a PITA to figure out, debugging is tricky, etc - and that's a single target. x86 isn't particularly elegant given its years of cruft and questionable design decisions but at least it's quasi-consistent (yes, lots of "well actually" possible; I'm speaking broadly).
The ISA on ARM is better, IMO, than x86 but the surrounding ecosystem is hellishly fragmented. Just my $0.02. makes it difficult for OSdevers to find an 'in' to a wider ARM audience. rpi is a great entry point.
I believe spetz is on the project, so I'd like to ask:
Is this a MQ implementation, or can this be used in place of e.g. something like protobufs and iroh/tonic? Does it have something akin to grants/capabilities/authorization? Does it have RPC? Can I have services speak a more privileged set of instructions/commands and clients needing auth to speak dumber/more high level administrative commands just like gRPC?
Also, is the performance due to the (what I assume is custom) zero copy serialization?
The landing page simply states it's essentially "fast messaging" but beyond that it's not entirely clear when I'd use this or what its features/limitations are.
It's more like Kafka or Pulsar in terms of being the message streaming infrastructure (so an append-only log, not the message broker like, e.g., raw RabbitMQ). I think that the main docs page should give you a good understanding of how the data is stored/organized https://iggy.apache.org/docs/ - for example, on top of the topics, we also have "stream" which is just an extra hierarchy that can be used for something like multi-tenancy isolation or anything else depending on the use case. And yes, there's a built-in RBAC (read/manage particular streams, topics, servers, etc.). As for protocols, we have native support for TCP, QUIC, WebSocket (these 3 are stateful binary protocols), and HTTP as well.
There are a bunch of things that sum up to the overall performance gains - using Rust, thread-per-core architecture + shared-nothing (think of Seastar), custom zero-copy serialization, io_uring for disk * network I/O, and VSR-based consensus (inspired by TigerBeetle) - we simply build all this stuff from the ground up to make the most out of modern hardware and Kernel features, with a custom protocol on top (but the Kafka proxy/gateway is also WiP). And there are also connectors (sink, source), benchmarking runtime, CLI and so on.
How is client logic support for different languages designed in your project?
Some time ago I found Kafka clients for several languages are pretty much unusable due to bugs and/or performance non-debuggability. The reason, I think, was that the client logic is quite complex and each client project had to re-implement it from scratch (or use some C FFI monstrosity - which was pretty much a dead end too).
reply