skysight-inc/HackerNews huggingface dataset:
I did say my understanding was probably naive; I didn't know the details to be able to assert anything beyond my own observation!
o1-preview and o1-mini. I don't think o1 is publicly available yet.

And I assume voice mode is like Sora; a nice PR play.
>> Russia [...] currently has foreign troops on its land that are attacking it.

> Ukraine is the defender in this conflict. Every reasonable action it takes to encourage a Russian withdrawal is, by definition, defensive.

War is peace etc etc.

I'd like to point out that an attack is the opposite of defense and the scale of the attack does not make it not so. Your argument does not negate the GP statement which btw is true.
Telepathic Datacenters: Fast RPCs Using Shared CXL Memory
And how much data can you give it?

I'm not up to date with these things because I haven't found them useful. But with what you said, and previous limitations in how much data they can retain essentially makes them pretty darn useless for that task.

Great learning tool on common subjects you don't know, such as learning a new programming-language. Also great for inspiration etc. But that's pretty much it?

Don't get me wrong, that is mindblowingly impressive but at the same time, for the tasks in front of me it has just been a distracting toy wasting my time.
Safe C++
if you tap the '-' key on ur keyboard it shows an overlay in red and green with the steps down and up which i've been using as a transposition aid
Oh, I don't mean cases that still hang in the air, but those which are closed-and-shut cases. The 2012 gangrape-murder in Delhi, India, was such a scenario - they found DNA evidence, evidence of gruesome rape with metal rods, a brutal murder and disposal of the body, and eye witness testimony of the boyfriend, and the entire nation in uproar. The death penalty was the only suitable verdict then - in fact, delaying it was a major reason the then-government lost power.

Then again, in India, we also had a rape in 2017, where the same thing happened with a 6 yr old Muslim child, but because the perps were lackeys of the ruling party at the center and the victim Muslim, the case was mostly forgotten within a few weeks. Doesn't help that the media was in the pockets of the ruling party too (still is).

There is an obvious merit to using the death penalty - after all, why should taxpayer money be used to fund the imprisonment of those who have already proven that they're the worst of society?
> 20-30 Lambda functions for different services

Yes. This is the basis of privilege separation and differential rollouts. If you collapse all this down into a single server or even lambda you lose that. Once your service sees load you will want this badly.

> SQS and various background jobs backed by Lambda

Yes. This is the basis of serverless. The failure of one server is no longer a material concern to your operation. Well done you.

> Logs scattered across CloudWatch

Okay. I can't lie. CloudWatch is dogturds. There is no part of the service that is redeemable. I created a DyanmoDB table and created a library which puts log lines collected into "task records" into the table paritioned by lambda name and sorted by record time. Each lambda can configure the logging environment or use default which include a log entry expiration time. Then I created a command line utility which can query and or "tail" this table.

This work took me 3 days. It's paid off 1000x fold since I did it. You do sometimes have to roll your own out here. CloudWatch is strictly about logging cold start times now.

> Could this have been simplified to a single NodeJS container or Python Flask/FastAPI app with Redis for background tasks? Absolutely.

Could this have been simplified into something far more fragile than what is described? Absolutely. Why you'd want this is entirely beyond me.
There are only relative few startups or non startups which need complex infrastructure from a technical point of view...

In reality, there is a strong bias in favor of complex cloud infrastructure:

"We are a modern, native cloud company"

"More people mean (startup/manager/...) is more important"

"Needing an architect for the cloud first CRUD app means higher bills for customers"

"Resume driven development"

"Hype driven development"

... in a real sense, nearly everyone involved benefits from complex cloud infrastructure, where from a technical POV MySQL and PHP/Python/Ruby/Java are the correct choice.

One of the many reasons more senior developers who care for their craft burn out in this field.
Is that a trick question? The Features page is right in the main menu, extremely visible.
In this case, IMO means International Mathematical Olympiad
In my experience, blockchain is introduced not to attract users, but to attract funding or stick price.

