summaryrefslogtreecommitdiff
path: root/content/blog
diff options
context:
space:
mode:
authormms <michal@sapka.me>2024-06-28 14:57:08 +0200
committermms <michal@sapka.me>2024-06-28 14:57:08 +0200
commitd6ac0fc244cc0666bae99833c7e5e835308b9eb9 (patch)
tree7b8db2a69ca69614d86eedeb54a2b4faaad96667 /content/blog
parent9566717e717438cee59e6f251a8234b5164f56b5 (diff)
chore: lazy load content images
Diffstat (limited to 'content/blog')
-rw-r--r--content/blog/2024/llm-honeypot.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/content/blog/2024/llm-honeypot.md b/content/blog/2024/llm-honeypot.md
index aa6240f..33c7c57 100644
--- a/content/blog/2024/llm-honeypot.md
+++ b/content/blog/2024/llm-honeypot.md
@@ -21,7 +21,7 @@ Identifying them? Good luck. Not only the IPs are in _millions_, but they lie in
Some are trying to poison the LLM by prompt injection, but this will not work in any bigger dataset.
Personally, I want to at least try.
-Therefore, my site contains a honeypot: _open [a gi repository](https://michal.sapka.me/git/mms/Library-of-knowledge) and your IP will be logged_.
+Therefore, my site contains a honeypot: _open [a git repository](https://michal.sapka.me/git/mms/Library-of-knowledge) and your IP will be logged_.
For now I collect them, but soon they will be blocked on my firewall for some time - a week maybe?
This repo is: