ahmedehab_01

If you control the company, then you can easily stop this by making the product manager the one who can request a UX change, not the UX team.

If you are an employee, a frontend dev, for example, then you can't change it as much as you want, other than raising it with your superiors; maybe, as an EM, you can have a chat with the director/VP/CTO about it.

Generally, for an employee, it's more work, which is not bad; it means you are safer in your job (if it's Enterprise). Just ask them to use official ways to request a UI change, such as a Linear/Jira ticket.

Reply with AI as well. And make it obvious. Then ask AI for a very brief and concise summary of your communications at the end of every day.

This is bad, but you have to deal with it one way or another that will keep you sane. And you can always communicate with the rest of your colleagues to not feel alone.

For him, it's a new fun toy to play with, and he also thinks that makes him very AI-forward or AI-native or whatever the current corporate jargon is.

He is doing this because he thinks this will net him another promotion, and that's the way forward because big shot CEO are doing. That's how most corporate managers think. It seems they know what they are doing, but they mostly try to blend in as much as possible and be the most "forward-thinking" and "raising the bar" and "leading by example".

It's blazing fast too. Good job. But is it purely text? Or do you support/will support, images and videos?

This actually shows that it was a human error on HuggingFace's end that led to that "breach".

I would say HuggingFace needs to prioritize both security metrics/alerts and metrics/alerts for node count. And not leave long-lived keys accessible easily like this.

It would have been way more groundbreaking if the agent found an actual vulnerability in Tailscale.

It's diabolical how they are allowed to write that you are obliged to get the consent of every person monitored for their AI training purposes.

Could that mean anyone owning a TV like this can be sued?

Good idea to reserve a username early! I will do that too

Anyway, it's not that I don't think GitHub has real issues under Microsoft, but I disagree with the title of the article, as devs are not leaving it in droves, yet.

Extreme generalization, most devs aren't ditching GitHub yet.

Why do all similar products have a hard limit on the 128 GB VRAM part? For that price, I hoped to get at least 224 GB VRAM

Would that lead to anything better for the users, such as a smaller bundle size? Or is it more of a QoL change for Shadcn maintainers?

I don't get why not open source it? You are already open-sourcing your weights!

Glad it's back, but the price outside of the subscription is insane. API pricing is just not for regular users.

Do paying customers distill? Is it fraud to protect against distillers?

Frankly, I don't see this as the concerning behaviour the article describes. It is fine to try to protect against distillation through a technique like this. This will also allow them to, instead of blocking the distillation agents, respond with a poorer result/model, hindering the progress of distillation, momentarily at least.

I would guess that's their first line of defense; they should have more techniques to identify distillation because that's a very simple way of detecting the host and can be easily spoofed.

Good, and should be banned worldwide for elementary school children. Either that or we get a generation of dumbasses with zero critical thinking skills.