skysight-inc/HackerNews huggingface dataset:
Thanks.

The problem is that he's fragmenting his efforts, it's like his effort capacity is 3 ants, and instead of telling all ants to pull the leaf in one direction, he tells each ant to pull in a different direction, so the leaf never moves.

Social networks are ALL about network effects. Split them up and they melt into obscurity. Combine them, they become untouchable.
100% true. It is only ego that makes people think we are "unique" and different to AI. If one plugs current AI into a body with external stimuli such as wishing to mate, eat, etc, then the external observer will not be able to spot a difference.

Our minds are in fact same statistical models with a gradually declining ability to learn and driven by exogenous irrational goals to eat and mate.
Another problem with lockless is that you can't turn every algorithm into a lockless one, it's actually only a handful of them that are practical to implement locklessly.

You can make every data structure lock-free, even wait-free, there are universal constructions [1]. The resulting performance may however be prohibitive.

[1] https://www.researchgate.net/publication/221343511_Impossibi...
You are totally right. Here's my rough personal guideline: prefer mutexes over lockfree code - unless you can't. For example, you cannot lock a mutex from the audio callback because it might put the thread to sleep and you would miss your deadline. (For anyone interested in this topic: http://www.rossbencina.com/code/real-time-audio-programming-...)
I got it by responding to content, not ad hominem nonsense, and occasionally making jokes. Some of the latter will not land, of course.
The classical techniques could do with an update here: https://www.theguardian.com/environment/2014/jun/08/the-dolp...
There is an argument that companies in mature sectors (like automobiles) advocate for increased regulation as a moat to keep competitors out since building a mechanism to comply is extremely expensive for new entrants.
There is an important change here compared to "classical" Windows, labeled taskbar item widths are now flexible. I really welcome this, others might not.
It's about their business model. If their business is to profit off of satisfying customers then they are going to be motivated to satisfy customers. If their business is to profit off of selling advertisements, then they're going to profit off of selling advertisements.
Define 'mainstream' ? The market for this thing is pretty limited.

And tongue controlled controllers aren't a novelty, they are used sometimes, but again - they are mostly one-time devices.
This isn't covered by the tweet but I found a whole bunch on TripAdvisor too:

https://www.google.com/search?q=%22as+an+ai+language+model%2...

Edit: Maybe not a whole bunch. Looks like just one or two repeated.
> in their later papers

Can you point out which ones? I thought I was pretty familiar with the Plan 9 papers but don't remember that part. Or maybe I just missed it?
Great idea.
With every technology advancement that could become mainstream like this one, we seem to get closer and closer to the brain.
By definition a "scalable" system AFAIK is a system which can handle more load (say 10x more, exact number is part of the design) without architecture change. Not always for this you need shared-nothing-horisontally-scalable system. If your code is fast, current load is low then you may handle 10x more load by running the same code in a VM with more CPU cores or even in the same VM/HW but having higher CPU utilization.
Isn't there evidence of animal dialect and "accents?" I wonder how this will address that.
You're right. Maybe, in a production environment, there should be the option to set an internal or corporate email address. Gmail was used only for demonstration purposes in my thesis, since it was originally developed and presented at my degree dissertation.
Show HN: Lakestream v0.0.2 – find files on S3 (or LocalFs)
Released v0.0.2 of Lakestream. It is (yet another, but hopefully better) file utility tool for object stores like S3.

The tool is by far not done. Although the List part seems to work fairly good. I am looking for good technical feedback or any other ideas/ suggestions.
> I just cancelled Spotify and got YouTube Premium and it was an absolutely brilliant decision.

What’s great about YouTube Music is that it includes user uploads, meaning that you get tracks (e.g. video game music) and versions/recordings of tracks (like old 12" versions and remixes, or live recordings) that you are unlikely to get on a purely commercially-sourced music service.
Possible change in business model, to become a merchant silicon vendor, e.g. in competition with Qualcomm? https://twitter.com/chiakokhua/status/1650114162310389767
The ideal is two or maybe even three standards. Having one means that upgrading to any new standard would never actually be possible.
I wasn’t arguing about control. If you actually read the arguments the gist of it is that shareholders are the only financial benefactors at companies, implying that employees don’t own any shares. I just reminded people who weren’t familiar with Silicon Valley that it isn’t true since stock is a big part of compensation for rank and file employees
The tongue muscle can be trained. This is also useful for at least one other activity.
> App review must consider developers to be potentially hostile.

And vice versa. ;-)
Nice observation. Algos do unlock some of that value. But long way to go. Cuz they need much more info about ppl.

For example, I know my younger cousins like certain topics that they cant get enough off, but if I see them busy with exams or homework I hold back on pointing it out.
It seems to be the same review appearing over and over
It depends on your usage. With 200 searches/workday (25/hour) - Kagi set as default search engine - I got following options:

- Stay at Professional - $10 + $49.5 query cost = $59.5 total (495% price increase)

- Use grandfathered - $10 + $37.5 query cost = $47.5 total (375% price increase)

- Use Ultimate plan - $25 + $0 query cost = $25 total (150% price increase)

With absolutely 0 guarantee ultimate plan will be ultimate. Would I pay for search engine 25$? Of course. Does Kagi delivers 25$ of search quality - no. As I mentioned I did metrics. 50% of the queries had to be moved to other search engines, so Kagi simply didn't deliver.
Generally agree, but I have had a couple of long term complaints which are seemingly never going to be fixed:

* There's no option to regulate how many times it recommends a video I have already watched. Ideally I'd like this to be arbitrarily close to zero.
* The recommendations are much, much, much too biased on recently watched videos.
Faster Than ChatGPT
chatbot like chatGPT. only a bit faster.
Natural language acquisition uses specialised circuitry in brain, and doesn't really run on general logic / intelligence, like programming languages do.

That's why analogies between the two are of limited use at best.

The rest of your comment isn't really wrong. I even agree with most of it. It's just not really relevant to your point.

> Learning multiple languages from a very early age seems to result in the languages being a single language from the perspective of the speaker, they have different situations in which they speak in different ways much like the average monolingual will speak more formally in a job interview compared to when they are out at the bar.

Last I checked the research was still open on that one. What you are saying might work as a gross simplification, though.

> Second and third, and etc languages are very different things between those that learned them from the start and those that learn them later in life.

Yes. And exactly when you learn them and in what context also seems to make some context.
I helped build a large message switch using something called QnX, which supported some very basic security mechanisms but it definitely wasn't bullet proof by any definition. The way we dealt with that was by treating the whole cluster much the same way that you would treat a single instance. If you had user access to any node it was assumed you had super user access to the whole cluster and all other security was handled at the physical and the application layers. Given that all of this was written in classic 'C' I don't doubt that there were many ways to exploit that system. But the niche application and the very limited way in which it was connected to the internet (it was mostly a replacement for a very large number of telexes) helped us to get away with it.
They do. I disable it always because it is annoying if you typo a command.
Sounds like you describe how aviation and other critical tech work. Every single piece has to be checked and validated by the administration, and yet planes keep flying.
searxng.org
In a word: yes, that's the essence of this system.
That is not how it works? People who know a lot are not in general slower then people who know only a little.
Uhmm, bad news for that concept... is that the economic value of something that's in overabundance is zero. AI will cause art, music, voice acting and so on... all to go into overabundance.

Economy is, as its name hints, about organizing the efficient distribution of scarce resources. We have lots of air, but no one is making a ton of money out of air, because no one is trying to buy some. They just breathe in.
There are some dimensions yes, but I do wonder if GC research is starting to approach the point of being "solved" well enough that we'll see a drop in investment. Not yet, clearly, but approaching that territory.

If you look at the very latest JVMs you have three GCs which a spread over throughput-optimized (parallel), a middle ground jack of all trades (g1), and latency-optimized (zgc). They're a lot more self configuring in the past, so no matter what needs your app has it's usually just one CLI switch to get something fairly optimal.

But ZGC is going generational, at which point it will have significantly higher throughput than before. Also, all the JVM GCs can handle massive heaps these days (like, terabyte scale). So at that point the choice might become even simpler: just use ZGC all the time unless you can tolerate higher pauses and want to reclaim some CPU for the app, in which case go with parallel. And in many cases the right tradeoff between latency and performance could be inferred automatically from the frameworks and libraries that are on the classpath, meaning that for most apps even needing to make that choice could go away.

If you have a GC that doesn't pause, can handle terabyte sized heaps, has great throughput, is largely or completely self-configuring, is portable, open source, supports dozens of languages and has clean code, there are really very few metrics left to optimize after that. It seems like HotSpot is nearly there, especially when combined with GraalVM for language support.
I suppose for the model indeed you should do that?

But then maybe not for the actual predictions made by the model, as the MIT license says:

> The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

Arguably e.g. a single function is not a substantial portion of a multi-file project—and, usually, even that function itself is not going to be a verbatim copy but adjusted to your use case regarding variable names etc.
> Similarly, utility-style government regulation often caps profits (or profit-like 'overhead' like salaries) as a percentage of expenditures. This creates an incentive for doing things in an expensive manner. It's kinda dumb, and has been understood as a problem driving excessive costs in regulated industries for many decades.

The term for this is "cost plus". As you note, it has long been understood to be a big mistake. And as you also note, it continues to be common.
Binary Lambda Calculus seems to spend its bits much more wisely than a Turing Machine encoding, working at a much higher level of abstraction. Defining and applying functions performs more useful work than moving a tape head around and jumping from state to state. The Turing Machine is also severely hampered by the pure sequential nature of the tape, where lambda calculus has access to all kinds of easily defined data structures.

> One strategy I'm thinking of for sufficiently large n would be to create a compression scheme for TMs

The universal variant https://oeis.org/A361211 of the lambda busy beaver can easily simulate any binary encoded TM with fixed overhead.
This sheds some light: https://news.ycombinator.com/item?id=30019307
I find it amazing for turning data into markdown tables (which are tedious to write by hand), for documentation.
Ages ago, I learned that our best receivers would not be able to detect our most powerful radio/TV broadcasts from more than half a lightyear away. I lack the knowledge to determine if that's true, but if it is, all those romantic notions of aliens learning about us from our radio/TV shows will sadly (or fortunately) never be true.

This article doesn't explicitly point out the distinction between broadcast (which taper off rapidly in power) and narrow beam signals (which lose far less power over distance), but it's pretty clear that it is largely about that distinction. It lists signals aimed at specific spacecraft that hit only a limited number of stars. That tighter beam hopefully means a significant signal will be detectable there.

It's cool that they calculate when the return signal might arrive here. It would have been even cooler if they'd calculated how strong the signal would be when it arrives at that star. But it's possible that's far too uncertain to determine; stars near the edge of the beam probably receive far less power than those in the center.
Fair point (this is the best counterargument in this thread so far), but do you have actual evidence of Google c level executives fucking over employee owned shares?
On the contrary the beneficial properties are popularly ascribed to bilingualism itself.

For example:

https://www.nytimes.com/2012/03/18/opinion/sunday/the-benefi...?

https://www.wsj.com/articles/does-being-bilingual-make-you-s...

Although it seems that skepticism about this truism goes back a few years as well.

https://journals.sagepub.com/doi/10.1177/0956797614557866
I once accidentally got my company's office blocked from w3.org automatically downloading the schemas for some XML documents.

What then happens is all requests to w3.org then redirect to a page explaining how anyone automatically downloading those schemas from those URLs became part of an accidental DDOS attack.
> Look, I recognise your username and I am well aware on your views on the matter. We've already clashed multiple times and there is really nothing to discuss when you insist on dismissing the idea that people who overwhelmingly voted for president elect in 2014 might not be happy with the fact that some mob had stolen their country.

Ah yes the country was stolen by the people such a novel idea, I understand you're mad because the Russian puppet got ousted for going against the people then ran away to his masters in Moscow.

But please keep telling me how the 'Ukrainian rebels' in Donetsk were using Russian air defence systems and then electing to put a former Russian FSB agent in as head of the military.

Totally sounds like a civil war right?.
Watch YouTube through Firefox on Android. You can install an effective adblocker too.
I've been working on a passkey-/WebAuth-first startup for the past months and I fully agree with most of the opinions for the slow adoption so far. From my experience, it's all comes down to two major obstacles: A) process / product flows and B) technical implementation.

