infogulch

Why? They get paid $10 every time spam is reported regardless of the outcome. Trained staff listening at 3x speed with AI assistance could classify 3 obvious spam calls in a minute. If you can't turn $1800/hr per employee into a profit center I don't know what to tell you. That's a lot of money to cover for extreme outliers.

Eventually the obvious spam callers would all quit and the volume would reduce to a handful of borderline cases. So the spam department wouldn't make a lot of money anymore, but the volume would be so low it would barely register.

The best technical solution I've seen is a spam review fee that turns into a reward and charged to the next closest originating peer.

For example say you get a spam call. You notify your service provider and pay $10 to have them review the call recording to verify that its spam. An employee listens to the call and determines that it is, in fact, spam. You get a $100 reward for reporting spam and your service provider forwards the charge (+10%=$110) to the peer network where the spam call originated. They will in turn forward it to the next peer, or if the originator is a customer, charge and/or close the offending account.

If this system is mandatory then the problem will quickly sort itself out.

Merged, thank you Richard! :)

Unfortunately their Zed agent is completely broken when running on Windows connected to WSL/SSH remote because the terminal tool checks for paths using the local Path style (windows) which breaks when applied to paths on the remote (linux).

I fixed this and a couple related issues in a PR but it hasn't gotten any attention yet. I guess they are a bit swamped. https://github.com/zed-industries/zed/pull/59937

Probably needed an excuse to rotate our stock out.

LLMs are very good at helping you manage DMARC/DNS related configuration, even as a non-expert. I used it to develop custom DMARC report processing app that: 1. sucks in reports sent to our dmarc inbox into a sqlite db, 2. displays the results in a web page. The reports queue up in the mailbox and I open and start the app once a month to check the status. The agent also also reviewed the state of email-related DNS records, describe what needs to change, including how and why, and verify changes after the fact to ensure they are correct.

Some changes I made at the direction of an agent: fix domainkeys CNAMEs for M365, rotate M365 dkim keys that haven't been rotated for over a decade, fix broken spf record formatting.

My biggest issue is that squarespace refuses to enable dkim signing for transactional emails that they send for us (order/shipping confirmation etc). The email sending service they use (socketlabs) supports it but they are not interested in enabling the feature, so I can't lock down our dmarc. I guess that means squarespace is not a good fit for our needs; it's just disappointing that we have to move to a different platform again for technical reasons that are solvable with a dashboard switch.

I put a path in my garden so I can continue to maintain the garden, and walk around and enjoy it. But oh no, my daisies are wilting because they're too close to the path. So I adjust the path, raise the bed a little bit, and add a border, and they're happy after a little bit of water.

Totally normal gardener behavior.

"be fruitful" and "replenish the earth" is already aligned

As for "subdue", ask anyone maintaining a large garden how much they have to work to keep it from reverting back to a wilderness. Gardening is choosing which species stay and which are forcibly removed and optimizing the environment to enable your chosen species to thrive. If the words "subdue" and "dominion" freak you out, pick your brains up off the floor and go touch grass.

Western civilization has decided that it wants to keep the primate species and is dissatisfied when they become roadkill, so it altered the environment to enable the chosen species to thrive. This article is a gardening success story. Gardening requires dominion. We have dominion over the primates and we have chosen to be benevolent with that dominion.

I guess another thing is once the related conversation is identified you can use some other mechanism to retrieve it all or in parts etc.

So you draw some distillates out of the conversation, do a vector embedding of each, and insert the pairs into pg. Then retrieval is distill -> find top N nearby vectors. Indexing, etc. Seems like a smart way to organize long term memory.

Also I can't help but notice that this solution combines technologies whose origins literally span 6 decades: relational databases (80's), vector embeddings (00's), and LLMs (20's).

What kinds of prompts do you use to get the distillates, and what shape are they? I guess I've been assuming you extract more than one distillation out of a conversation per memory access, do you?

Yes that would probably help!

LLMs are far from great writers. They struggle to form long coherent sentences and lean on punctuation like emdash and semicolon to ensure grammatical correctness when splicing together short phrases.

This makes me wonder if the reason why agents love weird punctuation is because the labs run the base models through a RL training step that forces them to correct their grammar; but instead of rewriting short spliced sentences into long coherent sentences, they just learn to splice them together with punctuation that passes the automatic grammar checker.

