skysight-inc/HackerNews huggingface dataset:
They didn't do a good job of "gathering" then. Real AI researchers don't have time to keep reading blogs. They should have announced it first and foremost on arXiv or inside the GPT API documentation if they wanted real researchers.
A friend of mine is building Zep (https://www.getzep.com/), which seems to offer a lot of the Assistant + Retrieval functionality in a self-hostable and model-agnostic way. That type of project may the way around lock-in.
That will put a dent in it for sure. But still I feel like fine tuning is the most resilient aspect of it for open models.
We need some independent benchmarks (LLM elo via chatbot arena etc) about how gpt4 Turbo compares to gpt4.
And just like amazon they will compete with their own customers. They are miles ahead in this regard as well since they basically take everyone’s digital property and resell it.
For sure, I didn't mean to imply OpenAI's time-to-market was the main reason for my singularity comment.

Say what you want about OpenAI, and trust me I think there's a lot of material there, but you can't say they don't ship. Nobody else is even close.
The headline typo is either ironic or fitting.
Still, safeguards are quite a lot less safe than if statements. We live in interesting times.

I don’t think there’s any way to guarantee safety from prompt injection. The most you can do is make a probabilistic argument. Which is fine; there are plenty of those, and we rely on them in the sciences. But it’ll be difficult to quantify.

CS majors will find it pretty alien. The blockchain was one of the few probabilistic arguments we use, and it’s precisely quantifiable. This one will probably be empirical rather than theoretical.
Aha, makes sense, thanks :)
> Make them fire you. Don't start smearing shit on the walls or watching porn during meetings, just do the job so poorly that keeping you there is an expensive headache.

what is the point exactly in doing job poorly and make them fire you>,,
> 128k context? Absolutely insane

128k context is great and all, but how effective are the middle 100,000 tokens? LLMs are known to struggle with remembering stuff that isn't at the start or end of the input. Known as the Lost Middle

https://arxiv.org/abs/2307.03172
Agreed on most points, but

> So if a USB-C cable is advertising "20Gbps", you want them to be talking about x1, because that means it's a better cable.

is not what the USB-IF recommends – to them, a 20 Gbps cable is one capable of 2x2.
AMZN makes Dollar General look like Nordstrom’s. Might as well shop at Temu because the price is right there.
Bunnie wrote this well by putting the important part right up front: "The request is facially misguided; any restrictions would only serve to reduce American participation in an important emerging technology".

This is a problem the USA experienced (and was widely discussed) during the cold war. It's so discouraging to see this self-destructive approach being revived.
> I will occasionally look at my history

It's others history that I'm usually interested in. I can easy follow the small diffs of individual commits, but have a much harder time grokking a wall of red and green.
>it should be able to do that job just fine even if you keep throwing lots of packets at it, right?

there's circumvention techniques that abuse the fact that they can't: https://upb-syssec.github.io/blog/2023/record-fragmentation

the intentionally terrible speeds are decided by software heuristics, so antisocial limits are fought with antisocial techniques, with continued brutality being enough to skip the slow deep packet inspection path via force
Somewhere in Settings, Android lets you set a default timeout for how long DND mode stays enabled.

If you want to mess with just ringtone volume, should be doable via Tasker or maybe even the built in Routines
So... none of that is correct. "Inflation" is a growth exponent, not an absolute measure of prices. No one ever promised "prices would come down", because that would be deflation (a negative exponent).

Inflation is just a rescaling. Everyone loves to say it's not, but it is. Prices are higher and wages are higher and assets values are higher. It all happens together, though not in perfect lockstep.