I crowdfunded an android tabletop device a while back (Taptop aka Blokparty) and when they pivoted to Blockchain I knew it was over and it was time to start trying to root it to get it on vanilla android.
Learned Helplessness – A Psychological Experiment [video]
Author here - I'm not using pointers in my implementation but indexes as you mentioned.
The bouncing wave was 7m high, and after 3 days only a few centimeters.
LLMs: When the code can be made by an enthusiastic new intern with web-search and copy-paste skills, and no ability to improve under mentorship. :p

Tangentially related, a comic on them: https://existentialcomics.com/comic/557
I upgraded to a Pace ADS200 and it’s dope.
A scientific outpost on Mars is actually feasible, but such an outpost would be funded by grants from the government or private foundations.

It's a self-sufficient colony that's not possible right now or anytime soon. You'd have to spend so much to create an air-tight and heated environment that could generate air, water, and food. How are you going to pay for, especially when anything you can't make yourself has to be rocketed in from Earth? Is there anything on Mars that you could sell back to Earth?
Kubernetes/k3s on a single node turns what could have been immutable 1-step upgrades into multi-step mutable upgrades, since kubernetes's software itself and all the management components you need are a mutable layer on top of the operating system.
All build tools are terrible, and among the available build tools, Sbt is OK.

Let me give you an example … in Gradle, the order in which you specify plugins matters, due to the side effects. Say, if you specify something complex, like Kotlin's multiplatform plugin, in the wrong order with something else, it can break your build definition. I bumped into this right off the gate, with my first Kotlin project.

In Sbt this used to matter as well, but because Sbt has this design of having the build definition as an immutable data structure that's fairly declarative, people worked on solving the problem (via auto-loading), and since then, I've never bumped again into ordering issues.

There are other examples as well, such as consistency. In Sbt there's only one way to specify common settings, and the keys used are consistent. Specifying Java's targeted version, for example, uses the same key, regardless if the project is a plain JVM one, or a multiplatform one.

Sharing settings and code across subprojects is another area where Gradle is a clusterfuck, whereas in Sbt it's pretty straightforward.

Don't get me wrong, Gradle doesn't bother me, and it has some niceties too. Other ecosystems would be lucky to have something like Gradle. But I find it curious to see so many people criticizing it when almost everything else is pretty terrible, with few exceptions.

---

Note that Li Haoyi has great taste, and Mill is looking good, actually. But he also likes reinventing the wheel, and the problem with that for build tools is that standardization has value.

Standardization has so much value for me that I would have liked for Scala to use Gradle as the standard build tool, and for Scala folks to work with Gradle's authors to introduce Scala as an alternative scripting language for it, despite me liking Gradle a lot less. Because it would've made switching and cross-language JVM development easier.
They started new factories in new states to try to break the unions in Seattle.
Yeah it is fair. You don't pay a lawyer for 40s of work expecting to see all the research between your consult and the document. You don't pay a cook for a meal and expect to sit and interrogate all the ingredients and the oven temperature.
There are many successful relationships that don't involve arguments - and which are about constant peace.

I am not saying things about successful relationship. I am merely pointing out how exploitation of users can occur.

Emotional bonding often occur in orderal and other challenging events. It is one of the tools that companies will use to push users' button and to exploit them for economic value.

And if AI girlfriends offer 'ideal relationships', how is that not 'good'?

Ideal relationships aren't necessarily good for AI companies' pocketbook.
Yes, use boring technology, I'm all for that.

But an application built in the high pressure environment of a startup also has the risk of becoming unmanageable, one or two years in. And to the extent you already have familiar tools to manage this complexity, I vote for using them. If you can divide and conquer your application complexity into a few different services, and you are already experienced in an appropriate application framework, that may not be such a bad choice. It helps focus on just one part of the application, and have multiple people work on the separate parts without stepping on each other.

