skysight-inc/HackerNews huggingface dataset:
tar --create --owner=0 --group=0 --mtime='2000-01-01 00:00:00' \
--mode='go-rwxst' --file test.tar /bin/dash /etc/hosts

tar --list --verbose --file test.tar
-rwx------ root/root 125688 2000-01-01 00:00 bin/dash
-rw------- root/root 1408 2000-01-01 00:00 etc/hosts
Tech bros love it. And tailscale. And saas as a whole. Data sovereignty means you can’t be kind by the adtech industry so it’s not cool.
I'm sure the tech is neat. But I get a real sinking feeling from how hard tech giants like "Meta" are trying openly to create dystopia. The "Metaverse" is not aspirational!

> That understanding would let AR glasses tailor content to you and your individual context, like seamlessly blending a digital overlay with your physical space

Horrifying, if it ever takes off in the way that "Meta" wants it to. Take the modern smartphone disease and amplify it a few orders of magnitude.

> While LLMs rely on vast amounts of training data that typically comes from a range of publicly available text sources on the web, no such repository of information yet exists for physical spaces at the scale needed for training an end-to-end model.

Considering the tremendous scale in question, the "yet" is also terrifying. The only way to collect such a dataset would be if some large fraction of people were wearing always-on, network connected cameras. Meta clearly sees this future and wants it; the kind of future where everyone wears a Meta headset, all the time, and has their experience of reality mediated through it - optimized to maximize shareholder value of course, under the watchful eye of The Algorithm. A panopticon AI shoggoth.

Meta is an AI paperclip maximizer, and it is getting uncomfortably close to the "RELEASE THE HYPNODRONES" stage.
I appreciate the insight.

That said, you seem to imply that detected cancer does not resolve without modern medicinal treatment? Small sample, but I personally know one case where it did.

Also, do you believe that ongoing stress (after receiving what is widely considered a death sentence or one way road to constant treatment) has no influence the outcome?
Which is why that kind of stuff only works properly with languages that combine dynamic loading with rich runtimes, alongside automatic memory management, having all puzzle pieces to work together to keep the application running when the library is removed again.

I came to accept that in languages like C and C++, the best path for dynamic loading code is really via OS IPC and external processes, the decrease in hardware resources and simpler programming model of using shared libraries as plugins, isn't worth the endless amount of debugging hours regarding program crashes.
You spend about 8 hours per day in something other than this definition of the “real” world.

Levels of reality imply levels of truth.
So if you managed a team, and when you look at commit histories you notice that one person has <1 commit a month and you look at the commits and they're trivial... you would disregard any concerns?
> However what happens on my private property is a privacy violation if it is recorded without consent.

And the biggest enablers of violation are things like ring doorbells and dashcams. There is no comeback in my country, don’t know about the US.

Governmental and commercial cctv has checks and balances. Domestic just goes onto planet wide databases with no control.
If a handful of payment processors can decide who can get money or not, it sounds like you need laws to force them to be neutral. Imagine if you couldn't put a truck on a road because the road is owned by someone that doesn't like your business!
Great one. submit it to productivity.directory
Well payments can be made, just not anonymous. If you want to receive from those wallets, you have to identify the sender (i.e. ask for ID). There is no mention of a global database where you have to put the ID data, you just have to keep it on your own records.
The first wave of BYD cars in Europe are not competitive yet. The price difference is small, they are less efficient and they have other issues (space optimization, driving comfort, etc)

But in only one year they already started to fix all this. They are getting cheaper, correcting mistakes and opening factories in the EU.

Old makers announce a car and need 2-3 years or more to have it in the market. The Chinese brands seem to need less than a year. There will be blood.
At this scale the negotiated price with AWS could be a lot cheaper even than the sticker price on 3 year reserved instances.
> However, the Ireland law firm expects these laws to become fully operational before the usual enforcement timeline.
It also has not entered into force, and I don't think it has completed approvals yet - as far as I understand the EU Council still also need to approve it, but I might be wrong about that part.
Most automakers seem to want to be banks renting out way too expensive cars for the customers budget. That segmemt is way too crowded with higher rates.