If people wanted to complain about real (where "real" means "inflation-corrected") wages falling, they would be screaming about it, because that would be terrible. Except that real wages are INCREASING and have been pretty steadily all through the inflation burst.
Apparently DuckDB requires your real-life name to file an online bug report, bucking every norm of online handles for communication, as well as enabling doxxers and stalkers to find and trace people in real life.
Well, they tried to put a government sponsored moat in the way of other people building AI companies that would be competing with them. Thankfully, they mostly seem to have whiffed the ball on that one. This plan of theirs to monetize the creation of agents and other tools that take advantage of their underlying infrastructure is a good secondary kind of moat. Because, if your tool relies on their underlying infrastructure, even if you could build something different, the infrastructure is required. This may be a "less-evil" way to keep them building things and making tools available without completely locking out competition.
Text to Speech is exciting to me, though it's of course not particularly novel. I've been creating "audiobooks" for personal use for books that don't have a professional version, and despite high costs and meh quality have been using AWS.

Has anybody tried this new TTS speech for longer works and/or things like books? Would love to hear what people think about quality
Previously: https://news.ycombinator.com/item?id=3947903

(I feel incredibly old right now.)

Edited to add: Finally found the full form letter [1]. (I filed a copy back then and it still shows up languishing in Feedback Assistant even now!)

[1]: https://gist.github.com/mysteriouspants/1989061
In general I agree with you, there are absolutely times where you want to retain commit history on a particular branch (although I try to keep the source tree from knowing about things like commit IDs).

I would argue that those are by far the minority of PRs that I see. As I mentioned in another comment, _most_ PRs that I see have a ton of intermediary commits that are only useful for that branch/PR/review process (fixing tests, whitespace, etc). Generally the advice I give teams is, "squash by default" and then figure out where the exceptions to that rule are. That's mainly because, in my opinion, the downsides of a noisy commit graph filled with "addressing review comments" (or whatever) commits are a much bigger/frequent issue than the benefits you talk about. It really depends on the team.
Some of that work does benefit me: better understanding of the bug, verification that it’s not something I’m doing wrong, maybe some ideas of a workaround.

I’ve stopped doing the second phase: packaging it up and submitting it to apple, because that’s shown itself to be an entirely negative experience.

If apple’s not going to spend the $$ on internal QA, and they’re not going to spend the $$ on developer relations, I’m not especially interested in donating my time to help them. I know I’ve seen a similar sentiment from other developers for years.

I think low quality / low content bug reports are usually worse than none, because they decrease the signal to noise ratio of bugs. Maybe if there was a better channel of communication, and I knew it’d be more interactive it’d be different.
It's true that it doesn't eliminate all bugs in general, but it can completely eliminate buffer overflows for example.

There is no excuse to not at least have bounds checking. This is one of the most basic memory safety problems and it's trivial to prevent.

Just preventing this small issue will prevent a non-trivial fraction of bugs. I don't have sudo's bug list on hand but I wouldn't be surprised if 25% or more are caused by buffer overflows.

So even if it doesn't prevent all logic bugs, it cuts out a pretty big chunk of the bug list.

>assuming you don't switch them off

You can't switch them off.

>Rust community's tendency to pitch this stuff as a security panacea

I've not seen anyone claim this so far.
Do you also get those hallucinations just on silence?

I kind of wonder if they had a bunch of training data of video with transcripts, but some of the video/audio was truncated and the transcript still said the last speech, and so now it thinks silence is just another way of signing off from a TV program.

IMHO the bottleneck on voice now is all the infrastructure around it. How do you detect speech starting and stopping? How do you play sound/speech while also being ready for the user to speak? This stuff is necessary, but everything kind of works poorly, and you really need hardware/software integration.
https://www.youtube.com/live/U9mJuUkhUzk?t=2006

(Timestamp 33:26)

Edit: updated the timestamp
>The elite at Sun Microsystems largely did all three out of necessity

Some of it quite poorly, which is why Sun lost to Linux and other hardware companies, and why basically no one used Joyent.

>And that's who runs Oxide.

It's basically "rewrite it in Rust" Sun Microsystems. Best of luck, but I don't see them being anything besides a niche player with some interesting tech that doesn't beat the competition enough to matter.
speech to text is a relatively crowded area with a lot of other companies in the space. Also really hard to get "wow" performance as it's either correct (like most other people's models) or it's wrong
IMO the relevant 'true history' is at the plane of 'things relevant to other developers'. As far as anyone is concerned, my local work history is that I atomically wrote all my code in a single instant. Commits are that unit of atomicity.

