duckerduck

The "load bearing" term has become a bit of a meme, given the author is familiar with these AI-isms, we can assume it's a subtle joke.

That is very region specific, in the Netherlands it's quite easy to operate a non-profit

When was this? I signed up recently and don't remember this requirement.

As mentioned elsewhere, the benchmark introduces bad pelicans in the training set. What I'm curious about however, if it's possible for a human artist to "poison" the benchmark by releasing some really good pelicans svgs and have all future models output their version.

Nice I am designing/building a pen plotter myself at the moment and was surprised by the lack of good software. Will give this a try!

Makes me wonder if we'll ever see a video game where the world is created by set designers irl.

They kind of already have a central point with 'ssh exe.dev', which hosts the interface for provisioning new VMs. But yeah, still one extra step for the user.

When I was very young I installed OpenSUSE on my underpowered windows PC, it was really a hacker man experience that is engraved in my mind as a core memory. As a child I just thought it was cool to have a new and faster desktop, but as I've grown older I've stayed with Linux for its ideas and principles. Hopefully these laws can be overturned...

Maybe the EU can open a book portal for the US.

https://pen.org/report/the-normalization-of-book-banning/

I got the Go60 recently from the same company, been really enjoying (re-)learning how to type on it. It does take some time tho.

We do this, can confirm its very nice

Now its 43 :'(

I'm building a Typeform/Google Forms alternative that integrates into existing applications and stores data in your own database. It allows you to define forms in JSON Schema or JSON Forms. Forms can be added or removed dynamically, and submissions are sent to your backend and in turn stored in your database.

Built using our full-stack library toolkit Fragno [0].

[0]: https://fragno.dev/

I'm building a Typeform/Google Forms alternative that integrates into existing applications and stores data in your own database. It allows you to define forms in JSON Schema or JSON Forms. Forms can be added or removed dynamically, and submissions are sent to your backend and in turn stored in your database.

Built using our full-stack library toolkit Fragno [0].

[0]: https://fragno.dev/

What are you using it for?

Congrats on getting to beta!

I very much relate to the problems you're trying to solve, so much so that I have created a Stripe integration library [0] that has very similar DX to flowgrad! (not nearly as feature rich however). I've also written a blog post as to why I built it[1].

Key difference is where the final billing information is stored, our library also ships db schemas and the webhook handlers write to that local db.

You should also check out our (open source, MIT) library[1] this is built on, it could be useful for you guys!

[0]: https://fragno.dev/docs/stripe/quickstart

[1]: https://fragno.dev/blog/split-brain-stripe

[2]: https://fragno.dev/docs/fragno

I've compiled the "pelicans riding bicyles" benchmark into a single page[0], it only spans a year and not every model is exactly comparable but you can see clear differences between 1 year ago and today.

[0]: https://janschutte.com/pelican-simon.html

They stopped using Cloudflare some time ago

https://news.ycombinator.com/item?id=18188832

From what I've been told by former ASML employees, ASML is not particularly worried about startups inventing a better method than their current lithography process because they basically run the entire chip production pipeline. Improving only one step of this pipeline is not enough to break their moat.

I’m working on “Stripe Integration as a Library.” It seems that whenever someone uses Stripe, for example for subscriptions, they go through the same few steps: creating a database table, setting up webhooks, and implementing the events they care about. The challenge of course is that everyone uses a different stack.

I’m building this using our framework for stack-agnostic JS/TS libraries. On the database side, we currently support Drizzle and Kysely, with Prisma support coming soon.

https://fragno.dev/docs/our-fragments/stripe/quickstart

Inspired by the Stripe integration built for better-auth.

Wow, thanks for sharing, that really takes me back. I was so hyped when I saw this as a kid, my dad and I made a mount for my glasses with two IR LEDs and a battery. I remember that I was super impressed with the effect.

I am a fan of Logseq [0] as well, although it’s slightly different in that it is mostly for bulleted notes and not long-form prose.

[0]: https://logseq.com/

I've created a custom "new tab" page that I have been enjoying. 95% vibes. I wrote about it here:

https://janschutte.com/posts/program-for-one.html

We've got a simple AI chat fragment in our repo: https://github.com/rejot-dev/fragno/tree/main/packages/chatn...

I just found out today that the Dutch teletext can be viewed through ssh:

`ssh teletekst.nl`

I think semcheck has a different use-case. AI is inherently imprecise, if you need formal mathematical verification, AI isn't suitable for that. What semcheck does give you is a very simple way to start verifying specifications, and it's best used in combination with AI-assisted development workflows where you're already spending a lot of time writing specifications (i.e. prompts).

I'm working on a development tool for specification-driven development. It uses LLMs to verify that your specification files and implementation do not drift. More specifically, I am trying to lower the number of false positives I'm currently seeing. I find that the LLM will hallucinate issues when there are no discrepancies, or become forgetful in the case of long documents (like RFC texts). The first step in improving this is to expand my evaluation suite so I can reliably measure improvements.

https://github.com/rejot-dev/semcheck/

It seems that many in the field are converging to similar ideas. With AI the emphasis seems to be more on defining clearly what to build rather than how. I made a similar experiment [1] recently where I setup "rules" between code and spec and have the LLM check that they are the same, I think similar to how Kiro uses hooks.

[1]: https://news.ycombinator.com/item?id=44432215