A) Passkeys / WebAuthn require a completely different user behavior (compared to passwords which everyone is familiar with) and thus a lot of user education. Many product managers see the benefits with less friction, but are super cautious to introduce passkeys for existing systems, especially when users are not too tech-savvy (if you're building a new system for a technical audience, then things look different). Besides it's a huge product management effort to cover all cross-devices/-browser/-platform flows and all edge cases that are involved. Due to the device-boundness of passkeys and the different UI patterns on different device/browser/platform combinations, it gets quickly complicated. Besides you still have to support all your existing login methods: passwords, MFA, social login, SSO. So many product managers looked for larger companies to show best practices for passkey / WebAuthn flows, but so far there's just a handful of these companies, so product managers rather wait for broader adoption.

B) When talking to developers, many have heard of WebAuthn or the FIDO alliance, but integrating passkeys into your existing auth flow is not a 60 minutes task. You have to maintain your own WebAuthn server, deal with different forms of recovery and have to stitch everything together with the existing accounts & login methods. So far there's not many providers who offer easy WebAuthn / passkeys out-of-the-box and many like FusionAuth or Auth0 charge quite a lot for it. Moreover, passkeys / WebAuthn authentication is not anymore a backend-focused form of authentication, but a lot more frontend-loaded, as the UX plays quite an important role and the WebAuthn flow requires JavaScript to call the OS-native APIs. This makes things way more complex than just calling an email-password-auth endpoint. Besides, passkey implementations for native apps (Swift, Kotlin, Flutter) are very basic and good documentation for cross-device flows is lacking here as well.

