skysight-inc/HackerNews huggingface dataset:
Thanks for writing this, I've been complaining and trying to get attention on this problem for somewhere close to a year and I feel like with so much of the completely uncritical coverage of passkeys I was disconnected from reality or something.

Portability is a huge issue for passkeys and the lack of communication about it as well as the lack of prioritization is holding passkeys back.

----

A few weeks ago there was a virtual tech summit for the FIDO alliance which had a tech-talk on the state of portability: https://www.youtube.com/watch?v=Mje6J2IMRTY

It is from what I can tell the only resource going over plans for portability to this level of detail. I'm hugely grateful to the presenters who even went out of their way to answer a few of my questions when I emailed them -- seriously, thank you.

But it's frustrating to have questions about portability years after passkeys became a thing and to have a 30 minute video be the best resource online for learning more. Hopefully that will change in the future, my understanding is that a rough draft spec is coming soon. But the process up until this point has been frustratingly vague and impossible to follow from the outside, and I'm still left asking why portability wasn't considered a pre-condition to launching passkeys and advertising them to ordinary users for regular usage.

I'm hoping things get better once the draft spec is released, I want to be wrong about passkeys. I want them to be something I can support and advocate for. It's because passkeys have so much potential that it's frustrating seeing them fall over in this way, and it's frustrating to see trends that make me feel like the entire standard is being developed mostly by companies without the kind of serious input from user-advocates or transparency about spec process that is necessary for a full password replacement.
It's a shame this isn't P650, which has the Hypervisor extension amongst other things (https://www.sifive.com/cores/performance-p650-670).
Building the network module took about a month, but writing the compiler took much more time.
Can you give a source that backs up your claim that the banned person here has shared any kind of hate.
Shorts plague the search. Short clips are always completely irrelevant to anything I can possibly be looking for, while not entirely insane, anyway.
Especially true if you are going to be touching prod. Part of being a junior I think is hearing a few horror stories, hopefully enough to make you stop and think before pressing enter on that rm command.
> While MinIO's setup is complex, SeaweedFS's setup is much simpler.

Are you sure you are not talking in reverse?

I find Minio single binary deployment very easy, and you also complained about SeaweedFS's complexity in the previous paragraph.
Super impresssive! I would absolutely love to work on such projects and admire the passion and countless hours that went into understanding and then building the system.

Retirement is not something desirable for me, so maybe that's when I'll spend my time on hardware and software projects like this.
With the goal of showing nice, clear images to as many devices as possible, while optimizing the file size, I would:

1. decide if I want to use any of the newer image formats. If so, each needs its own `<source type=''>` in a `<picture>` element, front-loading the most efficient formats.
2. decide if I want to serve different densities for the image.

For specifying densities, width descriptors + `sizes` attribute will always compute to a more useful effective density than density descriptors, if you can get `sizes` in the ballpark of how the image is actually laid out.

For lazily-loaded images, `sizes=auto` will do that for you, when it becomes universally supported.
> "A separate thread featured a “WTF moment” in which the owner said his Cybertruck’s auto-pilot feature seemingly malfunctioned as another truck approached in the other lane while both were driving on a highway."

Sounds like the Software had an identity crash when it saw itself. /s

But seriously, with that title I was expecting a more factual summary of this "astounding rate", not a collection of random posts from some forums.

But yeah, it's the NY Post...
> All hope and naive solutions.

Funny, but quite true.
I remember playing OPUS files at 16 KBPS over a... 2G? connection with mplayer's caching options. The audio sounded a bit better than MP3@32 or Real Audio back in the day.

As the music was "avant gardé", it almost fitted the genre.
An important fact that I only recently learned about this vulnerability is that the change that introduced it was not some rushed act: the maintainer raised the problem they were seeing on the OpenSSL mailing list, proposed a change to fix the problem with a request for feedback, and got some (including from upstream).

The result was a terrible vulnerability, but it seems more of a case of spectacularly bad luck of everyone not spotting the issue.
Interesting to see the credits of Sky Travel at the end and having an item "pagetable.com" which is currently a C64 dedicated page. It must be one of the longest running pages on the internet...
Electric motors do get warm during operation, it is no surprise that some form of cooling fluid is desirable as the weight/power horizons are explored across the EV fleet.

This article doesn't touch on battery pack cooling, which is also a thing and much like motor cooling in that manufacturers want one coolant for the life of the product.
Near ir LEDs are also cheap and easy to power, with its what's in remote controls. Low pressure sodium lights aren't. I remember using them in postgrad labs and it wasn't fun.

Alternatively you could use a solid state laser or narrow band LEDs if you need the band to isolate to be in the visible spectrum too.
Just because you could apply a different meaning to a character doesn't change the fact that some meaning, once learned, is more helpful than only relying on physical positions.

Combining meaning with a physical position is even more superior than purely relying on one approach.

And to me, it was far easier to switch layout while relying on mnemonics than on key position, and this continues to be true even when I add new keybindings now when I switch between multiple layouts. Maybe other brains works differently though.
Or mass surveillance.
We don't know if he played games. Some person declared that he did. There is a way to collect evidence from phones and it's not "let's find an apple engineer who will make a deposition." In fact, if he really played games Tesla would make sure that it can be submitted as evidence in this court so it's more likely he did not.
Kinda related, I was exploring how much complexity you really need with https://qoaformat.org/ - compresses at 278 kbits/s, but is much simpler than even MP2.
The paradigm shift that's going to come with distributed SQLite isn't to the edge, it's going to be to users devices. I believe the DX of building Local-first apps is going to hit the criticality point in the next year or so and its popularity is going to explode.

With dynamic partial replication you can synchronise a subset of your database to a SQLite db on your users device, eliminating the network from the ui interaction loop. Then with the emerging eventually constant syncing systems, many using CRDTs, it's possible to have conflict free eventual consistency. Just read and write to a local database and it will sync with your central server or other clients in the background, both in realtime or after working offline.

I work on one such system at ElectricSQL, but there are many people building variants of this such as Evolu, SQLsync, CR-SQLite, and PowerSync.

That's all not to say SQLite on the edge isn't really damn cool!
The Wikipedia article has a reference to where the quote came from. It’s a podcast, whose audio presumably has not been transcribed and indexed.

https://lexfridman.com/john-carmack/
You seem to be reacting to your own assumption that the original response was making an assumption.

I understood it instead to be generalizing to a related concept, and inferred no condescension, FWIW.
And here I am still wanting a damn widget I can put my Android which will "find my phone" my wife's phone, and vice versa without her needing to log into her google account.
Imagine that the USA and Europe decide to avoid using data available on the Internet that doesn't fully comply with the usage policies of the data providers. This scenario raises significant questions about the future of artificial intelligence (AI) development on a global scale.

If the USA and Europe take this route, what happens next? It's conceivable that China might not follow suit, opting instead to leverage all available online data to boost its AI development. This could lead to a scenario where China manages to develop a super AI, while Europe and the USA get caught in a complex maze of licenses and expensive, specialized micro-AIs.

Faced with an advanced and accessible Chinese AI, what will users around the world do? It's plausible that despite initial concerns, many will end up using the Chinese AI, thereby giving it even more power, data, and growth capacity.

This brings us to the importance of balanced regulation. The European Union, for instance, is often viewed as having hindered innovation with excessive regulations over the past decade. If the USA were to follow this path, they might risk limiting their own capacity for innovation.

Excessive regulation thus emerges as a double-edged sword: on one hand, it aims to protect privacy and user rights; on the other hand, it risks stifling innovation and making one's companies and technologies less competitive globally. In this scenario, the question becomes: How can the USA and Europe balance data protection needs with the necessity to remain competitive in the global AI arena?

Moreover, this discussion isn't just about licensing MP3s; it's about managing common knowledge—that which is accessible to everyone, including competitors in different jurisdictions—for the creation of an industrial revolution. Before clamping down with regulations, careful consideration is needed. Licensing mechanisms can be introduced later if necessary, but they should not provide an undue advantage to competitors. Balance is essential.
Continuing to this day, legacy news still validate Elon's criticism, ultimately leading to their own downfall.
Matlab is one language that chooses the second. Every assignment a=b where b is a matrix creates a distinct copy of the matrix.

The interpreter is slightly more clever and instead implements this as a copy-on-writr mechanism, but that's just an implementation detail .
Also I added EnCodec, but wasn't able to get the prereqs working for lyra2.
Ha what a coincidence, I live in NL too :P

re: spinnach: I'm sure you could substitute it with just about anything really. You barely even taste it in the finished product. It mostly provides bulk and texture.
In that case what would you expect the following to return?

a = []
b = [a]*4
a.append(1)
print(b)

I mean it is possible to change Python and make [...]*n a shorthand for "repeat this statement n times" but that would be odd on its own.

Lists pass by reference, tuples pass by value, if you want to understand Python you're just going to have to get used to that distinction. There are other options, but most are worse.
> Why are you comparing functions/closures with values?

I'm not. The fun _ -> [] is needed because the argument is the element's index. That's just what List.init happens to expect, a function that takes an index and initializes the element, but the index is not needed here.
Yeah, "the only shortcuts" worse are the most used ones!

And overuse argument isn't enough to even move them (it's an argument to maybe move word-based movements to the home row instead of them, but not to just move them out), let alone split them!

