futurisold

7 ms·

1.
The OnlyFans Economy of American AI(leoveanu.com)
146 points by futurisold 3mo ago|204 comments
2.
The Wild Cyberwest(xm4ch1ne.github.io)
3 points by futurisold 4mo ago|0 comments
3.
by futurisold 5mo ago
Hi HN. I wrote a deep dive into the math behind the XOR metric used in DHT networks. It turns out it perfectly maps onto the bizarre, 19th-century idea of p-adic numbers. I included a few interactive visualizations to make the ultrametric
4.
by futurisold 6mo ago
How I use agentic coding.
5.
Who Watches the Provers?(leodemoura.github.io)
2 points by futurisold 6mo ago|0 comments
6.
The Soothing Mendacity of Echoes(futurisold.github.io)
2 points by futurisold 7mo ago|0 comments
7.
by futurisold 7mo ago
why isn't this on the main page already? it's something very useful and well-done!
8.
Alignment at its Weakest Link(futurisold.github.io)
1 points by futurisold 7mo ago|0 comments
9.
What Bleeds Through(futurisold.github.io)
1 points by futurisold 7mo ago|0 comments
10.
Evolving Narratives(futurisold.github.io)
2 points by futurisold 10mo ago|0 comments
11.
by futurisold 1y ago
Thank you to everyone for participating in the discussion and for your overall support! As I said, I didn't expect this. I'm always just an email or tweet away, so you know how to reach me. It was great talking to you all!
12.
by futurisold 1y ago
Oh, definitely. I recommend you go for contracts. I've used something similar for a contract that iteratively "stitched together" a broken ontology graph. Here's some of the data models for inspiration -- you could have
13.
by futurisold 1y ago
Thanks for bringing this up. I'm fairly familiar with Peirce's triadic semiotics and Montague's semantics, and they show up in some of my notes. I haven't turned those sketches into anything applied yet, but the design s
14.
by futurisold 1y ago
I'd argue it's all of them. Contracts simply make better agents. I believe it also gives a very nice bias on how to talk about agents -- as apps obeying contracts. If you find time, please read this blog post; it gives the underly
15.
by futurisold 1y ago
It's subjected to randomness. But you're ultimately in control of the LLMs's hyperparams -- temperature, top_p, and seed -- so, you get deterministic outputs if that's what you need. However, there are downsides to this
16.
by futurisold 1y ago
This is the correct view. Since the instruction was ambiguous, the LLM did its best to satisfy it -- and it did.
17.
by futurisold 1y ago
Yes, that's correct. If using say openai, then every semantic ops are API calls to openai. If you're hosting a local LLM via llama.cpp, then obviously there's no inference cost other than that of hosting the model.
18.
by futurisold 1y ago
We hear you. We might end up renaming it. In the paper we have a footnote about the name choice -- it's meant to credit the foundational work of Newell and Simon that inspired this project.
19.
by futurisold 1y ago
Oh, thank you; refactoring artifacts. Fixed now.
20.
by futurisold 1y ago
+
21.
by futurisold 1y ago
That's very kind of you, thank you. Let's sync and see if we can align on something. You can find me on X, or shoot me an email at leo@extensity.ai
22.
by futurisold 1y ago
I'm struggling to understand the question. I'll revisit this when I wake up since it's quite late here.
23.
by futurisold 1y ago
Shortly, yes to all. We actually had an experiment going from theory of mind to emotion, but it's hanging right now since I feel the models aren't quite there yet and it yields diminish returns relative to effort. But could easily
24.
by futurisold 1y ago
Wolfram's also too busy running his TOE exps to focus on LLMs (quite sadly if you ask me).
25.
by futurisold 1y ago
> I'm surprised that they haven't revamped it No worries! I can't find it right now, but Wolfram had a stream (or short?) where he introduced "Function". We liked it so much we implemented it after one day. Usage
26.
by futurisold 1y ago
Thank you! I'm not familiar with that project, will take a look
27.
by futurisold 1y ago
One last comment here on contracts; an excerpt from the linked post I think it's extremely relevant for LLMs, maybe it triggers an interesting discussion here: "The scope of contracts extends beyond basic validation. One key obser
28.
by futurisold 1y ago
Very nice, bookmarked for later. Interestingly enough, we share the same timeline. ~2yo is when a lot of interesting work spawned as many started to tinker.
29.
by futurisold 1y ago
Btw, besides the prompt, the other input to the technical report (the gdrive link) was this repo: https://github.com/elder-plinius/CL4R1T4S/tree/main
30.
by futurisold 1y ago
Yes, pretty much. We wanted it be functional from the start. Even low level, everything's functional (it's even called functional.py/core.py). We're using decorators everywhere. This helped a lot with refactoring, extend

More ›