I personally don't think that should include k8s. But ECS/Fargate with a simple build pipeline, all for that. "Complex" is the operative word in the article's title.
How did it get flagged?

I don't have the option to down vote, per say
The classic HN catnip blog post:

1. New technology is bad and has no merit other than for resume.

2. Use old technology that I am comfortable with.

3. Insist that everyone should use old technology.
Simple is robust.

Focus on product market fit (PMF) and keep things as straightforward as possible.

Create a monolith, duplicate code, use a single RDBMS, adopt proven tech instead of the “hot new framework”, etc.

The more simple the code, the easier it is to migrate/scale later on.

Unnecessary complexity is the epitome of solving a problem that doesn’t exist.
Tyler Cowen: OpenAI o1 and Economics [video]
Hot tweezers is a fun idea we've been talking about. How would you like to see it implemented?

Yes, we really love the cap. It instantly safes the iron when you're done.

We'll post more documentation on the serial interface, it's pretty straightforward. A temperature control program would be no problem.
It was 100% covid.

The strip clubs were closed, the strippers and the patrons moved to the online strip club.
> having no way to assess if what it conjures up from its weights is factual or not.

This comment makes no sense in the context of what an LLM is. To even say such a thing demonstates a lack of understandting of the domain. What we are doing here is TEXT COMPLETION, no one EVER said anything about being accurate and "true". We are building models that can complete text, what did you think an LLM was, a "truth machine"?
But it's never just ECS/Fargate is it. It's ECR, S3, ALB, CF etc.

And at that point you've assembled a stack just as complex as doing it all inside a single k8s cluster.
Is anyone willing to admit they subscribe to an OF and explain why over the free pornography alternatives that most of the internet is full of?
It's not CPU-bound either. I made snappy GUIs in Python twenty years ago.
Perfectly well put! We should change the name from "AI" (which it is not) to something like, "lossy compressed databases".
This is so cool to see. As a health care worker I see lots of people who simply can not afford heating aids as they run for thousands of dollars and then things like they hop into a shower and they stop working happen all the time.

What a lot of people don’t realize is that hearing loss is a loss of ability to hear certain frequencies. You can’t simply turn up the volume although that does help to some degree. So what happens is you see a doctor who determines what frequency loss you have and the hearing aid when it picks up that frequency shifts it to another frequency that you can hear. So I do see why up until now ya it was regulated. We don’t want some company selling a device that simply cranks the volume and potentially causes more damage. But with today’s technology we are more then ready for this to be a reality. With an app we can offer hearing tests and determine what areas the client needs improved. This I feel will be a game changer for some.

The only thing I wonder about is how well do air pods hold up to waxy ears? With regular hearing aids they need cleaning and often have things like a wax trap which is a tiny plug that catches wax and can be swapped out easily.
Everyone Can Write Tech Blogs
I think we can just let this rest. These kinds of operations are not as ergonomic in python. That's pretty clear. No example provided is even remotely close to the simplicity of the F# example. Acquiesce.
If you've submitted a 510k for your medical device, you can advertise it as "510k pending".

There is a risk that you never receive the clearance or approval, but in this case Apple probably knew they had already addressed any feedback the FDA had so it was very likely there would be no further stumbling blocks
After reading all the comments here, the conclusion is to start simple, then switch to k8s and later to cloud-native only when your business has grown to 1000 and then 1 million daily customers respectively.
Don't know about all the countries, but since you're answering a comment on Russia, I must say, it reads comically out of touch.

Yeah, the old system was purged alright, but calling it a liberation is disrespectful to the lives of millions of common Soviet people driven to hungry death, being forcefully moved around the country, killed in internal squabbles or purges or otherwise "collectivised".

And it all happened despite the fact they hadn't exactly been property for more than 50 years by the time tsarism was overthrown.
It's called terminology. Every field has words that mean very different things from the layman's definition. It's nothing to get upset about.
I was imagining something more like concept-city based around an extensive quasi-Venetian canal network, where "swimmable" (like "walkable") defined a possible mode of regular transport.

