skysight-inc/HackerNews huggingface dataset:
The article claims (in a screenshot without quoting sources, so take it for what it's worth) that "A recent blog post pointed out that GPT-3-generated text already passes the Turing test if you're skimming and not paying close attention".

This is certainly debatable, and I agree that it is pushing the limit a bit.

I think in the end, the "Turing test" was devised as a thought experiment, not as a final definition of AI. So I guess some freedom of interpretation is reasonable.
The early days of crypto were an under-regulated wild west but most projects are now moving from sleazy to more formal regulation. There is evidence that Tether is making moves to improve.
‘Pharma Bro’ Martin Shkreli Released from Prison Early
Ask HN: What can I do today to prepare for anti-aging tech of the future?
Given the state of anti-aging research today, is it clear yet which technologies will be the first to have some success at prolonging life? If we have a general idea of what classes of technology will be available in 20-30 years, then we should be able to guess what it will not be able to do, or what constraints it might have that increase its effectiveness.

What anti-aging technologies will be available in 20-30 years, and what can I do today to prepare to derive maximum benefit from them when they arrive?

I’m looking for answers beyond the obvious exercise and be healthy, although I should probably start with that. :)
we now use cloudinary for the image hosting :) thanks for letting us know about it.
>> new technology (fashion is about the new) often experiences a period of rapid change, and keeping up with change requires time and effort. Does somebody with a family, or outside interests, really want to spend time keeping up with constant change at work? I suspect no

BS.

I'm not one for terse responses but I cannot think of any better way to say it. This author evidently has never worked with anyone outside their graduating class. Without "outside interests" or "family" I predict they will burn out within five years.
How often have we run a Turing Test, where we asked the judge how confident they were in their final answer, except both participants were humans?
Funny, english people crying about being colonies.
People literally curate lists of websites that are only spam, and provide no value in search results[1]. Even if Google only cared a little bit about blocking the worst 1% of websites they don't already block, they would simply copy these lists, or use them as a starting point. Let alone devoting actual resources of their own. But they don't even do that.

[1] e.g. https://iorate.github.io/ublacklist/subscriptions
Your parents income( really expected family contribution) is used to calculate your financial aid eligibility. This would make it really hard for many students to choose to stop being dependent.
I went from iPhone 13 mini, to iPhone SE 2020 and was way happier. That screen was too big and no home button sucks. I yesterday just bought an iPhone SE 1 (shape of the iPhone 5s) (the smallest/oldest phone AT&T will support because of 3g removal). Excited to try it out
There is, but I’d wager most viewers have been bitten by a sudden cancellation by now.

It’s definitely survival bias, but it’s exactly the kind of thing that makes you question whether a good show is worth investing in.
The kids could also just ditch their phones and learn to live without them for a few hours when they wanna leave campus. Or buy a cheapo used one and use WhatsApp/Messenger off WiFi if they need to communicate with friends.

Not that I'm saying the parents doing this are in the right, just that it's pretty easily defeated IMO. Kids have been sneaking around behind their parents back since the beginning of civilization doing things they wouldn't approve of, this is just the next step really
Pretty much everything is more complicated than people (including engineers) think.

Take a simple example: selling clothing in a retail store. Sounds simple right? You have an inventory of items and someone pays for it. Should be a simple transaction, right? Well, now you're dealing with:

- How do you determine the price? There might be a retail price but there are sales, discounts, overrides for various reasons (eg defective goods), etc;

- You have to handle different payment options eg cash, credit card, debit card, gift cards, store credit. Payment methods can be mixed;

- You have to handle returns. These generally have to go back to the original form of payment. Some goods might not be eligible for a return. What if the payment is split between store credit and a credit card? Where does the balance go?

- Identity of the person making the sale or handling the return;

- Authorization procedures for returns and price overrides.

Everything is complicated.

As an aside, this is one reason why I'm so bearish on Web3 and smart contracts in general. The edge cases are so complex and possibly unknowable that codifying these, particularly on an immutable blockchain, to remove the need for human intervention seems doomed to failure.

Take Web3 identity. If you lose your password there are methods for recovering your account. The first is a reset password option. That may be insufficient and there'll sometimes be a human avenue to recover your account. Now consider a Web3 identity. I've seen various incarnations of these such as authorizing other identities who with consensus can recover your account. Well, those identities can be compromises so you've just added an attack vector. Alterantively that recovery mechanism may become insufficient as people lose identities themselves.

If these problems weren't complex they'd be solved problems.
Our goal at this stage (invite only beta) was not to get users who just want to try it out, but who actualy wanted to contribute by reporting bugs and suggestions as beta-testers. This is why we have a survey form, as completing it signals wilingness to invest time in the product. Soon (in two weeks) we will move to public beta.

