skysight-inc/HackerNews huggingface dataset:
OP doesn't actually identify what is problematic with the toasts! The `The Problems with the YouTube Toast` section merely describes what OP sees, not what is bothersome to OP. I'm guessing that the issue is all the different locations on the page where things happen: the control, the dialog, and the toast are all over the place, thus maybe that is distracting to OP. In that case the issue is about UI element placing, not really about the toasts.

Toasts help communicate that an operation completed asynchronously after giving control back to the user without making them wait in a modal dialog. This is a very good UI/UX, especially now that users are trained to understand that asynchrony.
He has a good TED talk on this from over a decade ago. https://www.ted.com/talks/richard_weller_could_the_sun_be_go...
The need for this sort of disappears if the thing being displayed (client) is actually coupled to the application state. Toasts are bad UX, yes. But the reason they exist is that we have one state on the server and then another pseudo-state on the client. Keeping them in sync via code locality in every component is extremely difficult.

So we come up with a workaround -- put async server updates in only one place in the application -- to get around this fundamental issue. In 99% of cases, this isn't about UX, it's about engineering. Nobody wants to put toasts in; they must, because managing state is too difficult otherwise.

It's a symptom of the larger issue.

If instead what's displayed on screen is simply the server's application state returned by the server, the user will always know what's happening with the server.

HATEOAS
FreeValve
I always wonder with these things if game anti-cheat software will flag you based on the hardware identifiers not matching known manufacturers of peripherals.
The sunlight is free. :-)
> Nvidia appears to be the only financial beneficiary

It depends how you look at it. A lot of the spend by big tech can be seen as protecting what they already have from disruption. Its not all about new product revenues it’s about keeping the revenue share in the markets they already have.
> SBC are not supposed to be used as a general purpose computer.

Funny sentiment on a site called "hacker" news. Use them for whatever you like, the more creative, the better.
another effect - collagen mixed with vitamin B polymerizes in UV, thus eyes and skin repairs for example.

The biggest issue is non-managing mismatch between your geographically evolved skin type and the Sun in the geography you're residing - thus white people living south get a lot of skin cancer while for example Somali immigrants in Minnesota and Sweden have widespread severe vitamin D deficiency (and associated issues)

Tangential - a pet theory of mine is that 40K years ago when magnetic field flipped, and there was short period (1K years or so) of highly increased UV it led to large number of early eyes issues in those large eyed (most probably the result of evolutionary adjustment to the more northern light) Neanderthals living in Europe - early damaged vision, cataracts, blindness - while Cro-Magnon's eyes with Cro-Magnon just coming out from Africa, faired much better with that northern, even temporarily increased, level of UV and thus the Cro-Magnon quickly replaced the Neanderthals.
it's implicit in this comment by kens though:

> if you buy a commercial-grade gyroscope for [us]$10, it will have a random walk error of several º/√h. So after summing the errors for an hour, you're left with several degrees of random error, which is bad. If you spend [us]$100,000 on a navigation-grade gyroscope, you'll get a random walk error < 0.002º/√h, which is much better.

if the slope was anything else, the unit of °/√h wouldn't make sense; it would have to be °/h or °/∛h or something. similarly for noise figures given in nanovolts/√Hz
Why does it only work for some videos?
I noticed a few weeks ago that when people said "subscribe" the subscribe button had a little light show that was kind of cool.

From a technical perspective I like the attention mechanism and that it's automated.
I hope I understand the question correctly. The markdown files are assumed to be in the same folder. The RSS file can be wherever. This is all handled using a configuration file.
roc is the language most rust nerds really want but don’t realise yet. functional, modern tooling, fast enough for almost everything (~ go / swift), and without the insane complexity and cognitive overhead of the borrow checker.

So excited to see it continue to thrive and grow.
There are 4 beneficial effects of sunlight I know of that have nothing to do with vitamin D.
This reminds me of the story of the Taiwanese radioactive homes, where 2000 homes were built with radioactive materials. There was a prediction that a lot of the inhabitants would die of cancer, and that didn't really happen.