Nevertheless, there's a lot in the work under the hood and I'm still bullish that things will look pretty different in the near future.
I grew up with video games and believed it would be a young people’s thing forever.

But now when I talk to young people, many of them don’t play or even know many games, and would rather just watch Netflix or YouTube.

However friends of my own age still play games.

So maybe video games isn’t actually a thing for young people, but simply a thing for people who were born in the 80-90s.

Just like rock’n’roll music. We used to think it was evergreen music for teens… But overtime realized it was simply for people born in the 40s-50s. And now it’s an old people’s thing.
I think the gripe is more directed at letting super inefficient code stand, because it's easy to scale it 10x.

Often there is no problem with the architecture either way. Just code which if it was faster, you wouldn't need scaling out just yet.
Berlin is not Germany.

Yes, every city and region is a bit different but Berlin as a whole has such a different culture, especially if you predominantly speak English.

Most of my colleagues are English speaking only and they sometimes complain that its hard to do certain things where I have no problem with it. Getting appointments, doctors and Bürgerbüro especially, they always seem to struggle with. You can certainly get by without or very little German in Berlin, but there are things that are significantly harder to do. I'd argue you're generally missing out on a lot of smaller aspects of the culture if you experience the English version of it.

Though I get its hard to learn German. Not an easy language and all the English in Berlin doesn't make it easier.
> "low-level control, not OOP, not C++".

