skysight-inc/HackerNews huggingface dataset:
They were in fairly wide "unofficial" customer usage for a year before that too I think.

source: my last day at Heroku was a year prior to that post, and I recall using them.
This is where I first saw the idea: https://www.businessinsider.com.au/silicon-valley-parents-ra...
> How a female engineer defied all norms to save England in the Second World War.

Yes, let's pin the victory on one woman. Fuck the millions of brave front line soldiers, who sacrificed their lives, who paid the ultimate price to ensure this victory. Yay feminism!
Or that crypto mining is not really profitable.

Hetzner calculates tightly on the assumption that many renters don't tax the hardware. This assumption enables a profit on rented hardware. Like already said, arbitrage, but different: by taking away profit from Hetzner.
This is one of the main reasons we started working on Orion three years ago.

WebKit + uBlock Origin = bliss

https://browser.kagi.com
Well, no it wasn't sarcasm... if Twitter can offload image attach and crop entirely onto the client, I figure they would be doing that. Certainly their frontend engineers understand how to. But they must have some reasons for involving the server.
Because they do!

If you go attach an image to a new tweet, you will see it gets uploaded right then and there, whether or not you ever hit post. Who knows what happens from there. Allowing clients to demand more crop work, at will, on top of the one that is automatic seems like it would have some implications at twitter's scale. At the very least, it would probably undo some optimizations they've made around image handling.
I don't think anything you wrote contradicts what I said in the parent comment. In the section you quoted, I only meant to say that other homeserver projects are definitely not dead. There are a bunch that are actively developed and improving.

It's also true that the new homeservers aren't yet ready for prime time. But they're coming along really fast.

It's true that homeservers by third parties had a bit of a rough time in the beginning due to finding "bugs" in the spec that no one noticed before because there had previously only been a single homeserver implementation. That situation has been improving though. I've seen Conduit development result in several different patches submitted to the upstream Matrix spec.
You can already do that on Google -- press "Tools", then use the dropdown to change "Any Time" to "Past Week", or use the Custom Range option to select whatever time period you want.

The question is whether you should also be able to do a strict order by date, without regard to ranking. I'm not sure if you'd ever really want that.

---

[1] California in the past week:
https://www.google.com/search?q=california&tbs=qdr:w

[2] California in October of last year:
https://www.google.com/search?q=california&tbs=cdr%3A1%2Ccd_...
Late here as I was brought in through another HN thread so hopefully you have a chance to catch this.

If I was in your position I would be looking to understand from other business stakeholders how many customers my bug fixes have impacted, both from those that asked and those that would naturally benefit from them if they use the same product. If you know the total customer base, you now the % of the customer base that you have helped (1) improve the actual or perceived probability of retention, (2) directly influence the customer satisfaction of your product(s), (3) improved the chance that the customer continues to subscribes, buys other products / features that your company sells, or recommends your organization to their peers. This can be expressed as contributing to achieve retention goals, improving / meeting targets of NPS scores or other satisfaction measurements, and influencing quarterly or yearly upsell / expansion targets, which you might be able to get explicitly from those other business stakeholders.