But I have never seen a commit disappear while rebasing, ever. That workflow is busted somehow. They were doing it wrong.
Everyone’s got a loss leader
same here. I wonder why they are not opening it up to more devs. Seems strange.
> Issue 3 requires me to build my own time observer which is further technical debt, versus being able to rely on Apple's API.

IMHO, it's the same amount of technical debt, regardless of who built it. In this case, the overall situation is worse: because you didn't build it, you can't fix it. If you have a dependency built by a benevolent provider, that may mean less work for you in the future, but it's still technical debt.
Yep I feel like they solved the problem that Apple never managed to solve with Siri: How to interface it with apps. Seems like this was an LLM-hard problem
> How do I write monospace on HN?

Line that start with four spaces

like this
Related ongoing threads:

GPTs: Custom versions of ChatGPT - https://news.ycombinator.com/item?id=38166431

OpenAI releases Whisper v3, new generation open source ASR model - https://news.ycombinator.com/item?id=38166965

OpenAI DevDay, Opening Keynote Livestream [video] - https://news.ycombinator.com/item?id=38165090
This city looks awful in this photo but this is probably ideal living for urbanized people.

This was built as a public trans city so the narrow streets are for buses and trams. The apartment complexes aren't big blocky buildings like in say Manhattan, but L shaped to allow a large shady green area and to maximize natural light for all residents. Its full of green between the buildings and quite charming looking and walkable, especially considering some of those buildings are mixed use and allow for business as well:

https://imgur.com/sxgFLjO

https://www.shutterstock.com/image-photo/magnitogorsk-russia...

The Soviets got so much right, its such a shame the car-centric suburban sprawl model won out in the West and percolated its way to Russia and parts of the East after the fall of the SU.
I now haven't used Mercurial in about 8-10 years or so. However, I recall enjoying the workflow a bit more, and I did like how commits were explicitly linked to branches as opposed to branches being effectively pointers to commits - it was nice to find out the original branch of any given commit.

However the killer feature of Git is the ecosystem. I was always having to do lots of custom work to get Mercurial to work with CI providers, whereas Git just worked and had first class support. It was clear after a while that our team would always be outsiders if we continued down that path, and there wasn't enough of a compelling reason to stay with Mercurial.
I get rizzed by my SO whenever I update software. There's a "have fun when it breaks," aspect that she gets to relish a little bit in when it does!
Related ongoing thread:

New models and developer products - https://news.ycombinator.com/item?id=38166420
It wasn't in the clear, you did that.
Most of the API docs were updated, but none of the new APIs work for me. Are other people experiencing the same?
Vaping doesn't create tar, which was mentioned in there. It was quite boring and I only skimmed it.
$ is what I would expect and prefer, because it’s what I’ve been using in my browser dev tools for over fifteen years (ah, Firebug; fond reminiscences). If your document doesn’t use the names, you’ll get implementations roughly equivalent to these:

function $(selector, element = document) {
return element.querySelector(selector);
}

function $$(selector, element = document) {
return Array.from(element.querySelectorAll(selector));
}

Reference on more magic available in the console (there’s a lot of good stuff):

• https://firefox-source-docs.mozilla.org/devtools-user/web_co... (I think “:help” is my new favourite: opens that URL, which is not particularly discoverable)

• https://developer.chrome.com/docs/devtools/console/utilities...
Note, ElevenLabs is $0.24 per 1K characters while OpenAI TTS is $0.03 per 1K characters. That's a pretty big difference. Elevenlabs still has voice copying but for many use-cases it's no longer competitive.
Agreed, the moat are the models (as an extension of the instruction tuning data)
My issue was that my 2019 iMac got updates that made the whole thing practically unusable. The storage became so slow that it would take like 10ish minutes to become usable after boot. I did have the version with a hdd instead of ssd, but it was fine right when I purchased it. I ran whatever storage tests that would show the drive wasn't dead/dying, so I was never sure what the issue was.

