skysight-inc/HackerNews huggingface dataset:
> And I'm not aware of either term...being used to apply to the period from the 8th - 13th centuries

The Journal of Near Eastern Studies (https://www.jstor.org/journal/jneareaststud) is typical in defining its scope as the Near East, from the ancient times to pre-modern Near East. As I said, "Near East" is the standard term for referring to the history/archaeology of this cultural region in pre-modern times.

When you want to specify the pre-Islamic Near East, the standard term is "Ancient Near East", as this from the Journal of Ancient Near Eastern History (https://www.degruyter.com/journal/key/janeh/html?lang=en).

The Journal of Ancient Near Eastern History seeks to encourage and stimulate the study of the history of the ancient Near East, which is broadly defined to include areas from Iran to the western Anatolian coast and the Black Sea to Southern Arabia from its prehistoric foundations to the Late Antique period.

The Late Antique period is very roughly the 3rd-7th centuries.
> Contactless had no hope with a PIN

I’m not sure if it’s true for all EU countries and banks, but in general you don’t put in your PIN every time with contactless. The card usually works for a number of transactions without a PIN, often up to a certain limit, after which it asks you to insert it again.
I've been watching this thread and the comments in it unfold with some amazement. You make a simple and valid point and yet some people are unable to even step out of the capitalist mindset for a second to see that it is perfectly possible to add value to society without a profit motive. At some level this should probably be expected but I can't help being a bit shocked by it. Thanks for keeping up your end (and in a respectful way, no less).
In the era of AI's relentless advance, a profound yearning for human touch and handcrafted marvels emerges. For example we have our Handmade conference [0]: a celebration of software built with heart and soul. (Feeling poetic tonight.)

Practically speaking, as GPT-4 took the world by storm, our ticket sales skyrocketed in response. Of course this is just a correlation but this year we're on track for a record-breaking sellout. So we could predict people craving ownership and authenticity (whatever that means to them) free from the invisible hand of AI.

[0] https://handmadecities.com
Why splitting logic between Postgres and an application considered worse than splitting it between multiple micro-services? A DB is a storage service with INSERT/SELECT/e.t.c. as an API. Why we cannot extend this API to include stored procedures too? Indexes are commonly used to enforce data integrity. Why we cannot use triggers to do this even better?
It's a "pull request" because you're asking someone to pull a commit from your branch/repo into theirs. You're quite literally making a request.

This actual change could be anything. You could just as well provide them as a patch they could apply by hand. The only formal aspects of the process, e.g. reviews and tests, are organizational. As an organization the acceptance of a pull request doesn't need a bunch of reviews and tests associated.
With sideloading there's nothing preventing a developer to write a native app, and provide an in-app input for entering credit card number and handle payments without Apple involved at all.

Definitely less convenient and more risky for sure, but technically no problem at all.
U2 did that in 2018 although only for their concert goers...
Oh interesting, of course they do!
Interesting read, I was wondering what happened that day. As an operator of a small network of fastchargers, we were delighted to have a purchase price of negative 20cent per kw. Which is huge.
The big difference between SVN and Git is that SVN is centralized (a single linear history is enforced at all times for everyone) and Git is distributed (each user has its own local history).

Both models have advantages and disadvantages, but for many people working on the same branch the centralized model is arguably better.

(in the end, both Github and Gitlab workflows mainly try to put more 'centralization' back into git)
Once the app is updated, you will be asked at the next app start. You can either choose a Google account to sync your TOTP secrets to, or you can continue without a Google account, in which case your secrets won't be synced.
By the way, if you're interested in cooperatives have a look at the Mondragon Corporation, it's a fascinating success story.
I was somewhat amazed that a significant university doesn't handle IPv6 - sigh.
Came here to say exactly this. Over the last 12~ years working with PostgreSQL I've dealt with quite a few performance related issues - almost all were poorly written queries.
SQL Server is one of the descendants of Ingres, and PostgreSQL is, as the name might suggest, the successor project for database research after Ingres. They're both great databases really, it's a fun connection in their mutual history.
Then I guess I'll have to repeat my top reply to you then.

"Relays can be authenticated. If you don't want your relay to accept data from anyone, don't leave it open. Same with any other Internet protocol."

If you don't want people to host illegal stuff on your server, do not run an open relay, an open FTP server, a social network, or an image host.

If you do, be prepared to have to work hard to keep bad actors at bay.

It's not strictly a NOSTR fault, and there is no reason why YOU need to run a relay.

Your comment is misleading and a little disingenuous: Nostr doesn't make you forward stuff. A client doesn't have to forward anything. It just connects to relays and subscribes to topics. Relay != client.
Why does anyone think that apple is not spying on its users? They have a massively growing advertising business, that should tell you everything already. The only difference is that they don't want anyone else spying on their users, but that's simply to protect their business, not for the privacy of customers.
While I understand your position, none of this is new. I think this is one of the growing pains rust will have to survive.

I once read a text about someone implementing C++ before it was standardized. Whenever something wasn't clear, he tried it on CFront. CFront would generally crash. That's a lot worse than rust today, and there are a lot of C++ compilers nevertheless.

For the NP-complete problem, here is how Java solved this: The compiler has to validate that every function's execution ends with a valid return statement. This is literally the halting problem, impossible for the compiler to solve.

As a way out of this conundrum, the java standard dictates the algorithm. It is conservative, so it rejects some valid programs. But it is part of the standard, so if one java compiler accepts a program, you know all the other ones will too. So all java compilers make the same mistakes, as required by the java standard. A compiler is simply not allowed to implement a better algorithm.

While it is a huge effort, gccrs will probably succeed, and help clarify the rust standard in the process. Real risks are more long term: gcc java slowly petered out. For rust, things seem better, as gccrs has a stable funding source.

Update: Java's problem/algorithm is not (only) the return statement. It is the requirement that every variable is defined before being used. You find it as 'definite assignement' in the compiler standard.
Lest we forget our lore: 0xDEADBEEF and (based on a true story!) 0xCAFEBABE.
I don't _think_ the query planner takes "current load" into account.

If you have:

- Same resources (CPU/memory)
- Same settings (eg work_mem, amongst others)
- Same dataset
- Same/similar statistics (gathered with ANALYZE or the autovacuum)

you should get the same results. If I'm wrong, please somebody correct me!
This Would've Changed Photography Forever [video]
Ask HN: How does prompt optimizer works?
I think one possible way is to obtain dataset with prompts for given model and train the language model. Optimized prompt could be generated one, longer, with the "add-ons" that are typically added to the prompts with similar meaning. What are the technical solutions underlying the services as e.g. https://promptperfect.jina.ai/?
You should check that famous youtuber’s video on the bug. It looks like they’re hard to notice as they only come out for 10min every night and you can’t feel them.
I still want to host my own incoming mail server for my domains but because sending is becoming harder and harder, can anyone recommend a service where I can relay my outgoing to mail to?

Some cloud providers now even block port 25 outgoing so you can't even send mail out directly anymore.
LAION doesn’t publish the images, only the metadata, which includes the original image URLs. Anyone who wants to make use of the image set has to re-download the images from the original sources [0], and is then liable for actually using the images. Arguably, the alt text contained in the metadata is still subject to copyright though.

[0] see also https://news.ycombinator.com/item?id=35681085
It frustrates me the one size fits all approach often taken to software development best practices.

If no one is to review the code, then all code is either written by pairing/mobbing, or else it is the product of one persons thinking, blindspots, biases and all. It's great if you work in a team that pairs in everything, does trunk based development etc; that doesn't make it suitable for every team.
Can’t you just follow people that don’t talk about it? There’s no algorithmic feed that feeds you stuff you don’t want
You can’t patent leaves
Not the parent, but I have a friend who knows both Postgres and MySQL and prefers MySQL because "it is simpler and hence there are fewer ways things can get broken". (Not that I necessarily agree, but he seems to have a point.)
That wasn’t my experience in Munich recently, although I could see it being the case outside of larger cities.
>And then, when you download the Firefox installer, you are announced that it could harm your device.

Is it actually true?
While it's true that you need to feed some source images into the AI to get good results, what you feed into them can be pretty arbitrary and low quality, as all you are really doing is providing the AI with information about positioning and composition that can't be expressed with a text prompt. It's pretty much the "How To Draw an Owl" meme with AI doing the last step.
> To build LAION, founders scraped visual data from companies such as Pinterest, Shopify and Amazon Web Services — which did not comment on whether LAION’s use of their content

Pinterest, "their content"... not sure I agree with that but if we're going to use the logic that things saved to Pinterest by it's users becomes Pinterest's content then isn't LAION doing the same thing and the content becomes LAION's content when it's saved to their database of images...
It seems like we are reaching the same conclusions as Dave Farley on our development team. We have pivoted to just let everyone merge in their stuff and do "reviews" retroactively when we stumble upon code not up to the standard we set.

The reasoning behind this is exactly that we trust individuals on the team to merge. and because reviewing in the traditional sense seems to be a formalisation of distrust: Something you do when you don't trust your peers to implement and put in production properly tested code.
Wow, I didn't know!
You’re criticizing one of the best youtuber. Ballsy.
Might be that the major evolution is that nowadays "dissenting" became to be an ass about it, because the others are just "snowflakes" unable to take my "well researched" opinion.
Am I the only one for whom the "Bitstream Charter" font family on this page causes the text to be mostly invisible (except for some punctuation characters)?

System Information: "Bitstream Charter" is installed; Georgia is not installed; Happens in Firefox, but not in Chromium; Arch Linux
I believe it is not possible to imitate a human without the imitation being so complex as to experience reality itself. Your argument is basically the Chinese Room experiment, in which my view is that the whole room is conscious.
What was your usecase that you were unsatisfied with keepass?
Show HN: TxJSON – An extension of JSON5 with rich inline type information
This is something I have been working on as part of a larger project where we use it for programmatic test generation. This extended syntax allows the inclusion of type information within a document.

This means that after parsing, a user-defined deserializer can pick up the raw value and do anything with it (whatever it returns is included in the output of `parse`), and that a user-defined validator can allow or reject it with an error.

Documentation (mainly for deserializers/validators) is currently sparse since I'm somewhat busy with a deadline, the tests have many examples though. I plan to expand on it later.

Here is a glance at what it looks like:
```
{
x: date "2001-01-01", // it can handle custom deserializers!
y: 123n, // it can handle `BigInt` out of the box!
z: /^I\sCAN\sPARSE\sREGEX$/im, // ...and also regular expressions!
w: undefined, // ...and even `undefined`!
}
```

There are more examples on GitHub!
Elon Musk’s Twitter Blue check-mark fiasco is a master class in business failure
Rather than allowing side-loading on iOS. I hope Apple is forced to open up its bootloader on iPhones.

Step 1: Go to the Apple store and ask to unlock the bootloader, they give you a form to void the warranty and Apple Care, they then unlock the bootloader.

Step 2: Wait for the Asahi Linux, Valve/Steam Proton, Google, and the Pinephone teams to showcase their skills.
Regular end user…. docker-compose? We have very different concepts of what a regular user is. Surely, generating a key pair must be infinitely more easy than setting up docker?
With all the precautions the author takes, he ends up with a weird take:

> If you take away the appeal to trust, though, there isn't much left of the argument. What remains is essentially: Pull requests were invented to solve a particular problem in open-source development. Internal software development is not open source. Pull requests are bad for internal software development.

The specific point he tries to reword exists to explain that not everyone needs as much trust than open-source, and, therefore, that not having PR isn't a fatal flaw outside of open-source. The people who use it do so within a discourse along with other points explaining what they gain from forgoing PRs (usually, better continuous integration).

I don't buy the whole discourse about not using PRs, but I'm also not sold on the idea of dismantling a coherent discourse into separate talking points and demanding that they should stand separately. I'm also not a fan of rewording someone else's point and slipping a big non-sequitur in that rewording.
I don't really have any opinion about PRs versus trunk-based development, but I do have a small insight that I think is useful when you're thinking about which one to choose. The main advantage of trunk-based dev is speed. You don't have to wait for a review of work. You're trusting the team to merge things that won't break stuff. That's awesome, but if that's the case then you should also be able to trust them to review PRs quickly enough that they don't block work. Equally the converse is true - if you can trust your team is motivated enough to review PRs quickly they you can probably trust them to do work together well enough not to really need PRs.

If you can trust the team with one and not the other then something is wrong. There shouldn't be any "this way is better than this other way" argument. Your team should be capable of doing both. If it isn't then neither will work very well. You're going to have problems, conflicts, bugs, etc no matter what you do.

Believing that the team should stop PRs because they're too slow, or they should stop trunk-based dev because pairing takes too much effort, are both red flags. They're both saying that the team has a problem to address.
Yes, but bedbugpaper is not at all what you described.
Tesla gives update on battery degradation: only 12% after 200k miles
I don't understand it either.

Author seems to be arguing against long functions/procedures. But if you move that to the client, presumably with ORM support - you're going to be executing more or less the same sequence of SQL queries and commands. Only difference is that when doing it on client you will have a lot of latency.

Yes, you can cache some data in between those commands to avoid same multiple queries, but if you use temp tables to do so, they will use memory only if it is available, otherwise you are limited with the actual storage size.

Only time I had memory issues with PostgreSQL when I used too much data in arrays and json's. Those are memory only variables. For example, I'd return a huge json to client and I'd run out of memory on PostgreSQL. I started streaming row by row and problem solved.
I have a friend that runs it on his gaming rig.
Zero Shadow Day
Living with doubt is not easy on our minds, that's why. Today we know there's a portion of fake content there already but we're not living with the doubt that %100 is fake.
Some JavaScript frameworks will work, others will randomly break with timeouts and other weird failures. While we'd hope we'd get less JavaScript abuse all that would happen is no one would use that browser.
When I give you a barrel of oil in exchange for $80, that oil is priced at $80, and that is often phrased as its value.

When oil prices went negative in 2020, people were giving both the oil and $30, and so the oil was priced at -$30. Sure, the oil was worth $30 to give away, but the oil was not valued at $30; it was valued at -$30.

Many people sell speech (eg. President Obama has given a speech in exchange for $400K). When you give both money and the speech, just like oil, that infers the price of that speech.
That already wasn't the case without ChatGPT.
> One of the main reasons I shoot with an actual camera body is exactly because it has a camera body. The ergonomics of shooting with a phone are terrible.

For me it's that and the conscious decision to get a camera ready and take it along for the ride.

I'm not sure if it makes senses, but to me that's an attitude shift in how I take photos.
In the word "aurochs", the "aur" prefix is the same as German "ur" indicating beginning or origin.

(To beer drinkers around the world it may be familiar in the name of Pilsner Urquell, the original pale lager. Quell means source.)

So aurochs is literally "original ox". I don't think there is any other English word that preserves this prefix.
And you can win them back just as easily, so there.
I don't assume my colleagues will always make "reasonable" choices and furthermore correctly express those choices into code any more than I will myself! In fact perhaps most of the issues I find in PRs are after reviewing my own ones (often it's silly things like accidentally including files/commits I shouldn't've have). Plus knowing someone else must've approved my PR stops me feeling quite so silly if it does end up breaking something :)
The breakfast order analogy to me falls down because not being able to merge a PR into the mainline branch immediately is exceedingly rarely something that holds me up - there's always plenty of other stuff to do. And the time I spend reviewing PRs is valuable in its own right, even if I find nothing wrong (understanding the codebase better etc.). Sure the odd PR or two for a truly trivial change slows up the works a little but they're pretty rare and a it's a small price to pay.
Having said all that, I'm genuinely interested in what studies might have been done to genuinely guage the effectiveness of the PR/review process. I've certainly worked on some (open source) projects where it clearly was a major drag on productivity, as very few people had approval rights (wherever I've worked professionally all devs have the same rights - single approval from any other dev is always sufficient).
I think maybe you're misunderstanding Deming.

Consider his claim about operational rigor in the context of these guiding principles:

https://www.mindtools.com/azyjjsx/demings-14-point-philosoph...
Indices in Postgres do contain NULL values. My guess is that it's possible to make IS DISTINCT FROM an indexable operator, but it wouldn't be straightforward given that NULLs are a bit of a special case for indexing comparisons in the sense that they totally ignore data types. IS DISTINCT FROM would probably have to redefine a bunch of existing opclasses to account for the possibility of NULL.
If you liked it, you may like "FAQ on LoadBear's Instrument of Precommitment" (https://docs.google.com/document/d/1nRSRWbAqtC48rPv5NG6kzggL...), which is also about mind uploading, and "Basilisk collection" (https://suricrasia.online/unfiction/basilisk/), which is a fictional Wikipedia article about SHA-256. You may also enjoy the book The Age of Em; it is nonfiction futurism, albeit increasingly unlikely.
This is a tech forum. We tend to enjoy discovering and exploring new technology that's alpha quality and not yet ready to hit the shelves, and maybe we'll help them get there.

Nostr is a couple years old. How old is Mastodon? Of course it's not grandma friendly yet. No one is trying to sell it to them just yet.

I don't get this common and frustrating criticism often posted on here for any new project and idea. Every major breakthrough has started as a buggy, half-arsed project with many shortcomings. Pointing that out is not very constructive.
Strlcpy and Strlcat – Consistent, Safe, String Copy and Concatenation (1999) [pdf]
I think government should be promoting workers cooperatives by waiving business and salary taxes for them. Otherwise they can't compete with traditional businesses that can squeeze out additional value from workers at workers expense.
Why “Just learn to code” doesn't work?
Check out https://www.percona.com/blog (filter for MySQL)

I have been a heavy user of the Percona distribution of MySQL for many years and highly recommend it. I think that most of the MySQL articles on percona.com are relevant for other MySQL distributions.

As a side note, depending on the software stack, ProxySQL can have a major positive impact on performance and scalability.
I second that. I found it by far the most pleasant database to work with, including its tooling. Postgres is probably second. Too bad SQL Server is so expensive.
The only change in pricing that ever happened in those marketplaces was in direct reaction of this anti trust lawsuit, does that answer your question?
> This is not scientifically well supported

Inform yourself better. We have more than a vague feeling that they play a major role on many ecosystems.

Zoologists study this animals since XIX century at least and there is a pile of literature about them bigger than the Liberty statue. Mosquito life cycle in particular is middle-school grade knowledge.
Until the day your phone breaks for some reason, or one of those payment monopolists decides you shouldn't be able to spend your money because you modified your phone without their permission, and you find yourself unable to pay for the bill. Eliminating cash also eliminates the possibility of having transactions that are difficult to trace for whatever reason, at least in small amounts. What if something you take for granted today becomes illegal (weed, abortion, anything you may think of) and the government will now have near total ability to see what you bought. It's a bleak future without privacy.