https://www.todayifoundout.com/index.php/2020/12/the-curious...
> I also feel it makes you, the human programmer, lazy. We need to exercise our brains, not delegate too much to a dumb computer.

I kinda feel like this isn't talked about enough, my main concern right from the beginning was that new programmers would rely on it too much and never improve their own abilities.
https://docs.syncthing.net/users/relaying.html + https://docs.syncthing.net/users/strelaysrv.html
You just need to use the right tool for the job, you see. If jumping from a bridge is sufficient for this person, who are you to categorically disallow it?
You are of course right, but in practice I've seen many more incidents created by doing changes to make things more robust than from simpler incremental product changes that usually are feature flagged and so on. At deeper levels usually there's less ability to do such containment (or is too expensive or takes too long or people are lazy) and so many times I wonder if it's better to do the trade-off or just keep things simple and eat only the "simple" sources of downtime to fix.

For example the classic thing is to always have minimum of 3 or 5 nodes for every stateful system. But in some companies, 1 hour of planned downtime on Monday mornings at 7AM to 8AM for operations and upgrades (which you only use when you need) + eating the times when the machine actually dies, would be less downtime than all the times you'd go down because of problems related to the very thing that should make you more robust. An incident here because replication lag was too high, an incident there because the quorum keeping system ran out of space etc and you're probably already behind. And then we have kubernetes. At some point it does make sense, when you have enough people and complexity to deal with this properly, but usually we do it too early.
That adage only really applies to chemical toxicology.

It doesn't work on non-chemicals: UV, radiation, noise, heat/cold, pressure, physical trauma, repetitive motion, exertion, posture, etc.
> We produce a lot of open source

Got a link?
Ask HN: SaaS Pricing: Euros vs. US Dollars Currency?
I have a European SAAS and I wonder if users attach any importance to the currency available for payment.
At present, only euros are possible, but I wonder if we should add the possibility of paying in US Dollars.
Would you subscribe to a SaaS product if the price was in euros? Or would you rather have the price in U.S. dollars?
"Avoiding Sun as Dangerous as Smoking"

https://www.medscape.com/viewarticle/860805?form=fpf
In combinatorics we calculated that the typical wait time is very close to the actual planned interval.
No? It's a perfectly reasonable response. Imagine if we just accepted an answer without any sources. This article has a lack of proper sources, therefore it's hard to explain why
> Ignoring the computers is reasonable, but why ignore experts in well understood noncontroversial fields?

I would argue because there is no such thing. Human knowledge is ever changing, and experts have more incentives than just "convey the right information". Perhaps the most famous current example being masks at the beginning of COVID [1]. Why did the experts in the (up until that point, largely non-controversial) field of disease prevention tell people to not do the very obvious thing that they eventually told everyone to do? Either they were wrong, in which case one must ask how can they know when an expert is right; or the experts incentives were not in the direction of conveying the most correct answer to you, in which case one must ask how they can know if the expert is incentivized to help you or not.

Someone being an "expert" in their specific narrow field should absolutely bias you towards their opinion when seeking an answer but one must always be aware of what question the expert is actually answering. My GPS will happily tell me directions to my friend's house that requires a short 100 foot drive on a cut-through street. The problem is said cut-through is horribly maintained, with potholes deep enough to bottom out most cars, and blow tires if you manage to not bottom out. If one continues further up the road, and takes a switchback turn, they add about 1 minute to the drive time, which absolutely makes the cut-through route the objectively, expertly correct route ... if the answer you're seeking is "what is the shortest route, ignoring all other factors". And most of the time when I'm getting directions from the GPS, that happens to be the answer I want, and so listening to the expert is the correct move. But in this specific scenario, the shortest route is also likely to cause significant damage to my car. The expert does not know of other extenuating factors, and therefore can not give the actual correct answer to the real question which is "what is the best route"