My options were essentially to either trade it back to Apple for $300, try to sell it myself for maybe $400 and pay a ton to ship it, or try to take it apart myself to swap out the hard drive for an ssd and risk breaking part of it and it being worth $0. I caved and traded it in to Apple just so I could stop looking at the box.
If they could roll back the extreme rate-limiting on dalle 3 in gpt4, that would be great.
I don't know why you're replying to my comment, because I wasn't talking about any of those other issues you've said here. I did not confirm or deny them.

I quoted the single issue that I was disputing. I wrote as clearly as possible to only refute one point, about the implication that Bitcoin had never done a roll back.

If you want to talk about all those other things, then make a separate thread or post,. Please don't use my comment as a vehicle for your arguments, because it's confusing and few people will understand what you're talking about.
Getting to Yes: The Unpredictable Path of Startup Customer Acquisition
Search "waste to energy Sweden". It's not perfect, but they have emissions standards and they do filtration.

It's probably significantly better than pretending to recycle the stuff and then burning fuel to ship it somewhere else.
> Doesn't this require that pushed code is perfect?

We aren’t talking about pushed code. We are talking about cleaning up the local commit history before pushing it into a shared branch.
World’s Largest Biometric Digital ID System Suffers Biggest Ever Data Breach
Location: Ottawa, Ontario

Remote: Yes! Prefer remote or hybrid roles.

Willing to relocate: No

Technologies: 4 years of experience working with React, Node, JavaScript, TypeScript, Python, PostgreSQL, bash, Docker, AWS (main focus on IAM, RDS, EC2, S3). Enjoy working on the full stack and having opportunities to learn new technologies.

Résumé/CV: https://docs.google.com/document/d/1yZRyvV-kjn206cSFjX70VHri...

Email: jaharnum@gmail.com
> Any trick for Android to set a temporary mute? 1-2 hours.

Moto phone have actions in built where if one puts phone upside down and phone goes on silent
> (How do I write monospace on HN?)

Two-space indentation.
Turning an airline receipt pdf into a well structured function call is very nice.
> If you look at manufacturing consent, they make it clear that good stuff can get through media.

Arguably, the manufacturing only works if 51% or more is generally good stuff. Obviously propaganda outlets don't keep a lot of eyes, e.g. Fox News' viewership has been declining faster than demographics says it should be.

90% can be spot on, entertaining, and wholly or mostly truthful; it's the 10% makes it work.
Siblings, as in comments at the same level in the comment tree. A bunch of other people have responded to the original comment starting with:

> I don't know anyone who uses Debian and actually sticks with their packaged apps.

With various indications that they more or less actually do stick to the packaged apps.
That feels like a consolation prize more than anything. Epic still isn't a position where they want to put Fortnite back on iOS in any capacity, which I think tells you exactly how they feel about the outcome of the trial.
Yeah, but there's no product. There's no RISC-V CPU targetted at laptop or datacenter users that Intel would be worried about, but there absolutely are from ARM vendors.

So... how would hurting RISC-V, which helps ARM, be good for Intel? It's not. Pick a different boogeyman basically, Intel isn't the one here.
> App developers seem to stick with apple regardless of what they are being subjected to.

Because the alternatives aren’t preferable. The indies who have been exclusively using and developing for Apple platforms for years know that Windows and Linux aren’t better¹, just a different set of annoying trade offs. Apple platforms aren’t perfect, but they are the least bad option in that context. They also used to be better in many regards, which makes the situation frustrating due to the wasted potential.

¹ At a personal preference level. There’s no judgement either way, you do you and use whatever you like best.
I dont have that experience at all, and im a tesla owner. I see more negative tesla stuff than positive, especially about stock value and cybertruck quality problems.
The icon for the game explainer one is a die with two 5s on it. I wonder if they use ChatGPT to write their blog articles as well...
In my day job I work on a product that has FPGAs, and we don't do a single matrix multiplication.