Likewise I disagree with the sibling comment that you might be considered a cost to that organization (the organization might actually perceive you that way, but in reality that's actually not the case otherwise there would be no one fixing bugs and implementing features) as are a fundamental core to an organization's strategy of maintaining or achieving retention targets and influence its upsell potential.
Whatever’s in the contract does not matter for a false advertising claim.

You cannot advertise 12, then sign a contract that says 12 on the front, but has “go fuck yourself, you won’t ever see 12 in your life on this plan”. That’s false advertising.

If you do that, you run a real risk of finding yourself the subject of a lawsuit filed by the United States Federal Government, and potentially state Attorneys General
We were all taught that humans are not special and the earth is common. Well, it looks like everybody was wrong. We are unique after all.
Definitely. Last time I was looking at least 80% of job postings obviously had no job behind them or were duplicates. H1-B setups, recruiters simply trying to build a list of clients, multiple ads for what was obviously the same underlying job, a few that continually posted the same ad but didn't look like recruiters etc.

I suspect the actual garbage rate was at least 90%.

Admittedly, I do not live in a tech hub and relocation is not an option.
Ford F-150 Lightning Electric Truck
I bet Conduit is going to be the easiest to deploy once it's finished. It's a single binary (with the database included).
Going through the motions of using anything but nix now kind of drives me crazy.

The nearly clean builds nix provides with a replicable tool chain in most cases is stupendous.

It's the perfect container build tool. You can always, repeatably, build a container from scratch.

It's not a shabby distro either!
> In a way its more odious than violence.

You have very little understanding of the Amish perspective. If your assumptions of their beliefs lead you to a conclusion that their pacifism is more odious than violence, it should be a red flag that perhaps you are mistaken in your assumptions.

Their security, in their view, rests with God. The Bible demonstrates repeatedly that, at times, God uses evil men to keep other evil men from harming His people. For example, God used the evil Babylonians to conquer the evil Assyrians, to the benefit of his chosen people who were commanded to keep a low profile and stay out of it. Likewise, the evil Persians conquered the evil Babylonians, leading to the release of the Jews from captivity: once again, the Jews in captivity were to lay low and let God seek vengeance in the Babylonians.

The Amish are quite aware that one group of evil people (let’s say cops and the state) are doing evil and violent things to another group of evil people (namely, criminals.) The Amish stay out of it, keep a low profile, and rely on Providence.

In short, their views are more subtle than you think. Instead of concluding they are ‘odious’ you would do well to understand them.
Who is "we"? The IPCC was created in 1988, at the alarmed demand of the Weather and Environment offices of the UN. In 1997 the Kyoto protocol was signed by 184 countries, recognizing the urgency and the need for CO2 reduction.

Only in the US is there a political debate about climate change denialism. Thanks to you it is coming to other countries, but before GWB it was a fringe position everywhere.
FWIW I upvoted you upthread to try and counter the inexplicable downvotes; to me the points you made are uncontroversial and almost self-evident. (shrug)
The range filter exists for that.

Sorting by date wouldn't work for that. You'll have a ridiculous number of pages of oldest search results (or newest, depending on sort order).
And here I am living in one of the places that most of the SF tech crowd would consider synonymous with "failed rust belt shithole" where none of that stuff happens at any appreciable scale.
My personal and not-in-the-weeds take is that k8s had some base assumptions that turned out incorrect and things become more convoluted because of it. Originally, state was not included with K8s because state is hard and is antithetical to their goals. Then enough users ended up convincing the project that state was here to stay and then complexity kept growing. People realized they need variables for values like port number to be shared across k8s files and so templating was introduced. But that wasn’t good enough and so another layer of abstraction is added, then another layer, etc. As more surface area is introduced, they didn’t want to appear to be making too much churn, so instead of lots of major and minor version bumps, they introduced beta features that they could break without feeling like they broke backwards compatibility even though it still breaks integrations that use beta features (gRPC package in Go did this too). In summary, I don’t think it is over engineered per se, I think it will be a stepping stone onto what ever is next that solves for these kinds of things in its original design instructions of being tacked on.
Native apps (including those delivered using technologies such as Uno) offer a richer user experience with better performance and a more native look and feel. Blazor currently is an incubator technology that suffers from slow initial download and still relies on all the cludges that we've come to rely on for the web (html, css etc)
Fortunately (or unfortunately depending on your perspective), they will be fine... Enterprises are able to configure Edge to load certain websites using the legacy IE rendering engine (until 2029). Shouldn't break anything at this point, while allowing the rest of the internet to abandon IE.
That said, the ABS tree and the AUR in arch, combined with the general avoidance of patches, do make arch one of the easiest places to play with bleeding edge software. With the toolchain in place, so many packages are just a one line version number change to get any particular version building. Whereas building packages from source on ubuntu/fedora/etc can be an uphill battle depending how entrenched the distro's patches and inter version dependencies are. (Though most of the time, building things via make and sticking them in some directory is acceptable, arch really does make building packages easier than other distros)
Unless you have inside information on the terms of the acquisition, I wouldn't beat yourself up about what might have been. There's a very broad spectrum of options here between "we like the team and have agreed to put them on payroll because it's cheaper and faster than using recruiters" to "F$%@ you money for the founders". We've no way to know which it is.
> "Is there any work left to be done?"

Google could search captions on all the Youtube (etc) videos. Not sure why this doesn't happen. Along with a few other big resources not indexed.

I think the big thing with the article(Taken as a workable technology) is it's not search, it's getting other peoples information and transforming it into a Google resource.

Which does add to humanities knowledge, but it's owned and profited on by Google.
I don’t know if it’s “e-commerce” specifically, or just a more general fact that Google own a search engine, and want to surface URLs from their index as answers to questions, when appropriate. And, when you think about it, why would you be linking to a page — rather than giving a straightforward answer — unless you’re linking to a product page / review / other page that offers you a direct means of solving a problem that goes beyond a conversational answer?
As an outsider how sends resumes, it is difficult to know what a good resume is because one has not had the on hands experience of actually knowing what others are doing. Some searching on the internet may be helpful in the end but the jobs I got so far felt like blackboxes in the hiring process.
I was only commenting on electrolysis, I did not make any statement about hydrogen power in general. However, now that you brought it up, the other issues that you mention are very surmountable:

- Transport. You can either transport hydrogen via pipelines or simply produce it via electrolysis in-place. You have to get the electricity to the destination somehow, so this doesn't really differ between electric and hydrogen cars.

- Building up pressure. Energy required to build up pressure is related to how much the volume is reduced (force x distance and all that...) Conveniently water is almost incompressible, so you can raise the water to the desired pressure cheaply before you electrolyse it. https://en.wikipedia.org/wiki/High-pressure_electrolysis says this can be done at 97% efficiency.
It’s high status in some circles that equate celebrity with prestige
This really is a section that needs regulation. You basically have to use and allow Google to crawl your site if you want a website findable by 95%+ of Americans, so websites really should be able to tell google how they're allowed to use the scraped data instead of just 'for anything'. Maybe a meta tag would work well.
Mandelbrot was such an entertaining writer. I enjoyed The Misbehavior of Markets a lot.

He does tell a few “I’m such a badass” stories a la Taleb, but somehow he’s a much more sympathetic character. When he talks about bullying some bureaucrat into accepting his dissertation, you can’t help but root for him. Like, it’s a pretty bombastic story, but at the same time he’s such an underdog in the story itself.

Plus the mathematical modeling stuff was eye opening for me too.

Highly recommended.

Edit to add: Kahneman’s writing is much closer to Mandelbrot than to Taleb. I think you’d like Thinking Fast and Slow.
I've checked them out for the last 4 years while contemplating a move from Spectrum and every time, on checkout, there was the $10/month non-removable fee for renting the modem with no opt-out. This is in central Texas.
Once it's out of the bag, all over reddit etc., might as well let the conversation continue.
"San Francisco Deputy Public Defender Doug Welch called in to the hearing to say his clients charged with shoplifting are not part of organized crime, but are homeless or struggling with substance abuse and need more services."

As if is not stealing if you are a druggie or homeless.
> No, I'm positing the premise that it was shipped with an absolute minimum of QA that didn't approach the level of trying to build 'inclusive' reference sets, on the cheap. It wasn't about caring in terms of priority of what was tested, it was about NOT caring that much in any direction and shipping it.

Right. I’m saying that not caring is the problem. We mostly agree on the facts. I’m objecting to not caring as an acceptable position.

We’re not talking about shoestring developers. We’re talking about platforms that millions of people including heads of state use to affect billions of people’s lives.
Are there other reasons than financial compensation that someone would put facts on a web page?
Your first concern is addressed by saltstack - they chose an agent based approach, with client subscription, as the default, which makes for a significantly faster experience.

They subsequently offered an ssh-based option for those that wanted the poor performance of Ansible across larger fleets, or where agents were not palatable.

Unfortunately it doesn't address your second concern, as it also uses yml + jinja.
OpenFlexure Microscope, an open-source optical microscope
I fully agree about algorithms--that's what Google is for.

However, I can see merit to making a playable game of Go. I would think a playable game of chess or checkers would be a better option, though, as people are much more likely to know the rules.
This should fix the “broken enterprise network” problem:

https://www.stunnel.org/

Listen on port 443; problem solved until they switch to server allow lists.
> Business and/or First class do not make up for the jetlag.

Jetlag isn't as much of a problem if you're going for the nightlife.

I don't know whether Greece is that sort of destination, but know of people who jaunted off to Ibiza, for example (from the East Coast, anyway).
Finally that age old question has been answered!
The Belugas Have Landed
It also creates an incentive for those unwilling to pay high prices to find ways to do without, or to delay their purchase until production has caught up.
Some minutes searching the IEMode and WebView2 links and not a single match for ".HTA".
Thankfully Android (without Google stuff) is technically FOSS.
I'm glad I left Canada when I did.
It beats Baltimore and Chicago by a mile. Those cities are known for bad crime.
Yeah Crossbeam is awesome. And the pre-1.0 story about a similar interface that existed in std, until it was found to be unsound, is totally fascinating: https://github.com/rust-lang/rust/issues/24292. (Prior to that, std::mem::forget was marked unsafe!)

Another detail that's worth clarifying for folks reading along: The API in this example will automatically join all threads at the end of the crossbeam::scope. (That is indeed what makes it safe.) So if your goal is to fire off a background thread that will outlive the current function, you usually need to go back to std::thread::spawn and live with its 'static requirement.
You're being disingenuous. IRC has been right at the center of the vast majority of non-enterprise technical communities and especially opensource for the last 25 years.

Say what you will about culture but this is a fact and I don't see it changing. Slack and Teams are gimmicks at best. Matrix unusable for me, every single one of my peers and, apparently, the vast majority of said technical communities that keep their center of operations firmly entrenched in IRC.
A worthwhile read about the current SF DA that might explain a lot: https://stanfordreview.org/chesa-boudin-san-francisco-crime/
I've tried using this ad blocker before (I'm sure I saw a mention of it on DF or HN a while ago) but disabled it and went back to AdGuard. It misses too many ads for me and doesn't give me enough control (I like specifying which lists to use or if I want to just block social media widgets vs ads vs analytics/trackers.)
Unfortunately due to some things that happened with the way they renamed packages after the split (from ansible to ansible-core and ansible-base), it required a full 'uninstall and reinstall' operation, otherwise Pip gets things a bit confused and the installation breaks completely.