Also swim-up bars.
I am not blaming Apple. But I am saying that older phones will stop functioning as phones eventually.

Apple isn’t supporting older phones out of the goodness of their hearts. The larger the installed based, the more they can sell you. There biggest revenue increases are coming from Services

I agree with you, the fact that they are providing security updates for a phone that came out in 2015 as a recently as two months ago is remarkable
Fish Speech: an open-source TTS with a low VRAM requirement
> My (probably naive) understanding is that 25519 already provided better performance than other algorithms used for similar purposes (e.g. RSA) when tuned for a roughly similar level of security; anecdotally, generating 2048-bit or larger RSA keys for me tends to be a lot slower than ed25519.

My also naive (an possibly out of date) understanding is key generation is much faster in with ecc, and that signing is faster too, but verifying is faster for rsa. So switching from a RSA to an ECC server certificate saves bytes on the wire, because keys are smaller, and saves server cpu because signing is faster, but may increase client cpu because verification is slower. The byte savings may make up for the increase in cpu though.
Boeing fleeing Seattle while trying to cheerfully pretend they're a "Washington company" was absolutely disgraceful
You don't to execute code to have it backtrack. The LLM can inherently backtrack itself if trained to. It knows all the context provided to it and the output it has written already.
Probably the real cost is in providing adequate ongoing support, and possibly insurances, and I suspect the banks know this and might baulk at too low a figure.

They don't want to be left holding the bag.

So I would have thought a risk based approach to the situation would be in order, especially given the nature of the situation.

What will it cost to get external validation services performed to check the code?

What could it cost if you had to pay consultants to do what would be needed if there was an error or a breach associated with the module, in terms of analysis and rectification?

What will it cost to have people available who are familiar with the code to make any changes that might be requested?

What will it cost to develop the code further and stay in front of competitors or attackers?

What will insurances cost, given the possible losses and probability a loss could occur?

Will you be limited to exclusivity? e.g. not sell to other banks who might be competitors.

Given the above, will you need to have dedicated premises and infrastructure?

So what, 5-8 people at reasonable wages for skills and experience, plus insurance, premises, infrastructure and other factors, like keeping people interested to stay working for you in a maybe boring job? Plus actually make some profit and stash some cash for a rainy day or another development opportunity to pursue.

Starts to sound like 1-3 mill a year all up is needed to run it as a going concern, if you are going to do it properly and depending where you are based. Maybe more if insurances are expensive.

Otherwise, are you sure you can't sell them the IP and walk away?
I would guess a 20-30k retainer in this occurrence would be a discounted retainer as well. I say this just based upon my personal experience with a few smaller firms.
ive been doing exactly this for bout a year now. feed it words data, give it a task. get better words back.

i sneak in a benchmark opening of data every time i start a new chat - so right off the bat i can see in its response whether this chat session is gonna be on point or if we are going off into wacky world, which saves me time as i can just terminate and try starting another chat.

chatgpt is fickle daily. most days its on point. some days its wearing a bicycle helmet and licking windows. kinda sucks i cant just zone out and daydream while working. gotta be checking replies for when the wheels fall off the convo.
Med device startup cofounder here.

In terms of difficulty in your path to market, from hardest to easiest (and ignoring some less common pathways):

1. Pre Market Approval: you're addressing a completely unproven technology in a novel and or dangerous space. Usually Class II and above.

2. De Novo: you're adding a new technology to a somewhat well known space. Usually Class II+

3. 510(k): There's already something in the market that addresses a similar problem and works using similar technology to your device. FDA understands these things well and have a very clear approval guideline, which usually just takes time to rubber stamp if the submission is of sufficiently high quality.