Your layout isn't relevant when talking about Colemak, it's trivial to make Vim way better even on qwerty since the defaults are very bad, so of course there are layouts where these letters magically appear in more ergonomic position, the argument is that it makes no sense to make it worse just to stick to the labels
so, a perfect object to base a precise measurement on, with "a pinch of salt"
It was rhetorical. But in case you actually don't know: what you described (i.e. multi sampling) has been common practice in ML for ages. Only now the latest models are getting so big that people are actually trying hard to move away from this idea because it would take a human lifetime in wall clock time to train a cutting edge LLM on similar datastreams.
> With good tests

> I work in a place with 99% test coverage requirements

Sounds like your problem is bad tests. In fact, I guarantee they’re bad tests because that’s exactly what coverage requirements lead to
One way to answer this question is to look at the software produced when clock speeds were 20x slower.

The limitations, and features we had then are a minimum starting point.

So I'm thinking around the era of a 486 100mhz machine. We'd have at least that (think mylti-player Doom and Quake era as a starting point.)

We had Windows, preemptive multi threading, networks, internet, large hard drives, pretty much the base bones of today.

Of course cpu-intensive things would be constrained. Voice recognition. CGI. But we'd have a lot more cores, and likely more multi-thread approaches to programming in general.
I understand currying to be using a closure to "bake in" a value for a parameter.

