This was killed twice today already, and is related to this story, so if anyone else can vouch to unkill: https://news.ycombinator.com/item?id=47060078

The current one has already been killed once, and is flagged again.

I have set it up in a docker container that only has two host volumes mounted with the Obsidian vaults where I keep notes for two TTRPG campaigns, so a very low-stakes situation. I have set it up with a Discord bot so my players can chat about campaign and rules stuff (I already had player-facing notes for every session in the Obsidian vault in chronological order, plus a bunch of Markdown files with rules).

If the agent goes rogue and nukes my Obsidian vaults I have them backed up to Github private repos anyway which the agent cannot touch because I am not crazy to give it my SSH credentials.

I initially tried using Kimi-2.5 through OpenRouter and had the same experience you had with pretty bad tool use, not sure if this is a provider issue since it is a pretty new model. I switched to Gemini 3 through the Google AI Pro account I have for personal use and it was a lot smoother after that.

I have some experience with coding agents using Cursor for work and Antigravity for personal stuff, and the OpenClaw harness definitely seems worse, but for my low-stakes use-case I managed to paper it over with some edits to the AGENTS.md file.

But even in this very crude state it was already interesting to see one of my players giving the agent some info about his character, including an avatar image, and have the agent create a folder in my Obsidian vault to store this and update its memory file to be able to remember it for future interactions.

You only need row polymorphism if you want full type inference. You can get away with width subtyping with bounded parametric polymorphism if you are willing to give up on inferring all types. Examples: Go, TypeScript, Flow...

I don't know where the parent lives in Brazil, but the supermarket chain comment definitely has not been my experience in upper-middle class Rio de Janeiro neighborhoods.

People use Whatsapp instead of SMS because it simply is a better user experience, specially for sending media and group chat, not for showing off, or keeping in touch with relatives abroad. Phone companies began offering "free whatsapp" even in pre-paid plans because it because it became very popular, as a way to attract costumers, not the other way around.

you are probably a late adopter. 2010 it was used exclusively for overseas sms. Since nobody had it installed.

Then, after it was bought by facebook, they started to PAY telcos around the world to increase penetration and block any competitor.

...telcos offering something for free when they have a closed monopoly :) that was funny.

I forgot to tell in the message that there's also a mirror at http://fabiomascarenhas.github.io/lua/

Actually the "meat" of the course starts on unit 1, unit 0 is more of a recap of where Lua comes from and where it is used. :)

Try again next semester. Taking compilers is mandatory for comp. sci students, so they will have to bite the bullet and take it eventually, even if scared of Roberto (somewhat with reason; the course is easier than Coursera's Compilers course, but still a hard course for the undergrads).

OS/2 was actually quite good on underpowered hardware if you stuck to console apps running fullscreen. I started with OS/2 2.1 on a 40Mhz 386 with just 8Mb RAM, connecting to BBSes and reading FidoNet with a newsreader called Blue Wave and programming with the Boxer editor. OS/2 Warp was the first shrinkwrapped software I bought, still on floppy disks; I was quite proud of that as a 14 year old, as piracy was rampant in Brazil at the time.

I remember OS/2 was quite popular with both BBS operators and BBS users around here, as it was the easiest way to multitask on a PC in the early 90s. It had a quite vibrant shareware/freeware scene. You did have to be picky about hardware, though, but even here it was easy to find video cards, sound cards and modems that ran just fine.

You have to compare Lua at 1995 (version 2) to JavaScript at 1995, as its development, at least inside the browser, would be arrested the same way JavaScript's was. Lua 2 was certainly had a much better implementation than the first JavaScript, but I would not call it a better language (didn't have JavaScript's annoying quirks, but also didn't have closures, for example). 2000's Lua (5.0 and 5.1) is quite different from its earlier incarnations.

I can see a lot of folks just blocking Safari outright if Apple tried to pull this stunt...

That's exactly what I was thinking. As a producer of content, if a specific app is denying you an income, why would you not just block it.

Sure, you're turning away customers, but you're turning away customers that aren't paying.

Blocking would work for about five minutes, until someone releases a user agent spoofing plugin for Safari, just like the one that already exists on Firefox.

It exists under the Develop menu in Safari already. Also, there's no way Apple is going to do this, it's preposterous.