e12e

Nice touch to have the ability to run the model after upload. Like a cross between a Quine and a Morris worm for AI.

But it'll only be truly fun when agents set up this for themselves, paying for the infrastructure by way of their onlyfan personas.

Wow, how did this not get discovered and fixed at the time of:

https://www.cve.org/CVERecord?id=CVE-2007-0882

Might be a 32 year old bug, but it's practically also a 19 years old exploit?

Ed: I'm confusing TFA with

https://nvd.nist.gov/vuln/detail/cve-2026-24061

Which seems pretty much identical with the 2007 cve.

In this case I suppose we can take the Ayatollah's word for it?

I'd say mobile and desktop (from same html) would be more like css zen garden, than light/dark.

Guess they need to hire an "idea guy" first?

Animated SVG of a pelican shaving with Occam's razor?

I instantly thought of Nielsen's personal homepage - http://useit.com - which has moved on to a little softer and corporate design - but still linger in the Internet Archive:

1996:

https://web.archive.org/web/19961227172043/http://www.useit....

2001:

https://web.archive.org/web/20010711195207/http://www.useit....

That's the beauty of asdf and then mise; they leverage existing solutions where possible, and unify how to get versioned runtimes for projects. Rust? rustup with mise, ruby? Precompiled when possible, otherwise ruby-build. Etc.

I'm not sure if I trust or want pnpm to support bundling rust for binary plugins, or various sundry toolchains.

But use what works for you.

> Why would you even use python without uv anymore

Probably wouldn't:

https://mise.jdx.dev/mise-cookbook/python.html#mise-uv

> have a system python binary and virtual envs linked to it

I'm not sure if you're saying avoid using system python?

In my experience so far, you never want to develop complex software locked to system versions of runtimes. Too often you need a bleeding edge feature, or conversely need to postpone updating due to needing an old version for some reason.

Object databases exist - they don't magically solve data(model|schema) migrations.

See:

https://zodb.org

https://gemtalksystems.com/products/gs64/

Equivalent to 10% year-to-year, every year - assuming 5 years. That is somewhat steep.

Hm.. I just tried on my Google pixel 7 Pro (obviously very different display - OLED) - and certainly seems like the result of a test conversion pdf2djvu should be at home on an eink screen. Not sure if there's a simple way to test on the only eink I have to hand; a Remarkable.

Fwiw google Gemini cane up with the following to convert pdfs on device in termux after some prodding (koreader can display DjVu):

You'll need access to storage:

termux-setup-storage

Then pipe/paste this to a script: (Sorry for the verbose slop)

Ed: moved to sibling comment

Nice. I keep wondering if these devices would play nicer with DjVu rather than pdfs and raster formats?

https://djvu.sourceforge.net/

You jest, but a wiki with a voting system might be a good fit for agents?

You could always stay with phpbb - seems it still feels authentic:

https://www.phpbb.com/community/viewtopic.php?f=14&t=2672425

(I'm guessing flarum.org makes more sense, though).

A cursory search didn't turn up any golang based modern and well maintained forums, which surprised me a bit.

Haven't the rogue openai agents already demonstrated that a wiki works well for this?

Ed: for posterity

https://www.reuters.com/world/europe/openai-agents-hijacked-...

> Each of these stories will be written just for you

Great, now you can ask for a feed and the AI will create an entire world of news filling your feed, your very own echo chamber.

5 years is no age for an UI kit! ;-)

I see that unison (file sync tool) seems to use: https://garrigue.github.io/lablgtk/

For Linux UI.

I strongly disagree. Incidental complexity is the enemy good emergent properties of a system; security, auditability, stability, testability, maintainability...

Useless depends on context here; I believe the idea is that each player gets a feeling of agency (they go in the order dictated by "their" luck, not leaving the decision to someone elses roll).

The most pragmatic would probably be to shuffle N cards from ace(one) through N - and let everyone draw).

But that doesn't involve dice.

Except that as a sibling comment mentions; that generalizes to any size of group - for six players you could roll one d6, and have "that" player go first.

But apparently the constraints are: every player rolls one die once.

I think it's more about guaranteeing the whole sequence, rather than who goes first?

At least for two players, if you use a two sided die (a coin), have player one win ties on ones, player two win ties of twos - and otherwise highest wins - then that is trivially done?

I would have to do a little more math to see if it generalizes by induction... I'm not sure you would get a guaranteed sequence - but I think at least guaranteed fair winner works by just increasing the die (7, 9 and 11 would be tricky because if physics again... I suppose. Unless you just ignore highest tie for missing player (reroll on extremely rare 9 9s on a d10 for nine players)?

Ed: I suppose we break smaller ties, by letting closest and highest win (for ten players, 4, 6 and 7 roll 5 - 6 is closest and over/highest of the close players to 5, then come 7?)

Ed2: nevermind we end up biased towards "high" players that often win on "high" ties, like 5 or 6.

Have you read Nelson?

One reason I have some hope for this approach is that we start by removing complexity by going to a static web site first.

We remove WordPress, database, configuration, templates - a lot of cruft.

Then we can add it back as needed for keeping edits and publishing simple. It might turn out we hardly need anything from 11ty, thanks to AI making editing more automatic.

I think (the collective) we, are (mostly by accident) building systems that are at least one dimension or level of higher abstraction than before AI.

Unfortunately with AI, higher abstraction doesn't automatically mean less complexity, or better managed complexity.

I think 95% of systems being built now with Al and on top of - or including Al - will turn out to be highly complected mountains of madness.

I'm not so sure the article is written with AI. I'd love to hear from the author on that.

Interesting. This and the other posts I've seen about Delta seems to exist in that liminal space, were it's difficult to tell if the author has had a brilliant insight, that they struggle to convey to anyone who's not yet had the same insight; or if they've simply gone slightly mad.

It's a similar sense I get with reading Nelson (after being able to think about his ideas for a while, I'm quite certain it was mostly genius and only a little bit of lunacy).

It remains to see how Delta will turn out.

On a side-note; my initial reaction to the headline was; no. Xanadu wasn't missing agents.

I do think I see where the author is going, though; and I think I agree that agents might be a new tool that might facilitate some hypertext ideas. Not Xanadu perhaps. But some other, more pragmatic and less magic place - but a place that is a little more magical than where we are now.

And it intersects a bit with an experiment we started at work; migrating our modest web site from WordPress to a static site combining 11ty (https://11ty.dev) (we already lean heavily on typescript for our application development) and visual studio code with frontmatter cms (https://frontmatter.codes) - and AI/LLMs.

AI helps with making a static page version of our site, and adopting to 11ty.

The idea is that with trivial push-to-deploy setup, our business people, with the help of AI in vs code, will be able to work directly with 11ty and git to make changes, do reviews and publish changes.

A hill that would probably have been too steep for them to climb just six months ago.

So in reference to the theme of realizing a better hypertext system with the help of AI, we're sort of doing the same thing, it turns out: mix solid, boring tools (static site gen, typescript, editor, version control, CI, static hosting) and some AI - to hopefully allow more users leverage both tooling and AI in an empowering way.

We've just stated the experiment - we may yet fly too close to the sun, and end up falling back to a traditional CMS.

> It'll take two or three more of these before I've seen enough to start gelling the domain problems in my head.

I don't understand - there's years of historical data to look at?

Potentially interesting - of it is at a minimum source-availble - preferably FOSS?

I assume it is vibe-coded, so would need a pretty thorough review before considering using it.

License and source availability not being on the page/faq suggest this is just a hobby project, I guess?

Just to clarify - for every seperate read, update or write to your database - you setup and teardown a new connection?