Reading through these comments, it's clear that currying isn't clearly understood, which makes me doubt it's worth the cognitive load to use in a codebase.
Look nice! I like how you use the scope to remove the animation, this is very convenient.
What is this? a high concept "u mad bro"?

I fail to see how my feelings are relevant to the discussion.
impressive work! a lot of it went over my head but still i could appreciate it being a real feat
> In more sane languages, the expression [] means give me an empty list value, nothing more and nothing less. So then whatever the syntax for [[]]*4 is in such sane languages, it gives you four empty list values.

I don't buy this. Either the syntax to give you four empty list values is some kind of comprehension, which Python has and does exactly what you like, or it must have lazy evaluation somehow. Otherwise, how can the language know you don't want to copy the existing reference but create a new empty list? If [[]]*4 were to create new list on the fly, then `[print('hello')]*4` would have to print hello 4 times, i.e., the print statement is lazily executed, which does not fit into Python at all.
1k18
Settings > Google > Find My Device > Use Find My Device > Off.

Alternatively, don't use an Android phone with Google Play Services.
> If you say it’s the second (I can’t think of any language that does), then `a = […]; b = a` is an expensive copy by value assignment

In Swift collections are value types, so b = a conceptually is a copy. It’s not expensive, though, because Swift does copy-on-write.

