ewidar

could be, I guess we'll see.

but even that, if done correctly, is quite impressive. It sure sounds very useful given the number of papers out there.

Not a hit piece on AC, rather about how non coordinated a thorough policy change can have adversarial effect.

Also, yes AC is essential, but it is on track to consuming so much electricity that is has to be pushed in the right direction to not become a new problem replacing the old.

In startups with less than 50 people (and I am being generous on the number), everyone talks to everyone all the time, so there is no need for these moments to extract key info to fix/improve situations, identify topics to push, ...

But once the company is just large enough, there is no way you're going to interact with everyone in a meaningful manner (n^2 relationships and all that), and the simplest solution is intermediaries and 1-1s.

[also, being sarcastic is unhelpful.]

Seeing the same on our side, and now no github action is even getting picked up in our repo.

To me this rule is not necessarily something each individual must do on their own, but rather an objective for systems and societies.

In this frame the outcome is more: Companies providing chatbots should not encourage anthropomorphism by giving cute names, making them witty, using human like pictures, ...

It's not about the cyclists wearing ANC headsets (which is already prohibited at least in Euro countries), but about pedestrians wearing them. Another problem altogether.

I think you should just explain that part more clearly: why would they want you to host git repos on their behalf.

What these 'channels' do is essentially why I was running a nanoclaw at work: triggering a claude code based on events and getting feedback/review/analysis which nicely closes the loop with other agents.

Not sure why it has to be an mcp, but will be trying this out asap.

One thing that I currently find useful on MCPs is granular access control.

Not all services provide good token definition or access control, and often have API Key + CLI combo which can be quite dangerous in some cases.

With an MCP even these bad interfaces can be fixed up on my side.

Do you have a good starting point or explanation to share about using obsidian for a team, where we all change/sync files?