[1]: https://www.latimes.com/science/story/2021-07-27/timeline-cd...
That comparison doesn’t fit the situation: Microsoft is liable for their LLMs just like they’re liable for their corporate vehicles. If their company cars crash into pedestrians they don’t get to say “oh, that just happens sometimes” and shrug it off.
In-browser Postgres sandbox with AI assistance
> $9 to $20 per seat seems pretty average in the grand scheme of SaaS price modelling.

"SaaS" is not a feature; you can’t compare products just based on the fact thay they are "SaaS". Gitlab for example brings me far more value than a tool to search my codebase; I wouldn’t put the same amount of money in both.
Hi thanks for this comment. I'll look into Atom a bit more for this tool. Heard a lot about it.
I think you're thinking about this slightly backwards. What else would you expect the browser to do, given a URL and no other context? Would it not ... prefer text/html? It's a hypertext browser, it prefers hypertext.

For many, many years, content negotiation was not adversarial, and there was little reason to believe it ever would be. Until it was, of course.

So how do we fix it, telling every page view we'd prefer if it were a JPEG? Probably not. Of course, you could make "Open Image in New Tab" do some magic to ensure that it acts like an image fetch: that sounds like a good idea.

> What non user-hostile things does it enable?

Content negotiation in general is pretty good. In theory, it lets a web server pick the best possible format that is supported by your client. For example, it would be possible for the server to transparently serve you a JPEG XL-compressed JPEG if your browser supports it, or fall back to the original (identical but larger) JPEG image if it does not.

Is there a good reason to prefer text/html? I know this will be unpopular but I believe that "upgrading" GIF links to WebMs in <video> tags is not user hostile in and of itself. GIF89a is a pretty antiquated format and LZW compression of 8bpc frame deltas is not exactly state of the art anymore; the difference between a GIF and a WebM of the same thing is usually multiple megabytes of bandwidth, and that can be extremely annoying, especially on mobile clients. Of course if you make it hard to access the original file, this will reasonably irritate people, but I think broadly the idea behind it is reasonable.

Being able to distinguish a navigation fetch from an <img> fetch is actually good because it would let the server behave in a more user-friendly fashion on the navigation fetch, for example by serving only formats that would be most likely to be useful to the user. Unfortunately, we can't have nice things, so it seems like some day content negotiation will have to be partly gimped.
Elon Musk is magical. Magically, he makes Tesla's PE ratio 10 times that of Toyota. It wasn't outrageous to think he could flip Twitter for more than he bought it. The problem with magic is the effects are unpredictable. You never know when it will stop working.
The fact is the true nature of humanity revolves around the concept of survival. Survival of the fittest. Having largely defeated and subjugated nature on this world, we are no longer in competition with the natural world. Rather, we are in competition with one another. The strong, be it physically or mentally, will always overpower the weak. Our role on this world is not to live in peace with one another, it is to conquer and conquest over our fellow man.

Anyone who disputes this is lying to themselves about the true and ruthless nature of humanity, and disrespects the mechanisms that have allowed themselves to exist and ask that very question.

This is your permission to do whatever you can get away with in the quest to amass as much of whatever is the current measurement of conquest. Be it money, fame, or power. It will never be enough, but that's not your place to ask why. Only how you will conquest.
Sort of.

I think in the video you linked, what's being shown is an instance of VCV Rack representing the modules running within the MetaModule, and there's a non-interactive MetaModule faceplate in that rack that you can use to map from the real MetaModule's controls to the virtual knobs of the modules it's running. Which is a pretty cool interface.

But I reckon what the GP is asking is for a real interactive MetaModule within VCV Rack, running the real firmware - i.e. VCV Rack hosts the MetaModule, which hosts VCV Rack, which could presumably host another MetaModule, which could host another VCV Rack ... etc etc.
Just having some fun with bikeshedding here: Yeah, that could work but IMO in a big/international system the responsibility should ideally live elsewhere, since:

* You may need to determine adulthood for a different jurisdiction than where the person currently resides. Their citizenship may be elsewhere, or you may be running a report that expects "adulthood" to be by some other region's standards, etc.

* Sometimes the underlying kind of adult-need wanted is slightly different, like for consuming alcohol or voting.

* There may be a weird country or province has laws that need additional factors, like some odd place where it's a different age-cutoff for men and women.
England's Ancient Holloways, What Are They?
Repost – You Can Lie, but Only a Little
It's a good reminder that if things get bad, people will just start burning things to try and appease the gods.
EU regulators question Meta about the shutdown of CrowdTangle
Can anyone find parts 2-4? This seems to just be part of 1!
Harris has the right idea on housing
For business Open source is a business tool. Open source can be a goal, naturally, but for-profit entities have a duty to be profitable (or grow, plowing profits into building). I think there's no shame in saying this. You should not need to be elliptical in your public statements about this move. Everyone knows that this is about protecting your ability to monetize the product, and so it should be, and everyone knows this sort of move comes eventually.
I don’t understand how this is surprising for people.

We have evolved under the sun, of course we have adapted to its presence, and taking it away naïvely is unadvisable.
How Far Might We Fall?
Installed Nextcloud from F-droid, Play store tries to update it. Nextcloud is also available on play store, and newer versions are available on play store before F-droid.
While I'm in favour of asynchronous feedback like this, placing toasts nowhere near the button you've clicked is confusing when you get to bigger monitors. A toast in the bottom left on a large, widescreen 4k monitor can literally be half a meter away from the place you clicked, so the toast might as well not have been there. I myself have lost the progress notification for a file copy in KDE because it was placed all the way in the bottom right corner, and my screen isn't even _that_ big.

A little popover near the button makes more sense. Or, in this case, simply disabling the checkbox until the asynchronous action has completed, and using the non-disabled state to indicate success (or show a useful error message when the operation fails).
I have a similar mantra - "if you don't know why a fix worked, you may not have fixed it."

I'm willing to throw shit at the wall early in the triaging process, but only when they are low-impact and "simple" things. stuff like -

have we tried clearing cache?

have we checked DNS resolver for errors?

have we restarted the server?

etc. I try to find the "dumb" problems before jumping to some wild fix. In one of the worst outages of my career, a team I was working for tried to do a full database restore, which had never been done in production, based on a guess. At 3am on a saturday. I push back really hard at stuff like that.
For one, your body absorbs an abysmal fraction of supplements, nearly all of it comes back out the other end. This isn't unique to vitamin D, naturally, but for practically all food supplements. Your body is pretty good at taking care of itself so long as you give it the tools it needs. If you live in a northern climate, vitamin D supplements may be a part of it, but for most part, spending some time outside and getting your movement in is a reasonable baseline.
> Sanbonmatsu et al. (1991) studied consumer choice between multiple brands and products. Experiments demonstrated that when deciding what to buy, consumers search for unique features instead of common ones among alternatives before making their choice. Bolton (2003) further found that even when decision makers are forced to consider more alternatives, including counterfactuals, decisions are still biased towards the initial scenario, which is typically based on availability bias and the inside view. Again, this supports our interpretation that uniqueness bias is likely the outcome of information processing by decision makers rather than an expression of hindsight bias.

This seems like a far-fetched conclusion to me. Neither of these two studies seem to suggest that people do not significantly overestimate uniqueness of projects in hindsight.

The 2003 study seems completely unrelated. How does bias torwards the inital scenario imply a uniqueness bias? That would require uniqueness to be the initial scenario. If anything, I would claim the opposite.