BYD seems very interesting. I would need a small commute EV. Have anyome tried this model?
You should have posted that link as a top level comment, because it speaks to this guy's character (if true). I was going to defend the statement, as everyone has heard the tongue-in-cheek phrase "Man Jose" ridiculing the area's gender gap, but I won't defend the guy.
Bank notes that are not legal tender for all debts public and private are literally worthless.

The entire point of a currency is you can trust them to have their value anytime anywhere within their region(s) of circulation.

(Yes, I'm using American language to speak of European affairs, but that is beside the point.)
Whether it be Hateful 8, Scarfolk, Simpsons, Life of Brian, 1984, or Brave New World, doesn't reality always inform the satire?
but now that the crypto boys are back en vogue and are returning from hibernation / ai-vacations due to price levels you can combine 2 hype trends into one and capture the imagination & wallets of 2 intersecting circles of fools!

so if these days someone is talking about decentralized anything i'd bet it involves coinshit again
How-To Document: The Documentation System
Author here, I didn't bother submitting this to HN because I figured it would be too niche and trivial to get much attention. Evidently I was wrong!
I love that it is written in SQL, people keep forgeting it isn't only for queries.
Didn't known they moved from INRIA (National Institute for Research in Digital Science and Technology) to Dassault Systèmes
Huge models are the best type to open source.

You get all the benefits of academics and open source folks pushing your model forward, and a vastly improved hiring pool.

But it doesn't stop you launching a commercial offering, because 99.99% of the world's population doesn't have 48GB+ of VRAM.
Having been forced to write queries as JSON in elastic I definitely prefer writing SQL. I would actively avoid utilizing any query language where I have to count brackets.
The issue described by the article is only due to the digital signatures occurring in a TLS handshake, not due to the subsequent (symmetric) encryption of the connection (AES-GCM), which as the article explains is already considered quantum safe.

That aside, digital signatures are implemented in terms of asymmetric encryption (with the roles of private and public key reversed), so the quantum safety of asymmetric encryption and of digital signatures, as well as their possible size issues, are really one and the same.
If six months of daily meetings did not lead anywhere then cancel those meetings.
I'm confused which part of this is so off-putting.

Joe is always the one in every standup saying the thing he's working isn't done yet because he's wrestling "one last tough bug." As a manager, you wonder if the technical problems are really that tough or if Joe is just struggling. Let's look at the commit history... yeah, something is off here, Joe has 1/10th the commits of his peers and they really don't seem more complex in any way, but look rather trivial. Time to talk to Joe and look at these commits together and see what's going on.

Is that really such a troubling proposition?
GPL or any OSS license doesn't require you to accept contributions. Your users are free to do anything with it except distribute derviative software under a different license, but you, the author, don't owe them anything except buildable and runnable (since v3) source code.
I think that's exactly what Google's ex-CEO said years ago:

> If you have something that you don’t want anyone to know, maybe you shouldn’t be doing it in the first place

which you can read either as a terrible "nothing to hide nothing to fear" comment or as a good warning about the factual state of things.
It's not a "free 2% cut in salaries", it apply to everything else. If there is 2% inflation the company will have to pay everything more and will have probably have to negotiate to get higher price from its client too or it will not get its 2% more revenue to compensate the increase of everything.

Additionally, usually workers have too take debts too buy their house. If there is a little inflation and the salaries are following inflation the debts becomes comparatively lower every year.

It's not just against workers. There are upsides and downsides for everybody.
No need to base64 everything if you can just escape the new lines. Or you can use https://github.com/luciopaiva/binary-sse
Sure. My point was that most employees think that VCs take 80+%, and especially the first few employees usually have no idea just how little equity they have compared to the founders.
Due to a serious of steps where Copland failed to deliver, Gasse wanting too much money, NeXT being acquired into what turned out to be a reverse acquisition.
Seconding the Mox recommendation, it's pretty good and enforces good separation of concerns in your application. It was created by José himself, so you know it's got a well-designed API. You just need to get used with using behaviours, and using the Application config to tell your code when to use the mock vs the real thing.

I use it to separate and test external API calls (i.e. to test the payment layer without making any request), to maintain separation between my code and an external library I might want to swap out at a later date, or even between various components of the application. Then writing unit tests becomes a breeze, and you don't need many integration tests.

https://hexdocs.pm/mox/Mox.html
That film is disturbing for adults, let alone kids. The cut to the girl screaming is terrifying.
https://en.wikipedia.org/wiki/Emad_Mostaque

that wikipedia page screams "grifter", wow
It really blows my mind that this would even been considered acceptable in a civilized society… the fundamental right to privacy should be inalienable. When are we as a people going to say “enough is enough”?
Port-scanning the fleet and trying to put out fires
Why European VC Is Outperforming the US
> I really hope somebody sues

The EU is unfortunately not the US.

Suing governments there, much less the EU govt itself is not really something that is "done".
Same nonsense at Convergent in the early days. Jim Frandeen worked on tightening up the OS, saved like 10% memory footprint. Likewise, a negative code count. That manager actually quit.

My own experience was changing a 10K line module with a template in one page. Put some angle-brackets in about 100 references which left a net -9900 LOC
The Laughter of Wolves
Your gradient descent is an operation on a directed acyclic graph. The graph itself is stateless. You can do parts of the graph without needing to have access to the entire graph, particularly for transformers. In fact this is already done today for training and inference of large models. The transfer bottleneck is for currently used model sizes and architectures. There's nothing to stop you from building a model so complex that compute itself becomes the bottleneck rather than data transfer. Except its ultimate usability of course, as I already mentioned.
Indeed, first of all Apple might not be around any longer, without the reverse acquisition played by Jobs, who knows how well BeOS inspired Mac OS would turn out.

There would be no iPod taking Apple out of red zone.

There wouldn't be FOSS devs flocking into Apple hardware as replacement to sponsor Linux OEMs instead.

And it would be yet another C++ focused desktop operating system, assuming Apple would survive the transition in this alternative reality.
"CSS framework" is just a fancy way of saying "CSS library".
Yes, but I'm guessing your commit history over the last year is not just 1/2-liners once a month, right?
Branding is important but it's not Coca-Cola and we are not normal customers of something. I believe that in the end who wins is who provides technical excellence and a license that works for the use case. The reality is that most of the times nobody wants to put substantial work into OSS projects for free (I understand the reasons), and I don't agree with this post when Andy says that projects can be set in maintenance mode just doing minimal work to take them frozen, even when they are mature projects.

Moreover the current situation with Redis is not closed-but-maintained VS forks-possibily-without-development-force, because the SSPL is a quite open license. To put our destiny in the hand of what OSI approves or not is crazy IMHO. Actually for OSS to be viable in the future, we likely need many other licenses based on copyleft, that allows new projects developers to say, OK, I can use an open license because I have some protection from megacorps. Don't get fooled by a minority of strong voices, if you check Hacker News comments about Redis licese change, you will see that at this point many, many folks get that.

Stallman was now almost erased from collective memory but with GPL what happened was exactly what was happening now with SSPL. Initially copyleft was used, and later stronger copyleft was used in successive versions / modifications of the license, like AGPL. So this problem is not new and people a the core of the Free Software movement addressed them in a very similar way decades ago. But now suddenly if a small company goes along the same lines, that is a violation of everything, while big companies like Amazon posing a major threat to future of OSS is fine.
I doubt it.

The author makes a good point. Microsoft's Windows, having reduced the competition to ~3% market share, was pretty d*mn obviously a monopoly. Vs. competitors to Apple's iPhone still have ~36% of the U.S. and ~77% of the global market. (And with current political currents in China, the latter number may be headed for an upswing.)

However sincere the feelings of Apple-haters (or Apple-dominance-haters, or Apple-tactics-haters, or Apple-30%-cut-haters, or Apple-arbitrary-decisions-haters, ...), and however many good points they make - the actual legal case here relies on convincing a rather cold-hearted and skeptical old judge that Apple has a monopoly.
Why AI growth will lead to inequality
https://en.wikipedia.org/wiki/Emad_Mostaque

Read his Wikipedia page and tell me he doesn’t sound like your run of the mill crypto scammer.

> He claims that he holds B.A. and M.A. degrees in mathematics and computer science from the University of Oxford.[7][8] However, according to him, he did not attend his graduation ceremony to receive his degrees, and therefore, he does not technically possess a BA or an MA.[7]
Also at a given point, they were actually trying to compete into the UNIX workstation market, as a couple of Amiga engineering folks were really into UNIX.

Thankfully that never materialized as such, otherwise AmigaOS wouldn't turned out as special as it was, rather yet another clone, SGI style.
>>In the current environment, cost inflation is not a problem anymore.

Everyone person who lives paycheck to paycheck, and is barely keeping their head above water as the cost of everything continues to skyrocket disagrees with you.

Good luck telling them that "cost inflation is not a problem anymore".

I can't speak to how things are in Denmark, but without a doubt the situation for young people (especially those looking to rent or buy a house ) HAS changed dramatically for the worse in the USA.
Another factor might be that, due to visa restrictions, many great European entrepreneurs have decided no to move to the US.
The vast majority of the "open ecosystem" does a fine job funding open-source developers:

- In surveys, the vast majority of Linux maintainers are paid

- Both I, and many other people I know, have spent most of their adult careers being paid to do open-source

I have no problem with developers who "choose to put food on the table over being part of their social club." I have a serious problem with developers who pull a bait-and-switch, and:

- get support from the open ecosystem to build out market share and technology; and promptly

- pull a bait-and-switch, and try to milk their supporters for $$$

I think the point Redis is missing is that SaaS relies on **trust**. SaaS is almost always a better deal in the short-term, but once you're wedded to a vendor, you're relying on them to not extort you or hurt you. A SaaS vendor can potentially:

- discontinue a product with zero days notice

- totally ignore security, leading to all your data landing online

- raise prices 10x overnight, leaving you in an impossible situation

- "pivot" in all sorts of other ways which disappear your business

A major reason for doing things yourself is business continuity and risk management. Once a vendor has done something like this, it's a good sign they'll do it again. After a vendor pulls a trick like this, I wouldn't consider relying on them even for proprietary work I do.

(Footnote: This is also why I would never use Google's cloud or Oracle's cloud; there's a track record of business-killing moves).
I understand your frustration. Folks will tend to respond confidently in ways that align with their beliefs, often without reading the source or consulting any external material. They'll just say whatever. And those are the hard-working ones. Lazy disagreement just arrives as downvotes.

One way I've found to mitigate this is citing specific quotes and sources (that they should be aware of already if commenting), which often mitigates this effect, but commenting is nevertheless fraught. It basically amounts to defensive writing a lot of the time.

I keep coming back because I do think there are a bunch of us who do read, have expertise, and are here because we're curious and want to learn from others. But wading through the noise comes with that, sadly.
A backend service runs requests, and that backend service can use proxies
Doesn't it say it right there in the first paragraph?

> And anonymous payments in cryptocurrencies to wallets operated by providers (hosted wallets) will be prohibited even for minimum amounts without a threshold.

Doesn't this mean that literally all anonymous crypto transactions would be banned?
If you're OOTL on Google Gemini ML-based content creator then https://blog.google/products/gemini/gemini-image-generation-... is a pretty good summary.

Ostensibly it appeared to be tuned to be racist.

Maybe Google encourages people to speak up but also has a culture of racism?
It's not really one thing it's that it takes time and immense resources to put planes/engines through the engineering process and get certified. The 737 Max, took something like a year from conception to beginning of certification, another 3 years for the first prototype, 2 more years to get certified and go into production. 6 years total an that was:

1. Only a plane modification, not a brand new plane in a novel space,
2. Being designed and built by an organization 100x the size that lives in that space.
3. Was not also hinging on designing brand new engines.

On the technical side, engines are very difficult to get right. You are often operating at or beyond material temperature limits, relying on complex analysis that take years to perform and then years to validate with actual testing, and then pushing parts to fatigue limits in service.
Name calling is rarely useful. It certainly is not in this case, in addition to be patently false.
With the exception of engineers whose role is strictly advisory, architectural, etc, for most engineers the direct literal expression of their work is the code that they commit. Not the design document, not the ideas in their head, but the code in the repo. Managers should be looking at this code in their evaluation of everyone's work. Someone with an unusually-small amount of code shouldn't be "punished" but it is something that should be noticed and examined.
Really no wonder he ended up in “decentralized AI” aka crypto grifting. It must be like returning home after a long day.
It would have been yet another UNIX clone like SGI, without the features that make AmigaOS special in first place.

NeXTSTEP was great, because their UNIX support was a means to bring software into the platform, and have a checkmark for DoD deals, not the way to develop NeXTSTEP applications.
Huh. Just these days I’m building an MVP and was thinking that denormalized would probably be better. But I just can’t give normalization up.
It was a project without clear funding in INRIA, and an investor (who had previously been Airbus CEO iirc) created Scilab Enterprise and hired the engineers who'd been developing it. This helped pay the bills and get focused on reworking the software stack. They were providing paid support but that wasn't enough, so there was a series of acquisitions until, apparently, 3ds.

Source: interned there sometime along the way, met some great people.
Doing quick search, there is also interactions between Vasopressin and salt and blood pressure. Could ASD be helped by reducing salt? or increasing salt?

I'm not knowledgeable enough to untangle all of the studies where these terms are also used, which I guess is part of the problem this paper is pointing out, that the terminology/naming is confusing.

Is this saying if you have blood pressure problems you might also be at risk of ASD.

Or opposite, if you have ASD, you might have more risk of blood pressure problems.

"The name AVP refers to the hormone’s role in
increasing vascular resistance and regulating blood pressure (via
AVP receptor"

"Given the emerging evidence for central AVP signaling abnormalities
in ASD, we would expect individuals with ASD, or a subgroup of them,
to be at increased risk of AVP-related medical conditions and
symptoms. "
It was a little difficult to wrap my head around at first, but for me its main benefit is this:

In many static site generators, if there is a page in a collection of pages (say, a product page) that you want to add a custom layout to (but without affecting other pages in that collection), you often need to create a separate template, or modify the default template to allow for this exception. With Soupault, page content is typically written in HTML and giving a specific page a custom layout is as simple as including an <html> element in that page’s content file and it will be treated as a completely standalone page. In other words, a content file is not as different from a template as in typical static site generators.

This flexibility and HTML-first approach cuts down on complex or sprawling templates introduced to deal with many exceptions. And as a result, someone only needs to know HTML to make most edits to a website. Of course, you can make certain patterns more efficient with “widgets” (basically snippets to insert content dynamically) defined in the main configuration file, but it is not requisite.

At the end of the day, the website is mostly just HTML with a simple project directory structure, which makes it understandable to a wider audience, which is important to me since I want the website to be easily understandable for future maintainers of it.

Edit: Another benefit is that Soupault is a single statically-linked executable with no dependencies, and therefore can be downloaded via a simple link. This also extends the longevity of websites built with it (i.e. it is easy to get the development environment setup).
Thanks to Starlink, planes should have good internet soon.