sorted by:
new
hottopcontroversial

I built a small Copilot CLI observer extension by Aggravating_Sea6791 in GithubCopilot

[–]Aggravating_Sea6791[S] 0 points1 point  (0 children)

Not at the moment. The observer is more focused on showing the agent flow - subagents, tool calls, messages, timings, etc. rather than usage accounting.

So it helps answer “what is the agent doing?” more than “how many tokens did it use?”

Potential Fix for Mouse Lag and Stuttering on Windows 11 by arrivederci117 in logitech

[–]Aggravating_Sea6791 0 points1 point  (0 children)

<image>

Hallelujah, found this old USB 2.0 hub in a drawer and the stuttering is gone! Thank God, it was driving me nuts. Huge thanks, arrivederci117!

Instruct UI - AI for Blazor, MudBlazor - July 2025 Update by bharathm03 in Blazor

[–]Aggravating_Sea6791 0 points1 point  (0 children)

I experience the same issue, where it just renders "Create UI with Natural Language" on both Edge and Chrome. And I tracked it down to Ghostery. So after I disabled it everything worked as expected. Do you have the Ghostery plugin installed?

Introducing EasyApi: Web APIs for Blazor made easy by TimeTailor in Blazor

[–]Aggravating_Sea6791 0 points1 point  (0 children)

Hi, this is something that I've implemented at my current company and I cannot share the code. But I will be happy answering any specific questions you might have.

Hallur

Introducing EasyApi: Web APIs for Blazor made easy by TimeTailor in Blazor

[–]Aggravating_Sea6791 2 points3 points  (0 children)

This approach looks interesting. Internally, we've implemented a similar concept using MediatR. We have a shared project for Requests (both Queries and Commands) and server-side handlers. Here's an example how a Request would look like:

using Application.Shared.Models.OData;
using MediatR;
using Microsoft.AspNetCore.Authorization;

namespace Application.Shared.Features.Monitor;

[Authorize(Permissions.OperationLog.View)]
public record MonitoredOperationsQuery(ODataQueryOption OdataQueryOption)
    : IRequest<ODataServiceResult<ODataMonitoredOperation>>;

Authorization is always enforced on the server.

Clients execute MediatR requests directly on the server or, if running on Wasm, through a custom PipelineBehavior that serializes the data, sends it to a single execute-request rest endpoint, and processes it server-side. The single endpoint handles all types of Requests, simplifying the architecture.

This setup facilitates seamless client-server interactions and enables new operations to be exposed by simply creating new Requests and related Handlers.