I'm not trying to be obtuse, and correct me if I'm wrong, but "context" is just words, often rendered as markdown because it's easy for both LLMs and humans to produce and edit. Since its in a database and they're not necessarily full documents, I'll use the phrase "markdown snippets" for now. Feel free to quibble with the phrasing, I'm trying to understand what it does.

You save 2 respectability points by using postgres over nosql. (joke)

> depending on their role/group assignment, its available to their AI client to recall

So you generate/extract markdown snippets from the local context of each agent along a few axes like: what problem the user is working on and their approach, what role they're acting as and tools they're using, etc, and store those snippets in a postgres db with indexes over the category.

So how is that then exposed to the receiving agents? Is it fully opt-in / pull only? Or do they get some related threads automatically injected in their context. What does it look like? "Jan was working on something similar yesterday, her agent found these docs helpful: a.md, b.md" ?

Lots of people have their own voice and tend to prefer certain phrases. This has been the case for a long time and is generally not a big issue.

Now LLMs come along and they also have their own phrasing preferences. But now it's a problem because what used to be personal preferences of a single person that manifests in 5000 words per day from one person tops, is now the bias of a single model multiplied x10,000,000,000 generated tokens per day so any bias sticks out like a sore thumb.

So instead of markdown files in a repo, it's markdown files in a nosql database?

Sure, maybe you can find a paint that is black in all bands except for the ones used by the satellite. It won't use carbon black.

The entire underside of these satellites is a big phased array antenna. Maybe you can paint it so it absorbs all the other wavelengths, but it would be counterproductive to absorb the radio wavelengths used by the antenna itself since ground emitters would have to increase the gain to get through it.

Couldn't we just permanently solve the stack copying issue by always using a per-stack base pointer + offset for all stack objects? Copy stack -> update base pointer -> done. Trying to access a stack object on a different thread? That's retarded don't do that allocate it on the heap instead.

> Some customers may have experienced unscheduled collaborative compute with external parties.

Reminds me of the hilarious "rapid unscheduled disassembly"

Sure, but one might imagine that linkers are generic and reusable, so you can just pick one off the shelf instead of making a new one 1-1 for each language. Empirically this line of reasoning seems to be incorrect.

Neat! Barcodes are much more complex that I knew before looking into it. I used JsBarcode [1] to create a special barcode that reprograms a cheap barcode scanner we got on Amazon to be able to scan both UPS and FedEx tracking numbers. It is published on CodePen [2].

[1]: https://github.com/lindell/JsBarcode

[2]: https://codepen.io/infogulch/pen/yyLJdrP

To me, paperless means they ATTACH MY STATEMENT TO THE EMAIL. Not signing up to any paperless until they do, none yet have met this bar. The statement is supposed to be a snapshot of the status of the account at a given moment, if you have to open their website to view it they could regenerate it from whatever crap data they have lying around at the given moment. If it can change every time you look at it, it's a quantum statement, it's not a snapshot, it's a vibe. This defeats the entire purpose of getting a statement, I don't know how anyone tolerates this.

Ah so the fork is permanent. How unfortunate, guess I need to avoid QNAP software entirely.

OpenZFS released the zpool expansion as stable last year. Hopefully QNAP is charting a path to allow their users to migrate from their fork to OpenZFS, though of course these kinds of things take time to develop. I would be really worried if they are diverging further from OpenZFS rather than converging.

IPC scopes would be a great solution!

Anybody used a tinybox? https://tinygrad.org/#tinybox

The most "affordable" option is red v2 with 64GB GPU ram and costs $12,000. This is only ("only") 1.5x-3x the price of a beefy desktop (https://pcpartpicker.com/builds/), and could crush inference work even on bigger models. It could support coding tasks for a small team of developers, or run an AI agent for every person in your household...

I'm happy to hear you really care about perf.

I might have assumed io_uring would be the high throughput kernel interface for Linux.

Can iroh run on a proxy server which forwards requests to backends that don't integrate with iroh directly?

What is the CPU overhead at link saturating speeds?

How does Iroh's performance compare to wireguard?

io_uring taught us that if syscalls are expensive, queue them up in a buffer with one syscall to transfer the thread to the os to process it. So, queue up the new process mutations in a buffer with a single syscall to process all of them in a batch. This model should have replaced repetitive syscalls across the kernel years ago.

I guess you can try again when you post the video.