enether

The permission thing is a killer to productivity, if you're running Claude I think it's more efficient to just run in a disposable sandbox (like exe.dev[1]) or in some form of docker container with permissions you're personally ok taking the risk with on a personal machine[2]

[1] - https://exe.dev/ is a new cloud provider with some very useful agent UX [2] - I built https://github.com/stanislavkozlovski/dclaude/ for this; not perfect but gets my job done on the rare occassion I need to run the coding agent locally

I have to say, it works pretty good. I tested it by creating a Kafka cluster here: https://x.com/kozlovski/status/2050943790580457646

In <15 minutes it got everything up and running - the Kafka brokers, the Kafka controllers, schema registry, Grafana. Pretty impressive

are there really no other maintenance tools that do this already? seems like a low hanging fruit?

the irony of using Claude to create this lol

Yeah, which is why this Ursa-for-Kafka (UFK) fork can be a drop-in replacement. It holds both the classic Kafka topics with disks, and the Ursa engine topics that have higher latency.

I agree with your assessment re: latency. I've been very vocal about this ever since this type of architecture came out.

It could also be that the world as a whole cares less about privacy today than they did seven years ago. Without a relative measurement from a similar platform, it's a bit of an empty statement

One thing that has certainly changed is that algorithms have become more aggressive. If your content isn't performing well, it gets hidden much faster and more aggressively than before. This makes sense when you consider it from the PoV of the platforms (they have much more content to choose from)

A very in-depth tool that acts as a easily browse-able reference to many Apache Kafka internals like configuration options, error types, the wire format (by version), config advice and version upgrade diffs.

They make $8-9B a year (~90% profit margins) selling software to mainframes, which were deployed ages ago but still have to be maintained because critical COBOL business code was written on their systems - and migration is too riskly/costly.

To give you an idea:

- of the risk in regulated industries like banking: a UK bank was once fined *$62 million* for botching a mainframe migration and causing downtime. - of the difficulty and risk in non-tech industries: Australia once spent *$120 million* trying to migrate its social security system off mainframes... and failed.

Mainframes are not their only business, of course, but it's a major cash cow that's under appreciated. I, for one, didn't know that business keeps growing.

Coincidentally, I wrote about the topic of mainframes with relation to IBM's acquisition of Confluent here today: https://blog.2minutestreaming.com/p/ibm-confluent-acquisitio...

exactly. i posted about the same thing today https://x.com/twitter/status/2025949280251597291

It's an accelerant, both good and bad. How that plays out in companies where the majority are below-average is a nuanced and concerning case

I think it's worth it to build your own miniaturized versions of OpenClaw/claw-like agents. It's easy enough to build and the confidence of it being in a language you're familiar with, small enough surface area to limit risk, etc. seems worth it imo

In a way I think handing off digital tasks to an AI bot that does it behind the scenes IS reducing technology in your life.

But has to be done carefully to not increase the scope of things being done

we will need some sort of payment-block checkmark for use of social media soon enough. This claw phenomenon is opening the floodgates of spam even more than before

Mm, not at all. The usual LLM doesn't have its own file system, browser, persistent memory of all actions, etc. The usual LLM experience is you open chatgpt.com and have a singular chat session.

> I built this because running Kafka locally for development is painful — gigabytes of RAM, slow startup, ZooKeeper/KRaft configuration. I just wanted something that accepts produce requests and gets out of the way.

This is not true. Kafka's latest `-native` images are very fast to start up (~100ms) and use relatively little memory.

https://cwiki.apache.org/confluence/display/KAFKA/KIP-974%3A...

Would be cool to release the (miniscule amount of) code for this, and maybe have people standardize around a library for it.

Has anyone actually built event-driven agents yet? Or any agents, outside some basic dev workflows? (PR review, etc)

+1 from an European, it's beyond obvious and I don't understand why people are letting {politics, mainstream media painting of X} shape their belief on these extremely pressing and important issues.

Peter (the author) is a really, really cool guy. We recorded a 3hr 30m podcast[0] with him a month ago. For anyone interested in the Kafka space, performance optimization in Rust and the general "why yet another Kafka", I'd shamelessly recommend the video:

[0] - https://www.youtube.com/watch?v=pJQ7hcsI1Dw

to be fair, Kafka now has a GraalVM docker image[0][1] which was made for local dev/testing, and it has caught up fairly well to these alternatives re: memory and startup time

[0] - https://cwiki.apache.org/confluence/display/KAFKA/KIP-974%3A... [1] - https://hub.docker.com/r/apache/kafka-native

+1.

Bluesky is a left-leaning political mess - I strictly follow tech-only accounts yet get posts on the timeline about what this week's monstrous White House act was. This is not a judgement against the left, but rather against Bluesky.

As another example - the Bitcoin/cypherpunk community went to Nostr. Nostr today is the same slop as Bitcoin Twitter was before. It has a tiny bit more of an organic feel to it - but it basically spiralled to the same cookie-cutter attention-grabbing content. Things like mindless cat videos.

X as we know is already problematic.

Basically the current state is that all platforms suck

I didn't use AI in writing the post.

I did some research with it, and used it to help create the ASCII art a bit. That's about it.

I was afraid that adding the emoji would trigger someone to think it's AI.

In any case, nowadays I basically always get at least one comment calling me an AI on a post that's relatively popular. I assume it's more a sign of the times than the writing...

yes. apparently before Dec 19 too

I was definitely unaware. I suspected something like this may be up when I talked about the zero-review of the apparent PR "I’m not aware of Mongo’s public review practices". This is great to know though. Updating the piece now to mention this and explain the date discrepancy

thanks! updated

What an awful vulnerability. The most interesting fact is that this has been there since the PR that introduced it in 2017[1].

I'm not sure how Mongo's review process works, but it seems like this one had zero review.

[1] - https://github.com/mongodb/mongo/pull/1152

Warpstream (by Confluent (an IBM company))

For Rust-based Kafka alternatives, I like Tansu[1]. It at least provides Kafka API parity, and critically also gives users a pluggable backend (embedded SQLite, S3 for low cost diskless type workloads and Postgres because just use Postgres)

It’s nice to try and out innovate Kafka, but I fear the network effect can’t be beaten unless the alternative is 10x better.

Something like Warpstream’s architecture[2] had a shot at dethroning Kafka, but critically even they adopted the Kafka API. Sure enough, Apache Kafka introduced a competing feature[3] within two years of warpstreams launch too.

[1] - https://github.com/tansu-io/tansu [2] - https://www.warpstream.com/ [3] - https://topicpartition.io/blog/kip-1150-diskless-topics-in-a...

That is hilarious. The product looks like garbage to me. The business opportunity looks like it can be incredibly lucrative if it does catches on.

Aren't nanoplastics a larger concern?

All microplastics out in the open will degrade to nanoplastics at some point, and those find it much easier to infiltrate the human body. They penetrate the blood-brain barrier.

This leads me to believe that it's literally impossible to avoid. The air/water supply must be getting more poluted by the minute with these things

how is node failure handled? is this using KRaft or ZK?