We use them primarily for performant interface with obscure bus protocols, where high performance variously means high throughput (tens of Gbps) with zero acceptable loss, or low latency (interpret the bus protocol and produce the correct response in <10ns), but amusingly for our particular application, not usually both at the same time.

Our volume is too low and the set of bus protocols we need to interact with changes too rapidly for ASICs to be economical. And it's not possible to meet our performance targets with off the shelf SoCs alone or discrete logic gates.

Although I agree with your point that its hard to beat CPUs (and GPUs) when your needs are primarily computation.
Not saying it's not useful, but you can achieve the same result consistently with just a few extra tokens in the prompt.
Yes, but now it's mixed with the bathwater, and now morph into another metaphor as it become the needle in the haystack.

It's okay to have 'low information' commits one can easily ignore in your history, as long as the 'high information' ones stay readable and coherent.
Fully agree. I work in security and sent Apple a bypass for child restriction policies on iOS, they told me to send it to feedback.

Testing, reproducing, writing it up all takes time and effort. I didn’t want anything from them other than for it to be fixed, I have kids with iPhones.

It’s no different than other companies though, I sent a remote code execution to Cisco and they just replied that they already knew about it but the product was approaching end of life so they wouldn’t fix it.

I’ve stumbled across so many vulnerabilities over the years and I tend to just ignore them unless I’m being paid to find them. It’s not worth the frustration.
What about Oracle and MSSQL? I'd imagine that especially the former would be "military-grade" (whatever that entails)
Thanks! Very informative! It's really a fascinating topic.
Poe has done a great job in this space, quite a large marketplace of existing bots. I'm excited to see what it can do with the extra vision, D•ALLE, and Code Interpreter models.
I've been wondering this as well. I'm super glad, but it seems so different than every other thing they do. There's definitely commercial value, so I find it surprising.
Well I also object to multiple unrelated changes in the same commit. Those should be separate commits, and separate code reviews for that matter.
To my understanding severability clauses deal with legal findings of unenforcibility. And there are usually similar clauses that allow for a voluntary non-exercising of contractual rights to not void the contract (e.g. your landlord doesn’t collect December’s rent as a gift doesn’t mean you don’t still have to keep paying rent in general). I’m not aware of any standard contractual clauses that allow one to just voluntarily fail to perform their obligations and not also void the contract as a whole (barring provisions for repair of breach, but that’s not just unilaterally deciding you’re not going to do your contractual obligations)
TIL, thank you! Now I know for a fact that squash-mergers have no excuse and can brandish the man page at them.
Apple's solution for missing Catalyst functionality has been to create analogous features or port existing API to iPad.

That said - the long-term strategy doesn't appear to be Catalyst, but Swift UI.
It’s probably not worth the hassle and the risks. Also an idling server consumes a lot less power than a busy one, so it’s not that bad.
No one is mentioning:

$ git log --merges

Now you can see your features in a nice history and also have added benefit of seeing intermediary commits. Pro tip: merge commits aren't required to use the canned "Merge branch into..." message, you can give it any message you want, such as "feat: ..." or whatever your convention is.

I hate that branch squashing has become something of a defacto. I actually do rewrite my history and often add context to my commits. `git blame` can be an incredibly useful tool to get context about a given small change. Getting a massive diff for a whole feature is much less so, especially since you can just look at the diff of the merge commit.
3.5 Turbo 16k now cheaper than old 4k. 0.003c per 1k in / 0.004c per 1k out.

Fine tuned 16k: 0.003c / 0.004c

Assistants API with RAG and code interpreter (sandboxed jupyter).
I read git commits in either the repo I am working on or a dependency repo almost every day
Pascal, C, Java are used as first languages successfully. Why Rust cannot? It's even easier to use than C and Pascal.

Rust is hard for older programmers because it's hard to FORGET old habits from other languages, which allowed too much.
Precisely, you want to keep it about one commit per feature. I think the parent comment was worried about monster merges that squash many features together.
Incentivize screening Radars (and fixing them). There's no engineering glory in keeping your unscreened count at zero... nobody gets promoted for it.