You pay for that by a combination of having more expensive collection updates (they, at least conceptually, have to check whether to make that copy) and a more complex compiler (it tries to avoid having to actually do those checks at runtime)

var a: [Int]=[]
var b = [a,a,a,a]
b[0].append(1)
print(b)

will produce

[[1],[],[],[]]
To me it's just about what was taught in schools to me, and what I can find on my own. If you Wikipedia Estonia, it says right in the opening paragraph that it is Northern Europe. It's also what was taught to me in schools. Admittedly, being born in '92, I am a first-generation free Estonian and never experienced the soviet union so I don't have any strong feelings of East or the color red, but it is true that Eastern Europe is often talked with the vain of ex-soviet block countries that are corrupt and stuck in time, which is simply not the case with Estonia and I feel just minimizes the work we've done since.
Doesn't seem to be a problem, the Alstom Movia which is running for BART is an off-the-shelf platform for light rail[1].

[1]: https://en.wikipedia.org/wiki/Alstom_Movia
Yes. There aren't two root systems identical. I assume that this plants were cultured in a sandy or hydroponic mix.

But the main goal is the generalization and to know how long roots can grow. For trees they wanted to know also if roots can grow up the hill against gravity (they do it all the time). This is useful to understand how stable is the structure and how useful to fix soil in place and fix erosion processes.

The dune melon root is particularly funny. You can almost hear the root sniffing water right and left in the Namibian desert
I guess some people like this kind of videos, personally I can't stand it. Flashing subtitles that just look like an interference. I want to watch the video, not the damn subtitles. At a bare minimum, they should be optional!
if you compare

> a = [0]

and

> b = [0]

these two expressions produces different 'value' objects for `[0]`, and modifying `a.append(a[-1] + 1)` does not change b.

so it's unintuitive that using `[0]` as a default value in a function argument can cause that argument to retain the same value across multiple function calls, when programmers would assume the argument to a function is not the same across multiple invocations.

The issue really here is the usage of an array object, which is not a value object (immutable), but a reference object. It would not have been a problem if the default argument was a string, or a number.

This is a reason not to use arrays in default arguments.
Show HN: Nxs-backup – an open-sourced backup tool for GNU/Linux distributions
Hey HN! We wanted to introduce you to our nxs-backup and share the new version of it with you!
The reason behind the idea of creating our own tool when there’s already multiple backup software is simple - at some points none of them were able to do things that our projects required.

Previously, we started developing our tool in Python. As the number of projects in which we use the tool increased, the demands for its functionality increased too. So last year we completely rewrote our project in Golang and made many changes to meet the new requirements. The main requests for nxs-backup were:

- Backup data from the most frequently used software (files, MySQL, PostgreSQL, MongoDB, Redis); and store backups in remote storages (S3, FTP, SSH, SMB, NFS, WebDAV);
- To have a single configuration file that will allow you to manage backups centrally;
- Possibility to expand functionality through custom scripts;

And now, a year later, our tool is able to:

- Implement the corresponding interfaces of all storage facilities and all types of backups. Jobs and storages are initialized at the start, and not while the work is running;
- Work with remote storages via API. For this we use various libraries;
- Use environment variables in configs, thanks to the go-nxs-appctx mini-application framework that we use in our projects;
- Send log events via hooks. You can configure different levels and receive only errors or events of the desired level;
- Specify not only the period of time for backup, but also a specific number of backups;

You can check the other features of nxs-backup on GitHub: https://github.com/nixys/nxs-backup