Even then we won't have search without an account, among other things because bots would probably kill us.

(kagi founder here)
Am I reading you correctly in that you propose that the scams, et. al., are a conspiracy of The Man to tarnish the good name of cryptocurrencies? Seems the more simple explanation is that if there's money involved, the scammers will come a'knockin'.
Ah OK I haven't looked at IFA, but I wonder how it would scale to 40K lines of code? As far as I know that is beyond the state of the art, i.e. a research level problem.

Yeah I should get in touch for sure... I remember talking with John about the Apache Traffic Server (formerly Yahoo) and his Python-to-C++ pyc compiler almost 10 years ago!

Right now I'm contacting a bunch of people in the EU, since the funders have some preference there. But yes Shed Skin is one of the closest things!
You’d still have to apply the right tax rate for every line item. If you allow the user to edit the total, then which of the tax amounts are you going to recalculate?
https://archive.ph/iuk31
Quite a journey Craig and really funny to see how Heroku ended up with PostgreSQL. In my estimation, that decision is one of the biggest factors in the growth of PG adoption everywhere over the last decade. What a butterfly effect for that engineer chiming in.

Dataclips really was a great feature. We were using it for all of our internal dashboards at the company where I worked in 2013. One of our support staff even learned SQL due to interacting with it and went on to get a CS degree a few years later.
Thank you for writing this bit of history, Craig! I have a personal half-serious theory that it was Heroku that really gave Postgres its break-through popularity. I think life is often like that: after years & years of hard work, you get just the right coincidence of external factors to let you take off. All during the 'oughts Postgres seemed like an eccentric ideological choice over MySQL, but most of us had never really tried it. With Heroku we were basically forced to use it, and suddenly we could see that all those eccentrics were right. I love Postgres and have tried to make it more & more a part of my own career. So thank you to you and the Heroku team for making such a principled and brave choice back then.
> And also, think about it from first principles - why would people starting their programming careers 15+ years later than most people need to pick different tools?

Because the people hiring people that are relatively inexperienced but not practicing undercover age discrimination tend to be very much not representative of the industry, or opportunities for new programmers, at large; people starting their career late need to specifically target that market segment, not the more general one.

Note: I am not convinced of the specific advice, particularly in language focus, that the author here gives, but it is still less wrong than your suggestion that there is no difference between the optimum approaches for (by age) late- and early-entrants to programming.
I'm Anh-Tho, one of Lago's co-founders here. Thanks for sharing!
What did you do then? I'm curious!
>. With business customers, leaning back in the legal framework encouraging tax fraud will not fly.

Yes which is why in nations like Portugal, where any business invoice may be subject to accountability to government, there totally isn't a massive informal (read: tax-evading) economy to deal with the fact that the government makes it literally impossible (at least in above words) to accept an invoice legal in the jurisdiction in which it was issued.
I'm in my early 50s with a career spanning three decades, worked in fintech, worked in various FAANGs, lived in SV for close to 10 years, lived in NYC for half as long, now semi-retired.

For someone young (early to mid 20s), I agree with what you wrote. Being really, really good and actually enjoying doing it, should be a must.

For someone of your age or older, I see a lot more risk. If you start from zero, it will take you at least 5 years to build up ammunition (a degree from a good university and some demonstrable experience) that's going to open the doors that you need open and give you a shot at passing the entrance tests. And then the "being really, really good" part comes in except you're now 5 years older facing fierce competition and there's no guarantee that you will succeed (who knows what the market will be in 5-10 years, the trajectory doesn't look promising).

Personally, I wouldn't do it. The skills needed to offset the risk are hard to acquire in the timespans we're talking about, unless you're truly exceptional. But offseting the risk for me means living in the US and working at one of the FAANGs (job security and very high total compensation). Others see it differently.
I have to disagree. You produce a data structure representing the UI. That's basically the definition of declarative. Just because you can build that dynamically doesn't mean it is not declarative. You could always build up XML dynamically as well.

It's a far cry from an immediate mode API where you are making draw calls.
The difference is marginal at best. Most of the requirements are obvious and never/rarely change, like your address or the date. And adding a an incrementing number to a set of documents isn't exactly rocket science, either.
Well, Gödel set out to prove incompleteness. The first statement that comes to mind is “there is an unprovable sentence” but that is too general. What Gödel did was find out that “this statement is unprovable” is “definable” in Peano’s system (once it has been encoded), and that’s it.