There was a Herculean effort to try to get it to just upgrade cleanly, but in the end it turned out there was no way.
Oh good, the city I left Seattle for a couple years ago is not mentioned anywhere on this list. My rent has one less factor to push it into unaffordability.
This might be a stupid question, but why couldn't select be extended to accept fd's >=1024? I don't see "not segfaulting" breaking existing behavior and it would solve basically all issues with legacy programs. Yes, it might lead to select being used a bit longer than it otherwise would be, but that would probably be less of a pain than fighting segfaults caused by a `select()` somewhere in a linked library.
> No new code should be using select(). Using it assumes the execution environment keeps all file descriptor values within FD_SETSIZE.

Perhaps it might be time to start treating select() like gets() was treated: the compiler should emit a warning by default whenever it's used, and after perhaps a decade, the API should no longer be available for newly compiled code. While not as bad as gets(), which according to Rusty's classification of API quality (https://ozlabs.org/~rusty/index.cgi/tech/2008-03-30.html and https://ozlabs.org/~rusty/index.cgi/tech/2008-04-01.html) gets a -10 ("It's impossible to get right"), select() is around a -5 ("Do it right and it will sometimes break at runtime"), or perhaps even a -7 ("The obvious use is wrong").
Ask HN: How does your company accept code test submissions?
Background:

My company is currently evaluating processes for accepting code test submissions from applicants for our various engineering roles. We have about four or five GIT repositories that have the "code test" project. Right now we're just doing a `git archive` and sending the .ZIP file to the applicants to complete, and then email their submissions back to us. This is obviously very manual and not ideal.

What we would like is to be able to host these "code test" repositories on GitHub (or GitLab or BitBucket) and just allow applicants to fork the repository and then submit their code test as a normal Pull Request. But the applicants' Pull Requests SHOULD NOT be public. This would be our ideal workflow.

How does your company handle code test submissions during the hiring/evaluation process?
If this weren't HN someone might attempt to draw a humorous connection between this passage and his reported lack of need of romantic relationships.
I appreciate having a streamlined chat application, but understand that others feel differently. IRC applications are much better on resource consumption and snappier in my experience, but aren't all that practical on a mobile device.

Naturally, how each of us feels about that experience is subjective. So setting that aside, the part about IRC that I haven't seen handled with Slack is being a one-stop shop. With IRC, I can discover and access multiple communities within a single server at once. The most popular servers can be connected to and browsed with a click in most IRC applications. With Slack, I need to find a project's Slack workspace, request an invitation, then go through the process of adding it to each of my clients. I'd love to see the equivalent of a FreeNode workspace where I can join an OCaml channel and a Ruby channel without going through all of the above and dealing with walled-off communities.

Revisiting resource consumption, I've opted out of communities that moved to Slack because once I hit around 10 workspaces, the Slack app slowed to a crawl and guzzled RAM. To be fair, that's gotten a lot better in recent years, but I still find managing several workspaces to just be too much cognitive overhead. I may only be in one channel on each workspace, but I can't easily switch between them. With IRC, doing a "/join ##ocaml" is super fast, barely consumes additional resources, and adds a new tab to my main interface for fast switching between channels.
My sincere guess is that we'll kludge the problem with relatively low-tech geoengineering solutions. Primarily stratospheric aerosol injections. The technology is very well understood and fully mature. We know with certainty, from historical volcano eruptions, that a large enough dosage will lower global temperatures near instantly. And the cost is low enough that even a single mid-size economy could afford to unilaterally engage in it.

The downsides are secondary environmental effects (e.g. ocean acidification), the hesitancy of a single country to make a climate altering decision for the rest of the world, and the general bad optics of sweeping the problem under the rug for future generations. All that being said, up until now the tangible costs of climate have so far been relatively mild. If nothing big enough gets done on the carbon side, which seems increasingly likely, then warming will reach the point where it starts imposing major economic and humanitarian costs.

At that point, it's nigh inevitable that at least one major power will bite the bullet and start pumping the stratosphere full of sulfur dioxide.
Garbage websites hyperoptimizing for SEO have existed since the late 90s. I agree with the GP, the issue I have seen over the deterioration of search in the past 5-10 years is specifically a result of their business model:

1. Any remotely commercial search has an entire first page of ads, organic results are pushed way down.

2. Google has made it difference between ads and search results as minimal as possible. I long for the days of the early 00s of big yellow boxes.

3. On many pages the amount of content Google stuffs in at the top before you get to actual search results gets more annoying every year.

Honestly, I wish I had a button that made Google result pages look like they did 15 years ago.
> Running them in parallel would be better.

It does run in parallel by default though: https://docs.ansible.com/ansible/latest/user_guide/playbooks...