biwills

Do we know the code behind these vulnerabilities were written by AI? It seems like if anything AI was used to find exisitng vulnerabilities that would otherwise be used/sold as zero days and go unreported.

It was always the case that finding vulnerabilities in software was easier than writting perfect software. I'm hopeful that we can use AI to make software more secure over time. Project Zero [1] and others has shown many times the past few years (pre LLMs) that automated fuzzing and other forms of dynamic analysis are very effective, which bodes well for automated testing via LLMs!

I agree that more code = more bugs overeall, but there are slow moving codebases that run some of the worlds most valuable software. Seems like using AI to find vulnerabilities in that code is a huge win across the board.

[1]: https://www.google.com/search?q=site%3Aprojectzero.google&q=...

FWIW they have changed the price a few times [1].

The chances that this would survive ICANN's dispute-resolution policy [2] is very low:

> (iii) your domain name has been registered and is being used in bad faith.

I don't think putting up a page asking for $1M would pass the "bad faith" test

1: https://x.com/polycoolintern/status/2090532162067918941 2: https://www.icann.org/resources/pages/policy-2024-02-21-en

> And then there’s the Stack Overflow Developer Survey.

Honest question, at what point is the Stack Overflow Developer Survey not representative of the average software engineer, many (most?) of who no longer use Stack Overflow?

true and I'd love to be able to expand support out for the equivalent versions in linux / windows. For now, you can always fall back to using safeStorage on non macOS platforms!

> What about consensus? Elections? Which server is the primary for a given repository? It also doesn't matter! There's no state and no consensus here. Any server can be the primary. All updates to the write-ahead log are synchronized with an atomic compare-and-swap (CAS) operation on S3, so it's always safe for any instance of a repository to receive a push.

Again reminded of what an amaizing piece of engineering S3 is (99.999999999% - 11 nines of durability) [1]

1: https://docs.aws.amazon.com/AmazonS3/latest/userguide/DataDu...

I disagree, many companies are still great even after going public in the last decade:

Shopify, Cloudflare, Zoom, Spotify, Roblox, and Coinbase are all notable examples.

Please add links on your site to your Terms of Service and Privacy Policy.

The biggest problem I see is that, like static/dynamic typing, it's usually a boil-the-ocean problem. Most languages have historically been static or dynamically typed. Only recently have TypeScript and Python allowed for migration from dynamic to static typing, introducing millions(?) of developers to static types in the process.

With errors, it's hard since many languages can throw errors anywhere, so it's hard to feel like any function is "safe" in terms of error handling. That's one of the reasons why `enwrap` returns a generic error alongside any other result: to support incremental adoption.

If you have a chance to check out `enwrap` and have feedback, email me! (link in bio)

The more I write software, the more I think errors should be first-class citizens (camp #2 from the OP's post).

I've been using https://github.com/biw/enwrap (disclaimer: I wrote it) in TypeScript and have found that the overhead it adds is well worth the safety it adds when handling and returning errors to users.

That said, I see parallels between the debate about typed vs. non-typed errors and the debate of static typing vs. dynamic typing in programming languages.

Kitty (https://sw.kovidgoyal.net/kitty) has been my go to for many years and with tmux it's fantastic.

I have heard a lot of great things about https://ghostty.org/ but haven't had a chance to check it out

edit: oops, I misread your question as "what alternatives are there"

I'd say it's less about covering all edge cases and more about showing that text editors are insanely complex, and it doesn't take long to find edge cases that text editors with 10s/100s of millions of users have.

This reminds me of Marijn Haverbeke's, the author of CodeMirror and Prosemirror, blog post about making the first version of CodeMirror

https://codemirror.net/1/story.html

From the description of the repo on GitHub:

> I created this in 2014, the year I learned how to program. All of the downloads are from an old version of https://github.com/micromatch/micromatch.

Yes, but we have more details on our cloud offering coming soon

Hey HN,

Excited to share Mobile Tethering, our latest feature release on Faraday.dev. It lets you run local LLMs on your Mac/Windows Computer (Linux soon) and seamlessly use them to chat with AI on mobile. Since all the heavy workloads run directly on your computer (instead of on an expensive cloud server), it's 100% free to use, and your chat data is never stored or logged in the cloud.

I'm one of the founders of Faraday.dev, so would love to hear any ideas you have on what we should build next!

__

PS: For those who've never used Faraday – it's a zero-config desktop app for creating AI characters (custom chatbots) powered by locally running LLMs. Faraday can run on CPU with only 8GB of RAM via llama.cpp by @ggerganov, and the app will automatically use your GPU to speed things up. We also have a community-driven Character Hub, text-to-speech, lorebooks, and more.

Yes. Here's a quick rundown of grammar in llama.cpp (link on the docs of faraday.dev which runs llama.cpp under the hood)

https://docs.faraday.dev/character-creation/grammars

We are doing this with https://Faraday.dev - would love to chat more - my email is on my profile!

we've been looking at at a lot of custom models for https://faraday.dev (shameless plug)

There's already some interesting fine tuned llama2 models:

- https://huggingface.co/NousResearch/Redmond-Puffin-13B - https://huggingface.co/Tap-M/Luna-AI-Llama2-Uncensored