Hacker Newsnew | past | comments | ask | show | jobs | submit | akrauss's commentslogin

Adtech cookie banner on a .org domain for a thing whose name starts with „Open“? No thanks. Won‘t look further.


Your loss then. Although I prefer KDEnlive, OpenShot is not a bad video editor.

And I don't think it's a terrible thing for an open source developer to try to earn a few coins.


Its name starts with Open because it's open-source / free software (GNU GPLv3).


FWIW you can just install it from your distro's software repos or as a flatpak[1] and never ever visit the official website.

[1] https://flathub.org/en/apps/org.openshot.OpenShot


Easy to say. What did you accomplish for FOSS?


Oh come on, they only have 210 "partners" they give your data to!


You jest, but with even trivial sites having 900+ so-called partners, "only" does indeed seem apt.


I know, but we're talking about some free & open-source software funded by donations, not a for-profit company.

Funnily enough their not (fully) free and not open source competitor DaVinci Resolve doesn't have a cookie banner and doesn't set any cookies on your browser.


I feel like the only way to have this many "partners" as is to inherit them, at least if you're 'trivial'. Like, they probably chose some ad or tracking script that has so many partners.


Typical FOSS hypocrite.

Mad that “free” software has to be paid by someone.


Why is the Hono Websocket table non-monotonic in tokens vs costs?


Looking forward to some article/video


Does emdash also help making the setup secure by isolating the agent from my local environment? This is more than just git worktrees.

Or do you consider this orthogonal to what emdash attempts to do?


No Datepicker?


As pointed out in another comment, it's under the form elements, not listed as a top-level component as many UI libraries do

https://oat.ink/components/#form

Which actually makes sense: Oat's driving philosophy seems to be to use and enhance native controls as much as possible, and the date picker is already a native type on the input element.


But there's no enhancement here. That's just the native date picker control with a bit of styling on the textbox portion of it.


Thanks, I missed that when looking through the component list on the top level.


I'm not a web dev, but doesn't HTML come with a date picker?


HTML also comes with a button and an accordion.


I would like to see the following published:

- All prompts used

- The structure of the agent team (which agents / which roles)

- Any other material that went into the process

This would be a good source for learning, even though I'm not ready to spend 20k$ just for replicating the experiment.


Yes unfortunately these days most are satisfied with just the sausage and no details about how it was made.


Just claims with nothing to back it. Steal people's work of years, and turn around be like I make it "so much better". Support this compiler for 20 years then


What I missed when trying it was a simple way of accessing private repositories. There does not seem to be ssh agent forwarding, or is there? What do people use?

I realize this is all very fresh, but still wondering…


Did you ever find an answer? Other than copy/pasting my priv/pub keys into ~/.ssh/ I'm not sure.


> Sprites are active when: * They're servicing an incoming HTTP request. * You're interacting with a console.

They are advocated as Linux machines. How about daemons then, or cron jobs? What semantics can we expect from them?


This is a good concise summary, regardless of provenance.


It is really important that such posts exist. There is the risk that we only hear about the wild successes and never the failures. But from the failures we learn much more.

One difference between this story and the various success stories is that the latter all had comprehensive test suites as part of the source material that agents could use to gain feedback without human intervention. This doesn’t seem to exist in this case, which may simply be the deal breaker.


>> This doesn’t seem to exist in this case, which may simply be the deal breaker.

Perhaps, but perhaps not. The reason tests are valuable in these scenarios is they are actually a kind of system spec. LLMs can look at them to figure out how a system should (and should not) behave, and use that to guide the implementation.

I don’t see why regular specs (e.g. markdown files) could not serve the same purpose. Of course, most GitHub projects don’t include such files, but maybe that will change as time goes on.


> I don’t see why regular specs (e.g. markdown files) could not serve the same purpose.

I think because they're doomed to become outdated without something actually enforcing the spec.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: