skysight-inc/HackerNews huggingface dataset:
I have seen succesful outsourced projects. They were more expensive than hiring local, because they required a massive amount of up-front analysis, requirements definition, design documentation, and involvement from an expensive middle-management tier of analysts. It took understanding that the process was going to be hard and have a lot of iterative rework. It took understanding that communication is hard.

Markets clear. If outsourcing were so great, it would have completely taken over by now. It has been tested for decades now and it hasn't.

Outsourcing fits really well for organizations that have a lot of explicit, documented, well-understood domain knowledge, for which the org is the key inventor. But that's not most organizations. Most organizations are operating by the seat of their pants, competing in markets where a large number of other orgs know their business. That they turn a profit at all is more a testament to the perseverance of a few, key employees than it is the exceptionalism of the organization itself.

Every axis of communication is a potential friction point, be it collocation, industry, experience levels, language, time zone, culture, personality types, etc. The more you can remove those friction points, the more successful your project can be. But outsourcing throws several of those out the window, never to be touched again. So you're left optimizing on the few that are left, where most companies only ever optimized on those axes that have already been removed.
It still takes effort to sort support requests into those he wants to handle and those he doesn't. If he thinks that the manner in which is work is being used is going to bury him with requests, whether he takes them or not, it makes sense to try to avoid the situation altogether.

I don't think there's a way to actually do that with an open source project though.
It used to be that distro users did indeed open bugs against their distro, and then the distro package maintainer would triage them and forward them upstream as necessary.

I don't know when precisely that stopped happening. Perhaps when OSS became more commonly hosted on sites like GitHub that have more easily-approachable issue trackers, users became more savvy about talking to upstream directly.
Of course, it's easy to look at the last ten years and nudge the number up.

Retiring in 40s is a pretty big decision. It's not impossible to re-enter the professional workforce in your late-40s or 50s, if things don't work out, but it will almost certainly not be easy.
MiniDisk could have been excellent and possibly even overtaken CDs in popularity. They were durable, had a small form factor, and were pretty cool looking. But then Sony decided to make it a proprietary audio format only and totally ruined the UX.
Sure, but I don't see a ton of legislation being passed by Republicans about affirmative action or other areas where there may be some agreement across the political spectrum. I do see dozens of bills being voted on to limit trans rights, to reduce voting access to marginalized groups, to restrict access to reproductive medical care. Their priorities are being shown very clearly by the laws they prioritize. It doesn't help much if we agree on a few things but they have no interest in pursuing policies in those areas of agreement and instead keep focusing on divisive issues over and over and over.
"Sure, they don't support PWAs, but they support pieces of PWAs, so really they support PWAs"
Absolutely this. And it showed that the work output itself is better when the knowledge worked is better off. At least for the teams I am interacting with. Less BS time and more good code.
I don’t really understand the details here. Seems like they disagree about the ease of avoiding it being repacked. Perhaps a good compromise would be for them to collaborate on a solution they’re both happy with. As it is, this conversation looks like: “can you not pls” “too difficult” “no it isn’t” “yes it is” ad infinitum.
People shouldn't always just blindly accept what is told to them as truth either - they need to have the ability to determine if something is true or not on their own, and experiencing/verifying things yourself is a powerful way to do that. So overall it's a balancing act. There's also a lot of information that's lost when you merely just tell someone something. There's just no way to know exactly how bad it feels to touch a stove unless you have been through the experience yourself, there's no way for a human to convey that level of feeling to another human verbally, and as such it's inevitable that humanity's curse is that we have to relive things over and over again.
Pinebook Pro Arch Linux Alternative
I mean, yes, but then when the NixOS folks offer something like:

requiring users to explicitly set config.ambee.acceptThatThisPackageIsNotSupportedByUpstreamDevelopersAndIWillGoToNixpkgsToReportAnyIssues = true to be able to install the package, or they would get an error that would make it even clearer. Would that be enough for you?

the author replies just:

I feel like I'm starting to be on repeat now. Please don't add any of my stuff to this project.
I’m not sure why there are scare quotes around “his”, the code is the author’s property, it’s just they’ve granted a license for it to be used by anyone.
Speaking personally... I did this until a good friend pointed out that while I identified as independent, I basically agreed with most conservative view points. I come by my views honestly. My typical response goes like this .. I hear about something presented on the local news in a very fact based way. I form an opinion. Then I read others opinions and 9/10 times I match with the conservatives.

I mean sometimes I fit with the far left (for example, mother Jones had a great article on private prisons a while ago), but for the most part I'm a conservative.

Anyway, my friend pointed out it's disingenuous to basically always end up with conservative views and claim to be independent because you want the brownie points. And he's right.
Dependencies make this such an interesting challenge. What do you do when a library that’s upstream of 1000 packages with 1000 different authors… goes “rogue?” The friction of forking increases with each downstream you have to coordinate
From the Arstechnica article:

In 2017, Christel Dahlskjaer—who was, at the time, head of Freenode staff—created a corporation, Freenode Ltd., which she immediately sold to Lee.

Sounds like some money exchanged hands.
> Considering that Stripe's original selling point was that it let websites accept credit card payments without seeing your credit card number

This is true, but it's also kind of a misleading statement; the original selling point was that you could accept credit cards without having to deal with the requirements of PCI compliance and merchant accounts, which is done (partially) by you not ever seeing the card data.

If there was similar compliance regulation around document storage, I would assume that Stripe would use "Identity-Document-Standards" compliancy as a selling point. As far as I know, there are no such requirements.

I do think your #2 point though is exceptionally valid, and would hope that the majority of Stripe keys are scoped to not even provide access to this data/endpoints.

Edit: grammar
You can watch the snacks, but I check the TP quality. Easy to verify before you start as well.
The reason is the concern that users will confuse issues with the project with issues with how the project is distributed in Nixpkgs. He doesn't want to have to support nixpkgs.

There are likely multiple root causes. The whole space of issue management around libraries and applications using those libraries is a horrible and abusive mess. In my experience, between an application using a library and a library users will target whichever is easiest; not most applicable. Plus, most opensource user support is a fucking chore (you'd need to pay me for these days) that's unsustainable.

Another cause is likely the cost of nixpkgs contributions themselves. Personally, I no longer contribute to nixpkgs because even for tiny changes the process is ridiculously expensive. That's not including the cost of getting up to speed with nix/nixpkgs and the, often, highly opinionated packaging.

nixpkgs needs to be broken up into multiple independently distributable packages.
If you don't understand the authors frustration, read Daniel Stenberg blog about what kind of requests he gets about curl. It's insane and ridiculous, not everybody is capable of/wanting to deal with all kinds of shit and hostile users like Daniel.
He doesn’t understand the letter of OSS either. Limiting who can distribute a project means it no longer meets the Open Source Definition and is therefore not OSS.
Mate luddite here checking in. It hasn't changed since 2009.
Legally yes they are allowed and can ignore the author as they like.

They can also act as a bigger person and say "Sure, we understand, respect your wish and will find an alternative."
FI = Financially independent = Have enough assets to sustain an acceptable lifestyle off interest from investments + some moderate draw on principal (usually totals to 4%) = Finances are not dependent on money from job

RE = Retire early = retire from the necessary but emotionally unfulfilling jobs. For most people RE means pursuing interests that are not financially viable if you aren't already FI. It can mean a youtube channel, studying whatever you want or working on a side project without strict deadlines or the stress that comes with an all-or-nothing endeavor.

The key fallacy in FIRE, is that it ignores creeping costs and the stubbornness of your dependants. Avoiding lifestyle creep in fundamental to the movement. This also means being unable to fund fancy private schools for your kids and your spouse being fine with the sudden loss of a huge income source. FIRE is an empty pursuit without a definite end goal. If you don't know what you want to do during RE, you might just be condemning yourself to a loss of purpose and possibly significantly higher risk of death/mental deterioration.

Ofc, you can always pursue a more relaxed form of FIRE. Make enough to move to part time / contracts, or move to another country with lower wages or fully dedicate yourself to a moonshot.
Also, I’d put a premium on being able to decide on my own improvements instead of settling on the landlord-chosen paint colours and carpets and appliances.
"Upset open source developer spams other open source repository"?
Funny that the author complains they have no time to support users, but they have time to waste that of other open source maintainers and users as if the wish to package their Open Source software deserved no respect.
> The project could have pinned the version and downloaded from pypi rather than repackaging.

It couldn't, since Nix is a package manager and will only download things from its repository. It can't access the internet otherwise.
> (That’s not the issue here but it touches on the same challenge.)

I don't think so. The "problem" here is that the author doesn't want nixos to repackage his library because he's concerned about a "support burden" imposed, presumably, by nixos users who might get confused and report issues to him instead of the packager. I can vaguely understand where he's coming from, but being as his library in question[1] doesn't even have a single issue submitted, I can't help but feel that the "support burden" is either a consequence of paranoia or an excuse to have his sources pulled from nixos.

Worse, his package is being pulled--if I'm not mistaken--as a dependency of home-automation. So this is a totally different issue than yours.

As the sibling poster said, once you license something under a FOSS license, your intentions are pretty clear. If you don't want that to happen, pick a different (non-free?) license. Saying "this is open source, but I don't want $CLASS_OF_USER using it" no longer makes it open source by definition and thus no longer a free license.

His solution is to release a new version distributed under a license denying repackaging of his code, which is one solution, but that's almost certainly going to cause his package to get forked from an earlier version (under MIT) or dropped from home-automation.

Either way, this issue is going to get resolved, and I suspect it'll be resolved in a way he doesn't like. This should be a warning to anyone distributing under FOSS licenses: If you're squeamish about any vague possibility that someone, somewhere, might--maybe--post an issue on your issue tracker that has something to do with a use case you didn't plan, then you really ought to not distribute it under a FOSS license.

[1] https://github.com/frenck/python-ambee/issues
Oh boy, it sure is impossible to exploit something through a proxy in a training diaper!
It's not just about licenses. Fake chips, as Lego bricks with pins, do exist (seen them decades ago on cheap PC mainboards), but there also are grey areas made of discarded lots that didn't pass testing, lower specs parts relabeled as higher ones, for example consumer rated parts rebadged as industrial if not military, etc. Those are harder to spot, unless they're tested almost one by one. That would be unsustainable save maybe for the military.
That's an extremely valid concern, but one that seems easily addressed via an FAQ.

"I'm running into some issues with ambee..."

"First, make sure you aren't using the version in nixpkgs. I do not support that distribution and cannot help you."
It seems like the reason is (paraphrasing) "because I can't meet the resulting burden of support."

which is something I haven't really seen anything in the open source world manage, though that might be because I'm not much of a contributor. What happens if a utility explodes in usage and the author can no longer effectively support it as a result of being buried in overhead?

Are there any mechanisms for limiting how much of one's life an author signs away to their project (without feeling compelled to grow an operation) while still retaining an Open Source designation?
When they offered to fork it completely to avoid the issue and he rejected that, it really just looks bad.

I get being done with something when you've had a bad experience, but the maintainers here went to every effort to accommodate, and did so in a friendly way.

It reads like this guy wanted a fight and an excuse.

I think the correct answer is to just make the fork as proposed and use that instead, it solves the problem and removes the guy from the equation entirely. The fact he rejected it doesn't matter and he can be angry all he wants.
If they were vaccinated and still became symptomatic, doesn't the symptomatic part imply that they could still spread the delta variant?

What I read from this anecdata (liking that term btw), is that the delta variety can spread despite the vaccine, although probably with a lower R?
I agree. This is kind of bizarre behavior from someone who is such an important contributor to Home Assistant, a large scale open source platform. I can’t imagine most of the leaders in Home Assistant would share this attitude, but maybe I’m wrong.
I do not see that as a problem. Most news media is at least to some extent propaganda and basically all of it is biased. At the end of the day, if I want truth then I have to evaluate each bit of news media for its credibility whether it comes from state funded propaganda or from some supposedly impartial organization. So what I want from an aggregator is to just show me relevant content without trying to sort it by credibility. I trust myself to sort news media by credibility much more than I trust any aggregator to sort it for me.
That isn't a single line macro. Did you mean a single macro crate? Most crates in rust have more than a single macro/function, but some do. Regardless, it's not at all related to how "robust" or not the language ecosystem is.
For anyone else interested: http://www.dereferer.org/?https%3A%2F%2Fwww%2Ejwz%2Eorg%2Fbl... (dereferer because jwz is hostile in case your browser sends referer header)
Yeah, it's doom to fail.

The problem a lot of chain restaurants are facing is the prevalence of the internet and online reviews. They are setup such that you can either go to a known ok place to eat vs some new experience that may or may not be good. However, finding a good place to eat is now easier than ever. I'll look for the type of food I want, then look at some restaurant reviews and I'm off.

Chains like Olive garden or Applebees struggle because every city probably has an Italian or American restaurant that's better quality and price. At this point their main clientele are the internet illiterate.

This is what has killed a place like Planet Hollywood. The entire appeal of it is to be sold to young people as a hip place to eat some good food... but young people are the most likely to read and leave reviews which doesn't bode well when you are serving terrible food. But also serving terrible food at a huge markup? That's a chain killer.

In the next 10 years, I expect that the only mid->high price chains that survive are the ones that adapt. Even then, the outlook is bleak. You aren't going to eat at Chili's when there's a local steakhouse at a similar price and higher quality.
You might want to check what is on the other end of that link when the Referer is HN.
After a few demoralizing layoffs you have a tendency for talented folks to leave once the picture is clear. Does management think software is an investment or a cost? If you can work where it is an investment, do so.
That's not related to this particular issue though.
> the bunker when violent protesters were threatening to breach the security of the White House

Yeah because they didn’t and Trump hilariously lied about the incident. Even they weren’t saying “hang Mike Pence”

> Hillary Clinton spent years claiming that the election of Trump was illegitimate.

She did win the popular vote, while Trump won neither while claiming he did win both….

> They created an environment that was ripe for corruption and then assumed shocked faces as corruption was alleged.

Biden won 81M votes, the most in history. Have fun with the next 4-8 years.
I keep seeing this suggestion, and it seems not to occur to the proponents that it would simply land someone with destruction-of-evidence charges.

What I want is a system that has two passwords that unlock two wholly separate partitions, one of which is anodyne and the other which is where I keep my private opinions about Big Brother.

Of course, astute investigators might wonder why the accessible partition only uses half the storage capacity of the device; you might wish to make your secret space very small and perhaps use some compression scheme as well. If you have a large amount of information that you wish to keep private, you're probably best storing it somewhere else entirely and only accessing it remotely.
As I understood it at the time, alternatives required PCI compliance, which Stripe allowed you to sidestep thanks to tokenization, so I do believe that was a selling point. But this is besides the point I'm making, so I've edited my comment.
Agreed, there is a big market here. I worked on a real estate rental platform where we required ID verification for all listings and applications. At the time we used Berbix (YC company), which is practically the same as Stripe Identity. I would probably just use this Stripe feature today, since we were already using Connect for payments.
Hope this isn't too over the top, but we built exactly this with https://impossiblefitness.com/movement/lateral-raise

Written demo, video, photo, etc of each movement.

We are adding more movements daily. Please give me a shout if there's other information you'd want to see here.
If your only view of Tokyo is what you get through Godzilla movies then you definitely have a problem.

The solution is better movies on Tokyo, not no movies on Tokyo.

You're in luck, though, because there are plenty of great movies on Tokyo -- movies that even people living in Tokyo find give great insights in to their own society.
It's probably this. I haven't completely migrated my bouncer, either.
I don't see anything wrong here. I think licensing terms should heavily favor authors, because if you're writing FOSS, you're already giving away intellectual property for free.

You don't need to suffer any degree of support. Software in most cases is literally provided "as-is." There are no fruits to bare from providing something for free. Clout doesn't pay the bills.

I think people get really weird as soon as you cross the threshold of providing something for free versus something for even a nominal amount. As soon as you have to pay anything, it turns people off. Which is a good thing.
This is incredibly legitimate reason. Could these repacking be replaced with some type of just proxy/clone that is still the original source?
Our latest updates on Fully Homomorphic Encryption
Christmas is a very secular holiday. There is still mass, but in American culture the religious aspect of Christmas is minuscule in comparison to the secular and consumerism aspects. "Most of the songs are very religious" is just not true for most mainstream Americans.

For most Americans Christmas is about family, Santa (Coke's version), Reindeers, Elves, Trees, and Gifts. And then local or family traditions which may include mass, but for most, it does not.

If you'd like some stats - 90% of Americans celebrate Christmas. Fewer than half of Americans consider Christmas primarily a religious holiday. Among younger generations that is much lower (30% of Millennials consider it a primarily religious holiday). A majority of Americans say that Christmas is less of a religious holiday than it was in the past. Only about half of Americans will go to church on Christmas (compared to 82% that will spend time with family).[1]

https://www.pewforum.org/2017/12/12/americans-say-religious-...
If you link to jwz from HN, his server notices the referer header and serves an image that mocks the HN community
Matrix has become the messaging app of choice for top-secret communications
https://github.com/NixOS/nixpkgs/pull/126326#issuecomment-86... says why pinning and pulling from pypi wouldn't work
I mean this very famously happened with OpenSSL - Debian started producing the same keypairs for everyone!
It's sad that so many people get dogs and don't train with them. Watching young women get dragged along by their big working dogs is a common sight in Uptown Dallas.
Whatever its origins, I have the distinct impression that, in addition to being a shorthand, it is used commonly to disambiguate Secular Christmas from Christian Christmas. I agree that Fox News blows this out of proportion and isn't correct on minutia about its origins, but that doesn't mean it isn't commonly used to distinguish between secular and religious variants which is IMHO the more substantial point.
The Nix maintainers asked very nicely whether there was a specific reason and whether they could work with the author to solved it. The author just said "no, just don't include my stuff", which he technically didn't have the right to say after releasing the code as FOSS.

You can't demand respect from the Nix folks after disrespecting them by telling them to do something "just because".
Super interesting take, thanks! I've always been so confused by conservatives labeling all mainstream media as left-biased when I, as a liberal, see them as centrist or conservative.
> Most non-religious americans are something like Christian Atheists. They don't believe in a god, but their worldview, ethics, and cultural norms are still originating in Christianity.

I like latkes and challah, but that doesn't make me Jewish.

All groups influence culture and culture influences all individuals. But simply having adopted a piece of culture that came from some group does not make one a member of that group.

My wife and kids and I all celebrate Christmas. We are not Christian.

If celebrating Christmas made one Christian, then anyone including a yule log in their festivities must also be pagan.