dominiek
Joined 19 years ago
Joined 19 years ago
1. Adding MCP/plugins creates a lot of overhead in the context window. For example you can see Figma taking up large base prompt and tool listings.
2. As agentic wrappers get more bloated, the system prompt grows. The memory facility is a good example. It's a wholly unimpressive mechanism taking up a large part of the context window.
3. Perhaps the most revealing thing is the security constraints that are just part of the prompt. The "auto mode" for permissions is just part of the system prompt.
As impressive as LLMs are, it seems that the only way to control this statistical beast is to add stuff to the base prompts. "IMPORTANT: Don't talk about goblins".
What if the actual crime is committed by those that control our money...
Saifedean Ammous' book "The Bitcoin Standard" gives an excellent history of hard money and shows that any new form of hard money will inevitably replace the lesser form (e.g. from the silver standard to the gold standard).
Crypto is composed of interesting projects and scams. Gambling and speculations are symptoms of a wider problem of debased currency and a lack of hard money.
Bitcoin fixes this...
Talking about Bitcoin in the same vain as Crypto shows a profound lack of understanding of history both past and recent when looking at Bitcoin.
While people trade their little Pokemon NFTs Bitcoin will be doing what Bitcoin has been doing from the beginning: Staying exactly 21 million bitcoin - the scarcest and most accessible form of hard money the world has ever seen. It's a black hole sucking in monetary inflation.
1 Bitcoin = 1 Bitcoin.
If I had any influence on the protocol it would be HTTPs. This is why I wasn't expecting to build an FTP server in 2020.
I'm making the maintenance of this less painful by doing a hacking/debugging session with manufacturers once a month where we hook up many devices and fix issues. After addressing most edge cases fewer are coming up now (despite a relentless stream of new cheaply manufactured devices)
- Scaling requirements are relatively low. Even though we're dealing with 10 thousands of devices, the amount of firware updates at a given time to those devices is minimal. Our main scaling challenges are around OCPP over websockets. Story for another day.
- I have bad memories of ProFTPd etc buffer overflow exploits.
- I wanted something simple that could bridge between FTP and our cloud persistence (MongoDB and Cloud Storage).
- I found this Node.js library that I since then forked: https://github.com/autovance/ftp-srv - The great thing about this library is that it allows a quick implementation of a custom filesystem.
- For Kubernetes pods the file system should really be treated as a /tmp - which we are doing.
- When a charge station connects, the FTP username/password is a temporary generated set of tokens that is checked against our MongoDB.
Essentially, I'm using FTP as a throwaway here.
If you think through this you can imagine it would be quite a lift to accomplish this with an existing FTP server.