Nothing especially contrived there. Less so for a professional logician.
...specific use cases being the key operand here. Unified memory is cool, but there are reasons we don't use it at-scale:

- It needs extremely high-bandwidth controllers, which severely limits the amount of memory you can use (Intel Macs could be configured with an order of magnitude more ram in it's server chips)

- ECC is still off-the-table on M1 apparently

- Most workloads aren't really constrained by memory access in modern programs/kernels/compilers. Problems only show up when you want to run a GPU off the same memory, which is what these new Macs account for.

- Most of the so-called "specific workloads" that you're outlining aren't very general applications. So far I've only seen ARM outrun x86 in some low-precision physics demos, which is... fine, I guess? I still don't foresee meteorologists dropping their Intel rigs to buy a Mac Studio anytime soon.
ID.me has had quite a bit of controversy. Some interesting related non-Krebs (I don't support Krebs after his doxxing of innocent people) reads:

https://www.techdirt.com/2022/02/01/idme-finally-admits-it-r...

https://www.techdirt.com/2022/02/15/idme-doesnt-have-enough-...
Thanks! Macroexpanded:

Jailer: A tool for database subsetting, schema and data browsing - https://news.ycombinator.com/item?id=29939890 - Jan 2022 (14 comments)

Jailer: A truly relational database client - https://news.ycombinator.com/item?id=27811752 - July 2021 (2 comments)

Jailer: A truly relational database client - https://news.ycombinator.com/item?id=27808653 - July 2021 (17 comments)
PROs:

- Your documents are kept with revisions instead of overwriting then.

- REST API already built in

- Authentication (also usable in your app) already built in

- map/reduce

- CouchApps

CONs:

- corporate supported development is dwindeling (I believe, not entirely up to date on this)

- only REST API, no wire protocol

- CouchApps
(Render founder) Security and uptime are the only two existential threats to Render, so you can imagine we lose enough sleep over it. We regularly fill out security questionnaires that lead to successful migrations. Still, we can do a better job explaining and documenting our security posture publicly.
What kind of companies did you apply to?

I'll share my personal experience, in case it helps. I only apply to small startups (less than 50 employees, but I usually get hired in places with <10 people). These have much more straightforward and short hiring processes. I find those companies solely from HN Who is Hiring thread or AngelList. I never got anything from a job post on Linkedin (much less Indeed and etc). I am a frontend developer, but I do see a lot of Python positions.

If you filter for companies based in the US only, the pay is pretty good.

There is a lot of luck involved in getting hired (especially after going through an interview, since from there the process is very subjective). It sucks, but you just have to keep trying. One day you will be the lucky one. Good luck!
In machine learning (especially deep learning or neural networks), the 'training' is done by using Stochastic Gradient Descent. These gradients are computed using Backpropagation. Backpropagation requires you to do a backward pass of your model (typically many layers of neural weights) and thus requires you to keep in memory a lot of intermediate values (called activations). However, if you are doing "inference" that is if the goal is only to get the result but not improve the model, then you don't have to do the backpropagation and thus you don't need to store/save the intermediate values. As the layers and number of parameters in Deep Learning grows, this difference in computation in training vs inference becomes signifiant. In most modern applications of ML, you train once but infer many times, and thus it makes sense to have specialized hardware that is optimized for "inference" at the cost of its inability to do "training".
That sounds like a one way ticket to anticompetitive lawsuits from the FTC
From that page:

>One complete subscription...

Oh, so Apple just discontinued the one that comes free with the purchase of the hardware[1] and wants people to move to a subscription. I guess my confusion should have rather been frustration.

[1] - https://support.apple.com/en-us/HT208312
You can sign up for cryogenic conservation of your body in case your near death so that you can be woken up when scientists find a way to revive you.
How compose-able are ML solutions? I'm wondering if coming up with ok-looking generated headshots (face at a specific, known, predetermined angle, in a neutral and standardized context, independent of background features) is not ground-breaking, but embedding that capability in a dynamic image generator with myriad other objects, headgear, lights and shadows, etc. may be.
I do, but I don’t like many text to speech voices at the moment because they don’t always enunciate in a way that makes sense. So I’ve been looking forward to the day when I can use custom human voices to read me news articles.
Browsers typically support a minimum font size setting.
Yes. I interpreted the title to mean "If you put .gitnore in your.gitignore, the .gitignore stops working". And so I immediatly thought "that's wrong".

Why would anyone thing you wouldn't be able to put .gitignore in your .gitignore?
Shocking—photos made out of a data set of existing photos look like photos!
maybe i got the pricing wrong, i thought it was closer to $100 and that FSD was more expensive than 10k. I would need to check the numbers. I will say though a) if FSD wasnt something i already had, i'd have canceled the subscription by now, and b) I tend to keep my cars about 5-7 years, so it's certainly not a massive payback buying it upfront when it doesnt work for a period of the first few initial years.
> I'm inquiring as to what logically is supposed to happen in the scenarios that occur based on your proposed "pretty simple" solution.

Here's the simplest solution: If the limit is reached, stop serving requests, stop accepting new data, but don't delete any data. Allow static storage costs to go over the limit. That is probably what 99% of people who ask for a budget cap want, and it's the most logical thing to do because typically 99% of the charges are for bandwidth/requests/processing and only 1% for storage. If I set a limit at 10€ and amazon ends up charging me 10.2€ I can live with that.

The next simplest solution would be to look at how much is currently stored, multiply that with the storage cost per hour, multiply that with the remaining hours in the month, then subtract that from the monthly budget, and stop serving requests or accepting new data as soon as this lower limit is reached. This will guarantee that you never go over the limit without having to delete data. If data in storage is deleted before the end of the month, you'll end up spending less than the limit.

Now if you consider this basic math too complicated for a software engineer making $300000 a year, you could do something even simpler: allow the customer to set a limit on each resource. Eg. let the customer say, I want to limit S3 to 100GB of storage and 5TB of bandwidth and 2 million requests (or whatever). Of course that would be a bit of a hassle for the customer, but it would be very effective at preventing surprise charges.

> the majority of people want their stuff to stay up

At any cost? That's unlikely. I'm pretty sure that every company has some limit where they'd prefer the service to be down rather than pay the bill.

But if you go back up the thread you'll see that this discussion is about hobby users and tinkerers, and people who just sign up to try out the tech. These people absolutely want a hard cap on potential charges, and if you don't offer that you might scare them away.
It was mostly Bing and Yandex. The latter was responsible for the odd Russian language results you'd get at times but presumably produced English results as well.
Ask HN: Is there a free alternative to Gmail with Custom Domains?
Feature, not a bug. If there's pervasive lawbreaking, then the officials can collect more bribes.
I can't read your comment. The hyperbole is too blinding.
What I Learned from the YC Startup School Podcast
Lavender's Game: Silexan for Anxiety
For non-English locales, Google sucks 99.9% of the time for popular queries since they allow spamming from big media outlets. A top result is literally composed of spammy SEO keyword content filled with a chain of questions in the article. So (I think) it sucks for 'normal' people in non-English.
Having a structured way to select the best among several backends is completely canonical and expected in systems like these.

Reliable systems are built at the client, not at the backend. You get those extra 9s from having a smarter client, not from having a more reliable backend. Trying to make your lowest layers flawless is a fool's errand.
Although changelog says:

> v1.13.4 (2022-04-07)
> This release has been verified to work with Erlang/OTP 25 RC2.
> there's a ton of crime there. It's not at all similar to being a police officer in a town.

I assume people get this idea from the media, but it's not true--crime rates in NYC are significantly less than that of most other US cities.

https://en.wikipedia.org/wiki/List_of_United_States_cities_b...

A pandemic-related uptick (that has affected the country as a whole) doesn't change the fact that the cops from St. Louis are dealing with a murder rate about 20x what we have in NYC.
There are a lot of SEO-spam sites that look a lot like this one that are designed to top the results for searches like "technology 1 vs technology 2". They are all completely useless.

IMO If you really want to provide value, you have to dig into the actual details of these technologies, not just offer a top-level blurb and category label.

Just look at any Show HN post comments, engineers crave the details when it comes to comparing and choosing technologies.

Example: One thing I have always desired is somewhere to see all the major databases/event stream/persistence technologies and see what kinds of different consistency guarantees, replication, backup, recovery, etc. they each offer.

This goes a bit deep (most datastores have a bunch of different ways to configure and tune them for different consistency levels [1]) and is obviously more effort than the low-effort "this vs that" sites, but I don't see much value in the existing "this vs that" offerings.

[1] https://docs.redis.com/latest/rs/concepts/high-availability/...
To be honest, I would never do something that requires a single employee ever again. I sold my first company because soon enough, all you get to do is manage politics and not the thing you signed up for — Sounds infantile but at some point you have to stay true to yourself no matter the benefits. If you're more of a team-player, there are obviously better options today (remote, etc.) — The only thing I would recommend is not getting too romantic with a co-founder, having clear responsibilities from day one and don't try to make friends along the way — in the end it's all about building success.
A little bit more detailed than that?

I used to work for the oil industry felt (and probably objectively is) far less stable.