#HttpPost
A few days later, we identified a second variant, written in C, which remains in use to this day. As a DDoS botnet, it supports various DDoS commands. Initially, we 🔎 observed the following list:

➡️ httpflood
➡️ httpbypass
➡️ httppost
➡️ slowloris
➡️ tcp (syn, ack)
➡️ udp

The 🤖 botnet receives...⤵️
September 26, 2025 at 2:06 PM
Having a sneak peek under the hood of Pinch Payments at #DDDMelb
February 22, 2025 at 2:48 AM
[BLOGGED] How To: Semantic Kernel -Optimising Chat History When building agents you may hit LLM limits.

Learn how to avoid this in this blog post.

Info:

https://jamiemaguire.net/index.php/2024/11/23/semantic-kernel-optimising-chat-history/
Semantic Kernel: Optimising Chat History
When building agents using Semantic Kernel that integrate with SLMs (Small Language Models) /LLMs (Large Language Models), you typically send and receive multiple responses. A common pattern is to add all user and agent message to the ChatHistory object. In the past, I have done this by implementing a service class to handle these in .NET web applications. You can see an example of a controller which creates the chat history object for unique sessions for a webchat experience here: [HttpPost]   public async Task Post([FromBody] ChatRequest chatRequest)   {       // Use a fixed session ID for simplicity, or generate a unique one per user/session       var sessionId = default-session;       var history = _chatHistoryService.GetOrCreateHistory(sessionId);       // Add user input       history.AddUserMessage(chatRequest.Message);       var openAIProm
jamiemaguire.net
June 17, 2025 at 5:14 PM
そうだね🥺
具体的にいうならソフトA(httppostの機能がある)に不特定多数のぷゆゆが入力したメッセージを専用のブルスカアカウントでツイートしたいんだねぇ🥺
Googleスプレッドシートに入力したり、スパム対策前のしたらば掲示板にかきこんだりできたらしいから、ブルスカでもできるのではと思ったなさけ🥺
September 12, 2024 at 3:20 AM
[BLOGGED] How To: Semantic Kernel -Optimising Chat History When building agents you may hit LLM limits.

Learn how to avoid this in this blog post.

Info:

https://jamiemaguire.net/index.php/2024/11/23/semantic-kernel-optimising-chat-history/
Semantic Kernel: Optimising Chat History
When building agents using Semantic Kernel that integrate with SLMs (Small Language Models) /LLMs (Large Language Models), you typically send and receive multiple responses. A common pattern is to add all user and agent message to the ChatHistory object. In the past, I have done this by implementing a service class to handle these in .NET web applications. You can see an example of a controller which creates the chat history object for unique sessions for a webchat experience here: [HttpPost]   public async Task Post([FromBody] ChatRequest chatRequest)   {       // Use a fixed session ID for simplicity, or generate a unique one per user/session       var sessionId = default-session;       var history = _chatHistoryService.GetOrCreateHistory(sessionId);       // Add user input       history.AddUserMessage(chatRequest.Message);       var openAIProm
jamiemaguire.net
August 6, 2025 at 12:13 PM
[BLOGGED] How To: Semantic Kernel -Optimising Chat History When building agents you may hit LLM limits.

Learn how to avoid this in this blog post.

Info:

https://jamiemaguire.net/index.php/2024/11/23/semantic-kernel-optimising-chat-history/
Semantic Kernel: Optimising Chat History
When building agents using Semantic Kernel that integrate with SLMs (Small Language Models) /LLMs (Large Language Models), you typically send and receive multiple responses. A common pattern is to add all user and agent message to the ChatHistory object. In the past, I have done this by implementing a service class to handle these in .NET web applications. You can see an example of a controller which creates the chat history object for unique sessions for a webchat experience here: [HttpPost]   public async Task Post([FromBody] ChatRequest chatRequest)   {       // Use a fixed session ID for simplicity, or generate a unique one per user/session       var sessionId = default-session;       var history = _chatHistoryService.GetOrCreateHistory(sessionId);       // Add user input       history.AddUserMessage(chatRequest.Message);       var openAIProm
jamiemaguire.net
July 28, 2026 at 5:14 AM
Failed to load API definition error in Swagger for ASP.NET Core

There are various reasons cause the swagger to fail to load the API definition and you will get the error shared in the below screenshot. Below are the possible reasons, Swagger misconfiguration Controller methods without HTTP verbs…
Failed to load API definition error in Swagger for ASP.NET Core
There are various reasons cause the swagger to fail to load the API definition and you will get the error shared in the below screenshot. Below are the possible reasons, Swagger misconfiguration Controller methods without HTTP verbs (HttpGet, HttpPost etc.) Same class name etc…   Fig 1. Failed to load definition error in Swagger Solution: The Swagger can be launched by adding the ‘/swagger’ after your API URL which doesn’t show the error details causing the Swagger to fail to load.
som2nypost.com
August 7, 2025 at 9:43 AM
[BLOGGED] How To: Semantic Kernel -Optimising Chat History When building agents you may hit LLM limits.

Learn how to avoid this in this blog post.

Info:

https://jamiemaguire.net/index.php/2024/11/23/semantic-kernel-optimising-chat-history/
Semantic Kernel: Optimising Chat History
When building agents using Semantic Kernel that integrate with SLMs (Small Language Models) /LLMs (Large Language Models), you typically send and receive multiple responses. A common pattern is to add all user and agent message to the ChatHistory object. In the past, I have done this by implementing a service class to handle these in .NET web applications. You can see an example of a controller which creates the chat history object for unique sessions for a webchat experience here: [HttpPost]   public async Task Post([FromBody] ChatRequest chatRequest)   {       // Use a fixed session ID for simplicity, or generate a unique one per user/session       var sessionId = default-session;       var history = _chatHistoryService.GetOrCreateHistory(sessionId);       // Add user input       history.AddUserMessage(chatRequest.Message);       var openAIProm
jamiemaguire.net
June 12, 2026 at 5:14 AM
[BLOGGED] How To: Semantic Kernel -Optimising Chat History When building agents you may hit LLM limits.

Learn how to avoid this in this blog post.

Info:

https://jamiemaguire.net/index.php/2024/11/23/semantic-kernel-optimising-chat-history/
Semantic Kernel: Optimising Chat History
When building agents using Semantic Kernel that integrate with SLMs (Small Language Models) /LLMs (Large Language Models), you typically send and receive multiple responses. A common pattern is to add all user and agent message to the ChatHistory object. In the past, I have done this by implementing a service class to handle these in .NET web applications. You can see an example of a controller which creates the chat history object for unique sessions for a webchat experience here: [HttpPost]   public async Task Post([FromBody] ChatRequest chatRequest)   {       // Use a fixed session ID for simplicity, or generate a unique one per user/session       var sessionId = default-session;       var history = _chatHistoryService.GetOrCreateHistory(sessionId);       // Add user input       history.AddUserMessage(chatRequest.Message);       var openAIProm
jamiemaguire.net
May 1, 2026 at 5:14 PM
[BLOGGED] How To: Semantic Kernel -Optimising Chat History When building agents you may hit LLM limits.

Learn how to avoid this in this blog post.

Info:

https://jamiemaguire.net/index.php/2024/11/23/semantic-kernel-optimising-chat-history/
Semantic Kernel: Optimising Chat History
When building agents using Semantic Kernel that integrate with SLMs (Small Language Models) /LLMs (Large Language Models), you typically send and receive multiple responses. A common pattern is to add all user and agent message to the ChatHistory object. In the past, I have done this by implementing a service class to handle these in .NET web applications. You can see an example of a controller which creates the chat history object for unique sessions for a webchat experience here: [HttpPost]   public async Task Post([FromBody] ChatRequest chatRequest)   {       // Use a fixed session ID for simplicity, or generate a unique one per user/session       var sessionId = default-session;       var history = _chatHistoryService.GetOrCreateHistory(sessionId);       // Add user input       history.AddUserMessage(chatRequest.Message);       var openAIProm
jamiemaguire.net
March 24, 2026 at 6:14 AM
[BLOGGED] How To: Semantic Kernel -Optimising Chat History When building agents you may hit LLM limits.

Learn how to avoid this in this blog post.

Info:

https://jamiemaguire.net/index.php/2024/11/23/semantic-kernel-optimising-chat-history/
Semantic Kernel: Optimising Chat History
When building agents using Semantic Kernel that integrate with SLMs (Small Language Models) /LLMs (Large Language Models), you typically send and receive multiple responses. A common pattern is to add all user and agent message to the ChatHistory object. In the past, I have done this by implementing a service class to handle these in .NET web applications. You can see an example of a controller which creates the chat history object for unique sessions for a webchat experience here: [HttpPost]   public async Task Post([FromBody] ChatRequest chatRequest)   {       // Use a fixed session ID for simplicity, or generate a unique one per user/session       var sessionId = default-session;       var history = _chatHistoryService.GetOrCreateHistory(sessionId);       // Add user input       history.AddUserMessage(chatRequest.Message);       var openAIProm
jamiemaguire.net
December 24, 2025 at 9:05 PM
[BLOGGED] How To: Semantic Kernel -Optimising Chat History When building agents you may hit LLM limits.

Learn how to avoid this in this blog post.

Info:

https://jamiemaguire.net/index.php/2024/11/23/semantic-kernel-optimising-chat-history/
Semantic Kernel: Optimising Chat History
When building agents using Semantic Kernel that integrate with SLMs (Small Language Models) /LLMs (Large Language Models), you typically send and receive multiple responses. A common pattern is to add all user and agent message to the ChatHistory object. In the past, I have done this by implementing a service class to handle these in .NET web applications. You can see an example of a controller which creates the chat history object for unique sessions for a webchat experience here: [HttpPost]   public async Task Post([FromBody] ChatRequest chatRequest)   {       // Use a fixed session ID for simplicity, or generate a unique one per user/session       var sessionId = default-session;       var history = _chatHistoryService.GetOrCreateHistory(sessionId);       // Add user input       history.AddUserMessage(chatRequest.Message);       var openAIProm
jamiemaguire.net
October 13, 2025 at 8:05 PM
[BLOGGED] How To: Semantic Kernel -Optimising Chat History When building agents you may hit LLM limits.

Learn how to avoid this in this blog post.

Info:

https://jamiemaguire.net/index.php/2024/11/23/semantic-kernel-optimising-chat-history/
Semantic Kernel: Optimising Chat History
When building agents using Semantic Kernel that integrate with SLMs (Small Language Models) /LLMs (Large Language Models), you typically send and receive multiple responses. A common pattern is to add all user and agent message to the ChatHistory object. In the past, I have done this by implementing a service class to handle these in .NET web applications. You can see an example of a controller which creates the chat history object for unique sessions for a webchat experience here: [HttpPost]   public async Task Post([FromBody] ChatRequest chatRequest)   {       // Use a fixed session ID for simplicity, or generate a unique one per user/session       var sessionId = default-session;       var history = _chatHistoryService.GetOrCreateHistory(sessionId);       // Add user input       history.AddUserMessage(chatRequest.Message);       var openAIProm
jamiemaguire.net
September 19, 2025 at 12:13 PM
[BLOGGED] How To: Semantic Kernel -Optimising Chat History When building agents you may hit LLM limits.

Learn how to avoid this in this blog post.

Info:

https://jamiemaguire.net/index.php/2024/11/23/semantic-kernel-optimising-chat-history/
Semantic Kernel: Optimising Chat History
When building agents using Semantic Kernel that integrate with SLMs (Small Language Models) /LLMs (Large Language Models), you typically send and receive multiple responses. A common pattern is to add all user and agent message to the ChatHistory object. In the past, I have done this by implementing a service class to handle these in .NET web applications. You can see an example of a controller which creates the chat history object for unique sessions for a webchat experience here: [HttpPost]   public async Task Post([FromBody] ChatRequest chatRequest)   {       // Use a fixed session ID for simplicity, or generate a unique one per user/session       var sessionId = default-session;       var history = _chatHistoryService.GetOrCreateHistory(sessionId);       // Add user input       history.AddUserMessage(chatRequest.Message);       var openAIProm
jamiemaguire.net
August 28, 2025 at 5:14 PM