The 1991 study may imply that people tend to focus on unique aspects. Claiming that this tendency in product choice carries over to project management is a strecht imo. And even if it did, that would still not be a strong argument for the conclusion.
You can, and it’s quite possible that provides most of the benefit. But very few systems in the body operate in total isolation, and it’s equally possible something else depends on vitamin D synthesis or on UV absorption, and that thing might matter for health.
There's another thing that happens with busses that makes it worse.

The further behind the previous bus a bus is, the more people will arrive at the bus stop. The more people there are at the stop, the longer the bus has to spend picking them all up and selling them tickets etc. Therefore the delayed bus will tend to experience more delay. The bus behind them will have less people to pick up, so it will spend a shorter time at stops and tend to catch up with the first bus, so the two busses are dragged towards each other.
If he read it at 3.00 am, noticed the missing period, should he just have ignored sending a comment that the period was missing? Not sure what people thought Mark should have done here, should he have remembered the error and send the email later?

Email aren't meant to be responded to immediately.
In short, because the body and the mind is a very complex system.
Curious to hear some real-world use cases for fine-tuning and what your setup looks like in terms of:

- frameworks

- hardware

- foundation models (OS vs 3rd party)

- evaluation & training data

Did the performance gains justify the investment for fine-tuning?
My first functional language was Haskell, which essentially only has a letrec, so afterwards I’ve always viewed everybody else’s approach as a bit peculiar :) Fair point that it’s the Lisp way too.
Teenager's school project achieves plasma
>This affected users that did not have a specific version of the JS library pinned and deployed a new version

Par for the course honestly. The amount of garbage that gets called "production" these days is mindboggling. No blue/green or canary deployments, shipping code that has nothing pinned, no clear rollback, etc. This is what happens when anyone can become an EngineerTM after a two week JavaScript boot camp.
To understand why your totally understandable conclusion is wrong, it helps me to think about what it means to determine the average number of other winners when I win.

The reason is similar to the Monty Hall Problem (https://en.wikipedia.org/wiki/Monty_Hall_problem)

To understand, lets think about the simplest representation of this problem... 2 people playing the lottery, and a 50/50 chance to win.

So, we can map out all the possible combinations:

A wins (50%) and B wins (50%) - 25% of the time

A wins (50%) and B loses (50%) - 25% of the time

A loses (50%) and B wins (50%) - 25% of the time

A loses (50%) and B loses (50%) - 25% of the time

So we have 4 even outcomes, so to figure out the average number of winners, we just add up the total number of winners in all the situations and divide by 4... so two winners in the first scenario, plus one winner in scenario 2, plus one winner in scenario 3, and zero winners in scenario 4, for 4 total winners in all situations... divide that by 4, and we see we have an average of 1 winner per scenario.

This makes sense... with 50/50 chance of winning with 2 people leads to an average of 1 winner per draw.

Now lets see what happens if we check for situations where player A wins; in our example, that is the first two scenarios. We throw out scenario 3 and 4, since player A loses in those two scenarios.

So scenario one has 2 winners (A + B) while scenario two has 1 winner (just A)... so in two (even probability) outcomes where A is a winner, we have a total of 3 winners... divide that 3 by the two scenarios, and we get an average of 1.5 winners per scenario where A is a winner.

Why does this happen? In this simple example it is easy to see why... we removed the 1/4 chance where we have ZERO winners, which was bringing down the average.

This same thing happens no matter how many players and what the odds are... by selecting only the scenarios where a specific player wins, we are removing all the possible outcomes where zero people win.
Note: preventing photo aging by limiting exposure to UV, is currently the single biggest thing you can do to slow [an aspect of] visible aging.
(i hope this comment didn't sound skeptical or dismissive)
> I would much rather only get the toast if there is a failure to commit the change ... And being far on the screen from where I’m taking an action makes them even more of a distraction.

But wouldn't this situation be even worse with a failure-only toast? A request timeout could happen 30 seconds after the fact. You're likely in a very different UI state at that point, and unless the error message is very specific, you'll have no idea what even failed if you are quickly performing lots of actions.