Fizzadar

So is this AGI+ now?

I just hope this becomes the law everywhere (or at least, selfishly, in the UK).

This is why people pirate.

Victorian brick houses are all lime based, pointing (mortar between bricks), render outside and internal plaster. (Ours is 140 years old ish).

Lime is also more flexible (these houses have minimal to no foundation and constantly move), it’s breathable (no/less damp) and as such it also improves air quality indoors. It’s annoying to do because drying times are days/weeks not hours, but long run it’s a far superior material for small buildings.

It does burn though if you accidentally get it on your skin!

It wears down quicker than concrete (you can scratch it easily with a nail and minimal pressure). But we’re still talking 50+ years (before repointing brick, in my case). As long as maintained it’ll last forever (our home is 140 years old, I just re-did the pointing, should be good till I die).

Posting it because I just started watching and it’s simultaneously funny and utterly, utterly depressing. Is this really where we’re going?

- https://pyinfra.com - Python infrastructure management, been picking up pace recently trying to keep on top of PRs!

- https://kanmail.io - always plugging away at Kanmail changes, no one uses it really except me but that’s fine :) new site designed by fable blew my mind

- https://verified.fyi - first side project started initially as a vibe coding experiment, but it’s become quite good at sussing out dodgy websites

Reminds me of a similar effect around iPhone releases (https://www.statista.com/chart/2514/iphone-releases/, many others). Can’t say I’ve noticed any change.

Somewhat ironic that the site is completely broken on mobile, the text doesn’t render until you scroll near past it. Production code eh?

Exactly! Would like to understand more how that came about. PEP exists for a reason.

Indeed! (I am that original contributor :)), lots of work ongoing to address this, we now have a small maintainers group and are sharing out review and release loads.

This! Been trying to find the best (least worst) solution to this since 2015 when I started pyinfra. Done ast parsing/hacking, done weird context managers instead, tried rewriting statements to context managers. _if is the latest, and I think least worst, option right now.

Basically a flaw of the entire model where you write code as if executing a single host which is then executed on many in parallel, forcing the two step diff and deploy that causes this.

Funny thing is since v3 this behavior (diff then execute) is even desired with the yes prompt like terraform.

Pyinfra creator here - thank you so much for all the kind words, really means a lot to myself and the other maintainers, feeling the love.

Absolutely zero sympathy. You’re responsible for anything an agent you instructed does. Allowing it to run independently is on you (and all the others doing exactly this). This is only going to become more and more common.

One silver lining this is finally going to push me to switch to a dedicated camera and some niche unrestricted Linux or graphene device as a phone. Goodbye iPhone. (I say this as someone with an Apple account old enough to auto “qualify”, how lucky).

Also parent in the UK - strong disagree, it’s part of our parental responsibilities to set this up, not doing it is the same as not watching a newly walking baby on the stairs (/etc). Compromising everyone’s privacy for a subset of lazy parents is a failing of society.

I’m predicting a wave of such incidents to start appearing over the next few months/years.

There's https://happy.engineering/ which already does this with many fewer bugs and supports codex.

All of these agent wrappers/claws/whatever seem to encourage wildly irresponsible usage of AI. Sure it can get stuff done in what is effectively a simple loop but without review we’re just playing with fire.

I was experimenting with Claude code doing similar (don’t need wrappers really) and the result was a huge amount of mediocre code and my weekly limit burnt. The code “works” but oh my the duplication and potential bug surface is off the chart.

Stopped my experiment and back to human in the loop plan->execute cycle which is way more effective.

Thankfully I don’t think we’re at jarvis levels yet.

Worse than yesterday I reckon - no status page update, actions/etc are delayed by 15-45 minutes, some just never run. Bit of a mess!

Damn I ripped all our telephone lines out and ran cat6 up through the house to my office and I could have just done this?! Well shit.

http://pointlessramblings.com (though ramblings are rare these days!)

As a primarily Go dev - 100% agree. The endless check and wrap error results in long chains of messages you have to grep for to understand the call stack. For what benefit? Might as well just panic and recover/log the stack in many cases.

The key here is a singleton sequencer component that stamps the new versions. There was a great article shared here on similar techniques used in trading order books (https://news.ycombinator.com/item?id=46192181).

Agree this is the best solution, I’d rather have a tiny failover period than risk serialization issues. Working with FDB has been such a joy because it’s serializable it takes away an entire class of error to consider, leading to simpler implementation.

Absolutely fascinating. Hubble pictures are always mind blowing.

Eight, but half of them exist as long running test accounts for Kanmail (kanmail.io) so arguably do not count. I do use them for legit emails though, new services usually get one of four test emails.

I have Spotify premium but the constant shuffle of content availability has meant I’ve stared routinely archiving my liked songs to avoid any rug pull. Zspotify and co still work a charm.

In my experience building Kanmail neither Tauri or Wails have this figured out. I had to combine elements of both projects custom linuxdeploy GTK plugin and I’m still not 100% sure it works everywhere. https://github.com/Oxygem/Kanmail/blob/19c5bfe78fe1b22147c01...

Nvm - dupe of https://news.ycombinator.com/item?id=46083004

> Airbus said in a statement that a recent incident involving an A320-family aircraft had revealed that intense solar radiation may corrupt data critical to the functioning of flight controls.

And this is addressed via software update?