Things have a drop-scope. There are hidden initializations. Boxing is required for many things including dynamic dispatch in error handling. The tendency to use FP-like one-liners. All that mixed with funny syntax that hurts C developers eyes.

A lot of "no-go" in C land (at least for me), that makes really hard to learn and to move definitely into Rust (again, at least for me)
I'm pretty sure everybody can do it wherever the average is. It's a matter of wanting to do it, that's all. Foreign workers come and pick up whatever host country language yet they're not always the brightest and also don't have exactly ideal conditions to do it. Like a sibling comment touched, you can go to Berlin and complain the language is difficult, talk English with Berliners happy to practice their English, and you'll come back learning almost nothing while they'll polish their English without even needing to travel outside Berlin. Because of choices. Learning something new is a challenge and like with every challenge, can be accepted or not.
> Another, non-algorithm related complaint is that it’s difficult to watch a channel from oldest to newest, that is, keeping track of up to where you’ve already watched within the channel’s history

Invidious with an account has been has been very useful for this. In the channel's pages, it shows what videos have been watched, up to which point.
Out of interest, how effective do you find challenging the chargebacks is in practice?

I always thought about automating this (or for lost delivery claims with shipping companies) but the numbers never worked out for it to be worth it because the success rate seemed like it would be so low.
Sounds like you should write a book!
Ah, yes! That was a mistype from me, I meant to echo the previous comment but lower the count.
Now that's a reasonable debate we can have!

Gains from increases in productivity in the last hundred years[0] seem to be spread between more consumption, shorter working hours[1].

Some people expected that most gains would go towards decreased working hours instead of the spread we have actually seen. Not sure there's much significance behind that?

[0] Or any span of time you might want to pick.

[1] And bigger bureaucratic overheads, but you can count that either as a weird form of consumption or as just productivity not having increased quite as fast.
I can't agree with you. I've done a lot of real time stuff and networking stuff as well as graphical user interfaces on a system that was based on the file metaphor and if anything it made things far easier. If only because you don't have to think about it, there is only the one way to do it.

Similar to how HTTP is just a transport protocol, it's what you transport and how that is interpreted that matters. By restricting the number and kind of endpoints that you allow a driver or virtual device to have you ensure that all tooling is instantly composable, which is a much bigger advantage than the ones that you get from 'more effective APIs', which always turn into a giant salad of RPC. Think protocols, not functions and you're well under way to seeing why there is a lot of power to be found there that we've thrown out in the name of a couple of percent of efficiency.
But competition within an apartment building car park will be limited - I'd assume there is only a single supplier today and it wouldn't be economically viable for a second supplier to build on top so it's a quasi-monopoly. If the building owners are alive to this then they would probably have negotiated a price cap of some form in the contract but I'd be surprised if theres any incentive to cut prices.
Would encourage DuckDuckGo people who are looking for a new option to consider Ecosia - it also uses the Bing API so it has good indexing coverage - but does a much better job of postprocessing the results.
Agreed: the dispositive factors are: "Is this true?" and "Could this truth help others?"

Given the other reports of Hsieh's erratic behavior, including with regard to health practices & psychoactive drugs, & the specific manner in which he ultimately died, it's very plausible he'd developed a fascination with death & self-harm.

And some people who do that also seek out others with similar fantasies, sometimes for mutual encouragement, aka, a 'death cult' or 'suicide pact'. Sad but true – and in my estimation, better to be aware of as a real possibility than reflexively deny as likely fabrication.
Soft real time, clusters. A bit like the same space that you would aim Erlang/Elixir at.
I would expect similar amount of data (or more) compared to usual visual inputs.

After all, your skin is a pretty big organ. And your sense of balance and proprioception in all the joints is quiet a few different channels and pretty high temporal resolution.