We’re really looking forward to improving our tool so we’d love to see any feedback, contributions or report any issues you encounter!
What other opportunities for development do you see? What features would you add? Please join our chat in telegram: https://t.me/nxs_backup And you can discuss something about this repo or ask any questions in the chat: https://t.me/nxs_backup_chat
All of this makes me think we'll just be building meteor apps but with sqlite instead of mongo and minimongo whaha
Commonhaus Foundation: open-source innovation, collaboration, and sustainability
> , if you want to understand Python you're just going to have to get used to that distinction

My argument is that that distinction isn't needed, by default, in a high-level language, and that plenty of people get it wrong, understandably. It is simply complexity that is not needed.

These simple examples can be toyed with, but sooner or later one is going to want to solve real problems, and unintuitive, default behavior doesn't help with that. Python's mode of operation tends to favor implicit over explicit. And the syntax [...]*n is implicit.
“To Varoufakis, every time you post on X, formerly Twitter, you’re essentially toiling Elon Musk’s estate like a medieval serf. Musk doesn't pay you. But your free labor pays him, in a sense, by increasing the value of his company.”

This sounds disanalogous to me. When you post on twitter, you can be rewarded with engagement and attention and even the possibility of growing your own brand and following. All at no monetary cost to you. Meanwhile, twitter has the costs of paying for servers and infrastructure and salaries of those required to support the site
I did appeal (the error message informs you you can), but do I want to use an LLM that might randomly ban me?
I think too. But I want to check and to quantify.

It is also about improving human speech too, what can we do to match AI performance ?
I think, that are some very interesting questions that it may helps to answer.

How can we make AI even better at « brainwashing » ? Does the value of information matter ? I mean is it easier to AI to « nullifies conspiracy beliefs » or to « nullifies scientific ones » ? We may have opinions on these issues, but the scientific reality behind them is not obvious. It's so exciting !
The Caltrain KISSes are not really off the shelf, in many ways, good and bad and ugly.

The (arguably) good: 1) they have a boxier profile than the standard KISS, which some have complained about, but the reason the European version is less boxy is because Europe has a more restrictive loading gauge (the allowable cross-section of the vehicle), resulting in a more cramped upper level. Caltrain doesn’t have this issue, and so the upper level will not be cramped. 2) The Caltrain KISS is more powerful than the standard, which would allow for a faster top speed… if the corridor was upgraded to make use of it, which it is not. Maybe someday.

The bad/silly: two sets of doors… a higher set since HSR might allegedly someday come to this corridor and require changing the platform height, and a lower set because that ain’t happening for a long time, if ever. I think there are some other bad/silly things which I’ve willfully forgotten about (I think they fucked up the ADA lifts somehow?), which I’m sure are documented somewhere on Clem Tillier’s excellent blog.[0]

The ugly: “buy America” requirements forced Stadler to build an entire factory in the US, raising the cost by over 50% compared to the standard KISS. This is the bad kind of industrial policy which raises costs without actually building up US industrial capacity in this field (if Stadler closed the plant tomorrow, the US wouldn’t retain any expertise or capacity to build trains).

[0] https://caltrain-hsr.blogspot.com
When you mean strength, what are you referring to?
Could very well be because of the popularity of coffee in Japan, as it's seen trendier than the old fashioned tea, which alao tends to take extra care and time to brew.

S. Koreans also tend to drink coffee way more than tea, but this might have to do with the extreme poverty coming out of korean war, and coffee being less expensive.
Very few job markets in Canada are burning hot right now.

Canada's GDP is like 50% housing (real estate and renting)
Tea shops in Taiwan mostly sell bubble/boba tea, which is drenched in syrup and artificial flavors and the actual leaves themselves are an afterthought at best. The latest wave of higher-end places like Chicha San Chen are placing the focus back on good quality tea and proper brewing, but these are still a minority and it's still far, far away from the austere world of Japanese tea ceremony.

https://chichasanchennorcal.com/