OpenClaw, Hermes, Poke를 쓰며 느낀 단점들

내가 만약 워크스페이스 에이전트를 만든다면 어떻게 만들까?

메모리

• 육하원칙에 맞게 기억해야하는데, 이걸 잘 못 함
  • 맥락을 종종 헷갈려함
• 메모리 툴을 명시적으로 불러야 함
  • 이는 Hermes에서 많이 완화된 부분

Slack

• 답장을 매번 하려 함. 쓰레드에 달리는 모든 글에 답을 함.
  • 매번 답할 필요는 없음. 필요할 때만 하면 됨.
• 언급하지 않은 메시지는 읽지 않음.
  • 모든 워크스페이스의 변화를 계속 보고 있어야 함, 그리고 기억해야 함

An unfortunate dope technology that has been stained by a bad use-case (stealing licensed products)

• https://sciop.net/
• Files are in 256kb chunks.
• At any given time, everyone has different chunks.
• The client will regularly ask for the list of chunks my peers have.
• The client will request the rarest chunk to the server
• The client sends chunks to the top 4 inbound chunk senders
• Re-evaluate every 10 seconds
• Every 30 seconds, send chunks to random peers

Articles

Building a BitTorrent client from the ground up in Go

• This mechanism allows us to verify the integrity of each piece as we go. It makes BitTorrent resistant to accidental corruption or intentional torrent poisoning. Unless an attacker is capable of breaking SHA-1 with a preimage attack, we will get exactly the content we asked for
• Now that we have information about the file and its tracker, let's talk to the tracker to announce our presence as a peer and to retrieve a list of other peers. We need to make a GET request to the announce URL supplied in the .torrent file, with a few query parameters
• can communicate using the BitTorrent protocol
• can understand and respond to our messages
• has the file that we want, or at least knows what we're talking about
• Therefore, it's essential to pipeline our requests to keep up with the constant pressure of some unfulfilled requests. This can increase the throughput of our connection by order of magnitude
• Notably, I left out all the glue code, parsing, unit tests, and the boring parts that build character. View my full implementation if you're interested