This is all ignoring Breakthrough Medical Devices, which have a ton of red tape cut (max 30 days to hear back about any submission, and if they run out of time, it's an approval). These kinds of devices are pretty rare, though.
Your idea is really a brilliant insight. Revealing.
As stated somewhere else, flash fraud has already been committed when you start testing.

Once you grab your dubious device, the seller has already got your bucks in exchange of a fake device.

You've been already and effectively cheated when those flash devices are being tested against cheats.
Would picking deterministically help through? Then in some cases it’s always 100% wrong
I have a limited experience, only having been involved in one trademark case professionally and am not a lawyer, but this was a case that very quickly settled and fees were still close to $30,000.
Yep, not faulting you at all! I too was surprised when I found out that it’s a straight 256-bit random value with a few bits masked.
I have been testing o1 all day (not rigorously). And just took a look at this article. What I observed from my interactions is that it would misuse information that I provided in the initial prompt.

I asked it to create a user story and a set of tasks to implement some feature. It then created a set of stories where one was to create a story and set of tasks for the very feature I was asking it to plan.

And while reading the article, it mentioned how NOT to provide irrelevant information to the task at hand via RAG. It appears that the trajectory of these thoughts are extremely sensitive to the initial conditions (prompt + context). One would imagine that if it had the ability to backtrack after reflecting, it would help with divergence, however, it appears that wasn't the case here.

Maybe there is another factor here. Maybe there is some confusion when asking it to plan something and the "hidden reasoning" tokens themselves involve planning/reasoning semantics? Maybe some sort of interaction occurred that caused it to fumble? who knows. Interesting stuff though.
My wife had this problem when she started metformin. After 2 weeks of diarrhea she tried a different approach, she purposely skipped her medication every other day for a week. The she gradually started taking it every day. The problems went away over night. Her doctor was baffled which is…funny.

I think some drugs are more easily tolerated by the body if they are gradually introduced.
In "serverless" defense, I'll put a one data point from myself. I built https://crates.live 4-5 years ago. I used a "complex" tech stack. A single page web app. Hosted in Github pages as static HTML/JS. For the server side, I used Cloudflare workers (Wasm) to run a GraphQL server (kind of).

The result: It's still up after 5 years. I never looked back after I created the project. I do remember the endless other projects I did that have simply died now because I don't have time to maintain a server. And a server almost always end up crashing somehow.

Another thing, Pieter Levels has successful small apps that relies more on centralized audiences than infrastructure. He makes cool money but it's nowhere near startup-expected levels of money/cash/valuations. He is successful in the indie game but it'll be a mistake to extrapolate that to the VC/Silicon Valley startup game.
Tulu script added to Unicode Standard
After more than a decade and a half of efforts and drama from within the community, the Tulu script has finally been accepted by the Unicode Consortium.

I was curious about the drama, so I searched around and found this article from 2021 that kinda explains why: https://restofworld.org/2021/tulu-unicode-script/
> Could you use a LLM function call to decide whether or not to respond

I've implemented this for a toy project before and it worked surprisingly well, yes! It can take some creative prompting to have the model understand which messages are actually directed at it, though, which I guess makes sense since every User message is _supposed_ to be?
World does not revolve around you, it's an infantile outlook :)

I simply see a discussion that might be interesting and respond to comments related to topics I feel proficient at.

In any case, how many deployments realistically adjust their goroutine stack size? What are the implications of starting with <500B-1KiB default stack (because asynchronously yielding task will use as little as <100B)?
> And how much data can you give it?

128,000 tokens, which is about the same as a decent sized book.

Their other models can also be fine-tuned, which is kinda unbounded but also has scaling issues so presumably "a significant percentage of the training set" before diminishing returns.
This is from August 2000!

Since them, much more detailed magnetic fields maps have been made of the Milk Way: https://www.forbes.com/sites/startswithabang/2019/09/23/this...

Also for other galaxies: https://www3.mpifr-bonn.mpg.de/staff/rbeck/PSSS18.pdf