lemagedurage

Agree.

I do feel like there's merit to having an open source implementation of anything, no matter who/what wrote it. I'm just hoping the results are validated well.

Given that you bring the weights from NVIDIA's DLSS. So basically, the repo contains reverse engineered machinery that produces the exact same output given the same model.

We're not simply changing the seed. The LLM provides some probability to tokens, and the SynthID watermarking makes it slightly more likely to choose some and slightly less likely to choose others within that distribution.

Theoretically, that can be true.

In reality, Gemini and Anthropic use SynthID watermarking which affects token probability distribution, i.e. their tournament sampling can pick lower-probability tokens which the LLM's distribution would otherwise not have. They likely use this over unbiased watermarking because SynthID is resistant against text edits.

That's not true. Watermarks are messing with the next token generation probabilities based on some random seed. The quality is neccesarily lower, the difference is simply too small to notice, typically.

Yep, I'd hypothetically economically gladly build an alternative app store charging "only" 5% on app revenue. The blocker would be that Google has a hold on what store is installed by default on Android. Apple even more so. This is hardly a fair market.

Being pedantic about the captcha is the less-human thing to do here.

Agree, and for me I feel like I often have more implicit intentions than I write in a prompt. A plan helps me verify whether an agent gets these right or not. Plus, it highlights tradeoffs I might've not thought about. Removing both feels like lowering a quality bar.

On the other hand, for a low effort hobby project: just do the thing.

Yeah, Tailwind is great as long as you have some way to reuse markup, like React. You don't have to care about class names and whether CSS defined somewhere else affects styles of a current component at all. That last point makes sense for LLMs as well: all the styles that affect the current file are automatically in context since styling is local. Admittedly, there are other ways to achieve this but the ergonomics of Tailwind are just good. Having nice defaults and good training data is an added bonus.

A challenge of releasing tech on a platform of people that are picky about tech.

Sometimes it feels like we're living in an episode of Silicon Valley, the show.

Well I don't think the position of planets when you're born has a large correlation to how your life will go.

On the other hand, how an AI writes will have a big correlation to whether the written text would likely be written by an AI.

The latter is more of a direct relationship.

Maybe A and B are not correlated, and Y and Z are? What pattern are people falling for here?

I just feel like, from the POV of AI companies, that reducing the amount of em dashes they use to "blend in" more and talk more human-like, for the sake of being less detectable, wouldn't be a big priority.

That just proves that perfect classification is impossible. Classification doesn't need to be 100% accurate to be useful.

The 80% accuracy from the article would be one reason to believe there's significant correlation, no?

Why would sounding human be a goal rather than a byproduct of trying to communicate efficiently?

The problem seems to be deeper rooted. Cursor doesn't see cloning a repo with Cursor and code execution as separate security boundaries.

Cursor ships with Workspace Trust disabled by default [0]. A repo that includes .vscode/tasks.json with "runOn": "folderOpen" will already run arbitrary code [1].

[0] https://cursor.com/docs/agent/security#workspace-trust

[1] https://www.oasis.security/blog/cursor-security-flaw

You're right, looks like they changed it, though Task should still work.

> In version 2.1.63, the Task tool was renamed to Agent. Existing Task(...) references in settings and agent definitions still work as aliases.

https://code.claude.com/docs/en/sub-agents

True. For Claude Code, I disabled explore subagents globally by adding this to ~/.claude/settings.json:

  "permissions": {
    "deny": [
      "Task(Explore)"
    ]
  }

"LGTM"

That'll be $50 — please.

Ehh, AI makes plenty mistakes but they have a different vibe to it.

In my mind an AI would do something the most popular way even when that's not appropriate.

A human might do things in an unpopular way even when that's not appropriate.

Maybe they added the comments to get a longer payload for the sake of the shirt's design.

The comments can be more cute/awe inspiring for people who aren't as familiar with bash but like solving puzzles as well.

I don't think it was written by an LLM, some things stand out:

The congratulations text is both in English and Japanese. Contains a single heart emoji.

There was an intention to have a cyan to orange gradient, but the range starts in an ANSI block, ends halfway through the 256 color block and 256 terminal colors are not arranged like a gradient at all.

There's no sleep at the end of the loop where I feel like an LLM would add that defensively.

Sounds like a convenience feature for a dev that they forgot to remove before distribution, since it's this poorly hidden.

Use cases range from sending 100s of requests per second just to bring a website down to doing a montly request to a municipality's endpoint to get a local dashboard of when trash is picked up. I don't think you can pass a single judgement of automating web requests in general.

If a vulnerability disclosure program has a good track record of paying out, and legitimate reports get refunded, why not?

Again, the alternative might be shutting down the program entirely.

Have you considered requiring a small payment for vulnerability disclosure? Refund it on payout. This should be very effective at deterring spammers. It also sucks for real reports, but beats shutting down the program entirely.

Both sides are not looking too pretty here.

Having their business transparent makes sense but by restricting people's personal lives like this would disincentivize good people from rising to power, which is not what we want.

People connect through cellphones more on weekends, and cellular has higher IPv6 usage.