skysight-inc/HackerNews huggingface dataset:
I think if you're actively deploying malware that people will run, the case is pretty clear. And when you say "for common use", it sound like you know that it is or intend it to be distributed and run by many people.

What's less clear is security holes (which are not malware as such) or just "putting code out there" ("not in common use", although someone could come and pick it up and start using it). I would defend your right to write exploits and backdoors and bots and put them on github.

Simply making a security hole is IMHO OK unless you have intent to exploit it (or let someone who intends to exploit it know about it).

The difference, for me, is in writing versus deploying. And I'd consider it deploying if you intentionally post malware to a public repo you know people will run (without knowledge of having malware in it).

Contrast with building a trap (and maybe showing it to people) and stashing it in shed, versus building a trap and priming it and putting it in the woods where you know kids like to play. Not a watertight analogy, I guess making traps could be illegal just like making guns is in many countries. But you get the idea. I think you should be allowed to write malware or make combat knives or mantraps for fun but don't put them to their respective use.

Of course, going down this line of reasoning is a rabbit hole. If you build something on your yard (something that isn't illegal per se and has no intention to harm anyone) and it turns out to be dangerous and someone gets hurt, you might have to take responsibility (but it really depends on a lot of factors and would be decided on a case by case basis). I'm not sure I would like such reasoning to be applied to FLOSS projects that come with a warranty disclaimer and which can freely be audited by anyone who intends to use them for real. It's not like they hurt you just because you happened to stumble upon them.
So, spec is the ukulele in the vast domain of Type Systems?
How does 2020 bode for China’s overseas investment? A Chinese lawyer’s take
Good job!!!
Multiple particle entanglement is the common state. 2 particle entanglement is a special state achieved for research and manipulative purposes. A quantum computer is made up with multiple particles being entangled. If they didn't, the speedup would only be a parallelised version of a 4x speed normal computation.
If interested, this is the economic news release: https://www.bls.gov/news.release/jolts.nr0.htm
Rust didn’t introduce this language, they adopted it. Memory safety has been called that as long as I’ve been programming.

Using the antonym of safe was a natural move, though with the benefit of hindsight, `danger` would have been a better keyword.

After all, good unsafe code isn’t unsafe! It is dangerous though, because it forgoes guarantees of memory and resource safety provided by the compiler.
Is there anything else you would like to demand about people's code they you are not paying them to write?

I demand you go write a tool that lets me query projects and tells me if you think they are a toy or not. I'll wait.
You don't need links. Just exhaust yourself. You know how.

I was in the same boat - solo founder, working 14 hour days, incredibly stressed. Exercise and avoiding alcohol, drugs, and shitty food is the key.

There is a certain level of stress that I think can't be dealt with. When you reach that limit, you have either step back and curtail what you're trying to do, or just push forward and get through it.
The benefit of extra speed in ballot count does not completely offset the risks of electronic voting. Not only the risks of massive tampering in electronic ballots and servers, but also the lack of clarity on how the process works under the hood for the median voter.
Does the US government provide metrics on job openings by wages or some measurement of monthly or annual earnings?

My portfolio has been doing fantastic, but I have to stop and wonder how the average person who doesn’t have assets is doing.
You are right that he didn't have to do any of the things people pointed out but that doesn't mean choosing not to do them isn't fair game for criticism and "he should have labeled it as a toy project" and "he should have given reasons why he didn't accept the patch" seem more like fair criticisms than making demands.
That's not guaranteed to be true. Leading the way on fostering new cleantech is a way to get ahead of the same cleantech industries elsewhere. The question is really how good can the timing be rather than if it's going to happen.
Alas, common sense is an uncommon virtue.
Didn't the Rust stdlib just gain a high-performance hash map recently? Is there a real case for using a custom implementation in reqwest? I could see Shnatsel getting a bit frustrated wrt. that choice.
Love to see adoption of living building challenge even if it is their least rigorous certification.
Maybe that is what the developer intended, but afaik it is not what he communicated. What he communicated was a flat out dismissal of the issue along with the proposed fixes. Followed by deleting the whole issue from GitHub. To be fair, there were some very unpleasant things said in there, but he could have just deleted those and maybe locked the conversation telling people about his plans.

This whole thing was a feedback circle of increasing hostility between the community/contributors and this developer. At some points the developer was very unresponsive, leading to disappointment from the community, but then some very uncalled for personal attacks came from the community. I think the developer received some justified criticism, but I still understand his perspective, putting work in and getting abuse back sucks.
Alternative summary

About 150,000 Americans are homeless in the way you worry about homelessness: Suffering from addictions and other mental illnesses, they sleep on the street, and stay there for months or years. Most of these homeless people would have been institutionalized before the de-institutionalization of the 1970's.

Another 400,000 have no more addictions or mental illness than the housed population. They sleep in cars, shelters, or other protected sites. Their homelessness lasts for several days or weeks and then they are able to obtain housing again.
> Making all of these overlapping API calls in a performative, reliable way is a challenge.

Pythons asyncio is pretty hard to beat. For non-cpu intensive tasks, I find it a pleasure to work with. Goroutines can still have race conditions.

> Originally, we wrote the CLI in Python, but trying to distribute it across platforms proved to be too difficult

Sure, I get that go can cross-compile. But what makes python hard? Python works on every platform, and distributing is just a "pip install" and "pip install -u" Surely thats easier than
"Download the correct binary for the platform, unzip it, change permissions, add it to your path, then do it all over again for every update"

I was the original author of the awseb cli and we found that pip install was significantly less of a hurdle than a go binary and decided to do it in Python instead. If a user on windows has a hard time installing python and pip, telling them to drop a binary and change their path isnt going to be any easier.
Then we get blasted by a gamma ray burst from Betelgeuse and we're all dead. Studying the cosmos is extremely important, and studying threats (asteroids, supernovae, etc.) are just one part of that.
This doesn't indicate if is good or bad. You need to know employment rate as well, all the job could be getting filled faster than they are opened.
If the goal is to reduce emissions, then a tax on emissions is the only solution. Anything else is too open to avoidance (just look at corporate tax avoidance).

Maybe there's other ways to make it better for the people who can't afford it - a tax free allowance they can claim back or similar.

I'm still not sure if this is feasible across borders though. How can you stop carbon tax havens?
> I imagine this list would be different if the team was 100% remote.

IMO this is a key point. I wouldn't recommend working remotely unless the entire company (or at least the department) is organized online and people are generally remote.

That said, I don't believe 100% is a necessity, as long as you act it. Eg some companies have a "one camera per face policy" for meetings. We recently adopted it, and it works super well. At my company though, sometimes a few people are colocated, and you get this weird dance of finding a spot sufficiently far away from each other to be able to stick with the policy and not also hear each other directly, with no latency. It's weird but it works super well. Everybody feels more connected.

With a few rules like that you can be, say, 80% remote and not 100%, without the downsides. Really it's all about the mindset.

Also, seriously folks, do retrospectives.
You're appealing to an emotion that I have already conceded to share. And it can't be more than an emotion, unless you are one of the very select few who have seen this forest.

However, my emotions occasionally tell me something that intellectually, I know not to be in my best long-term interest (or even far from it).

Edit: Try to think of my argument another way: I feel a certain way about this, and I would like to rationalize that feeling.
Are you asking for a value judgment? Or what exactly is your question? This can happen for example in some games like Master of Orion. You send a ship to the border, and before it gets there, you've already researched, built, and deployed a faster version. Sometimes it changes things, sometimes it doesn't. If your sole purpose is simply to arrive then it hasn't changed a thing. If you are planning to fight aliens when you get there, however...
Why would the voter remove the paper ballot or paper receipt from the polling place?

The paper would be kept by poll workers so the electronic count can be audited.

My state has paper ballots that are counted electronically. I feel this is a good compromise and allows much easier vote total auditing.
If a team member is requesting changes that don't cause any harm, then I tend to just make the changes in the interest of overall productivity.

If, however, I have a sound technical reason to disagree, then I discuss it with them. 90% of the time, a solution can be arrived at quickly, with one of us seeing that the other's approach is the best one, or both of us finding a third approach.

For the other 10% of the time, I've found that both of us are making really solid points. So I rope the rest of the team in on the issue, summarize as accurately and fairly as possible what the dispute is, and what the position of each of us is (if I can't correctly state the other's argument, that means that I don't really understand it -- and that has to be corrected first). So far, every time I've done this it has led to a rapid resolution, often because there's something that both of us missed, but someone else in the team noticed.
Those goals all seem very concrete? What does nebulous mean to you?
Mr. Andrews, high school computer science. I got bullied terribly in his class from other students[1], and he made sure I still got to take his classes.

He let me hide in his classroom and work on programming projects during mandatory pep rallies.

He taught me programming fundamentals like object-oriented programming and functional programming, database structure, and bug hunting I still use twenty years later.

He encouraged me and told me good classes he taught to take at the same time so I could work on skills in the right order, and when I had two of his classes at once he let me do work from the harder class during the easier class.

He wrote me a recommendation letter that showed he knew me, and I still have it framed in my office.

[1] I was the only girl, a year or two behind the majority of the students, and a sarcastic little thing. Kudos to him to telling me being aggressive and female at the same time was ok, and showing me how to do so in a better manner.
> You would need to invest an enormous amount of hashpower to create so many blocks that the difficulty adjustment could ratchet down

Thanks for the clarification. I don't know much about the difficulty adjustment algorithm of bitcoin so that's the point I was missing. So I guess there are some mechanisms like "the difficulty can only be adjusted every N blocks" and "the difficulty can only rise/sink by X%"?

If that's it and the deadline for when the key should be released is far enough in the future (e.g. 50 years?), it might still be feasible for an attacker to implement such an attack?

> simply by changing the witness proof to require blocks have a certain minimum hashpower on average

This assumes, bitcoin is an ever growing network and will never loose miners below a certain point. Depending on how long the key should be secret, this assumption might not hold true and I wouldn't depend on it.
When there is so much discontent in the community a fork is a very natural consequence. This, in my opinion, is open source working well.

https://en.wikipedia.org/wiki/Ethereum_Classic
The buttery males? Oh my, that was a national security disaster! /s

Edit: actually, she did get in "trouble". That faux controversy helped sway the election against her.
But that’s the thing : there is definitely a science for climate modeling, but it’s probably at its infancy. Someone brave enough to correctly asses the limits of the field should be recognized in the field itself. It’s a bit similar in spirit to the « reproducability » issues in biology research.
As others have suggested, a corresponding decrease in income and corporate tax such that you get a revenue neutral framework with no additional wasteful government spending would be supported by many, including those on the right. This may also have an additional effect on neutralizing any downwards economic impact from the carbon taxation.
Thanks for including GitLab in the report, Hrishikesh!

For those looking to learn more on remote, or leaders/founders considering it, here are a few resources that were used in this survey.

GitLab's Guide to All-Remote: https://about.gitlab.com/company/culture/all-remote/guide/

Informal Communication: https://about.gitlab.com/company/culture/all-remote/informal...

People: adopting a remote lifestyle: https://about.gitlab.com/company/culture/all-remote/people/

Guide for starting a remote job: https://about.gitlab.com/company/culture/all-remote/getting-...
I Started a $30K/Month Business Selling Custom Trade Show Booths
Which countries practice direct democracy for their top executives (Presidents, PMs, etc)?
Its on the up and up, why do you ask?
Did someone hack into your account? This is obviously a troll message, but your older messages are normal.
You don't get to invoke professionalism, or lack thereof in regards to some individuals work they've made available for free.

Open source gives you access to source code to do with as you please. Storing your own copy is a good idea if it's something critical to your endeavors. The possibility of having to maintain anything of that nature yourself is always a risk.

Expecting, demanding, or begging for anything except what the author willingly, and happily takes upon themselves is exploitation, pure and simple.

If you think about it, trying to coerce an author/maintainer into doing anything they willingly and explicitly have commited to, is no different than employing bullying, group pressure, and other social/psycholgical manipulation techniques to get whatever outcome others deem useful to themselves.

Yes, something as trivial as complaining about the lack of response to a question can easily be seen as being abusive when there is no established relationship or expectation, no quid pro quo, or similar.

Getting free access to someones work is amazing, and nobody should ever have to face what so many maintainers have to face today in the form of unreasonable expectations and outright bullying.
Open source is fundamentally wrong and in need of a correction. It's an exploitative labor practice.

There's a better way. It's coming.
> it is incorrect that languages doing what Rust does fundamentally need unsafe-blocks

But they do need those. Even C# has unsafe blocks, and Java has sun.misc.unsafe. It's a rather boring feature actually, the interesting part is what you can assert about safe code, and at what cost.
He's not referring to giving you a receipt, he's talking about voting machines that produce a paper print out that the voter quickly confirms at the polling place, then deposits in a ballot box. If the custody these paper ballots is managed carefully, they can later be used to verify any apparent funny business in the results of the electronic vote counting system.
That’s not Tesla, nor is it a big investment. Boring Co is funded by merch and client work.
كلمات اغنية عذابك صنعة شيرين اللجمي
This is going to be a game changer when the first password manager implements a no third party time-lock as its recovery by trusted contact mechanism. Most of them just hold onto your password store public key encrypted for that contact, if they implement a trusted contact recovery at all.
The problem is that gas is a small part of the equation. You also need to account for depreciation, increased repairs, and opportunity costs (e.g. Uber may require a newer car than you'd otherwise get). It may look like you're making money because you make more than you pay in gas, but I'm guessing people aren't noticing that their day job is subsidizing their side hustle for infrequent expenses.

I use the IRS figure of ~$0.50/mile to ball park an opportunity. When I calculated it for my car, I got closer to $0.25/mile, but that's because I got a good deal on a reliable, used, efficient car (~$10k for a 60k mile Prius) and I do most of my own maintenance. The average driver (having a shop do repairs, worse mileage, buy from dealer with loan) will likely be closer to the IRS figure.
U.S. will look at sudden acceleration complaints involving 500k Tesla vehicles
thanks. how absent-minded of me to not link to that one
I think the whole attestation thing is generally a terrible idea. It's not impossible to extract data from secure hardware, right now there is not a lot of incentive to do it because it's not going to get you much, spend a month of hardware research to get one user's key, no thanks. But with whole batches of devices having the same private attestation key stored on the device this incentives essentially ransom of security key vendors. I.e. Lets say I am a hacker that spends a month of hardware research finding a vulnerability and extracting the attestation private from a token. Its worth my time because I know this vendor has 100,000+ keys out there that uses this same attestation key. I then request that vendor send me $500,000 in bitcoin or I release the private publicly. The vendor pays the ransom because it's cheaper than recalling 100,000+ security keys. Another issue here is it's not if but when this happens, so when it does how do all of the web sites out there update to block the hacked keys? Lots of web sites never will. Time to rethink the attestation key being stored each token, that's a bad idea.
Of course, I don't blame Mozilla for all of that. I'd like them to champion disadvantaged users, that's all.

I expect more from Mozilla than from the other players in the web/browser/mobile scene, perhaps I'm wrong!
That’s what I was trying to get at with the “is /r/rust part of the community or not” bit. Inside official spaces, none of this happened. If you don’t read Reddit, it follow certain folks on twitter, you wouldn’t have seen any of this.
Pretty sure it is. Fairly ubiquitous, and I know of nothing else that would conflict with it.

RasPi is also used.
Which is what? Use a different phone? Thats not always an option except maybe to the priveledged
And this is why I honestly don't ever want to release an open-source project.

At the very least, I'm not going to make it easy for people to contribute. I'll keep the git repo private, go without a ticketing system, and just post tarballs full of code on a self-hosted website (I guess like the NetHack team used to do before 3.6, but they had a ticketing system, and I wouldn't). Maybe I'll even use a non-free license just to reinforce my "you take what you can get" policy.
The only service I have seen that only allows Yubikeys so far is Vanguard.
Amazon Puts Consumers at Risk
This has been the argument throughout the various discussions -- that somehow if there isn't a payment structure between party A and party B, there is full immunity from criticism, questioning, expectations, etc. It is absolutely insipid and is a logical non-starter that doesn't pass the most basic of considerations. Yet it keeps recurring. It's bizarre.
Cooler Master is tired of telling parents their kids aren’t on drugs
I personally think engauging with other people directly without a corporate intermediary is the way to go. /okboomer
Concerning is what message this sends to other OSS developers. One goes into F/OSS knowing full well there will be little rewards financially - but facing harassment or attacks on their reputation cannot encourage future projects.
LOL rust is a shit language that will never replace C, and this situation was entirely predicted by doubters, despite the assurances of rustophiles who claimed unsafe was not a problem, won't be abused etc.

The emotion unveiled by this incident shows a deep anxiety in the rust community that the doubters are correct.

C forever!
Any advice (books,blogs, etc) for someone looking to hire the first people?
Your analogy is stupid. People are still able to fork the project. Taking the ball and going home means that you prevent everyone else from playing,
The C4 Model for Software Architecture
I don't think using the IRS mileage number is an accurate way to calculate costs of operating a vehicle for a couple reasons.

Consider this report from AAA: https://exchange.aaa.com/automotive/driving-costs/

Notice that the cost per mile actually goes down the more miles you drive! You have to drive 20,000 miles to get down the ballpark of the IRS number. This indicates that expenses affected by mileage like gas, maintenance, and depreciation are dominated by up front costs like insurance and taxes. Now consider that most door dash drivers already chose to have a car before working for door dash, so they will have to pay the up front costs regardless. For this reason, I don't think $0.58 per mile is a good estimate of the marginal cost associated with extra driving for door dash. The AAA report estimates gas and maintenance costs per mile at $0.17 to $0.23 depending on the type of car.

Second, I don't believe it is right to include depreciation in a household budget because it does not manifest as an additional cost on top of the price of the car. Unless the car is listed as a line item on your household budget, you don't have to account for any additional loss in value. Imagine that you bought a car in cash for $1000 and never drive it. You lose the $1000 immediately. If some years later the car is worth $0, your total cost of ownership is still just $1000, not $2000.

I believe the fact that people still chose to work for door dash is additional evidence that the estimated costs in this article are too high. We may not be perfect rational actors, but most of us can tell if our bank account is going up or down.

None of this excuses the unethical behavior of door dash, and personally I choose not to use them. I believe tips are intended as a gift to the driver, so it is misleading to call it a tip if the driver isn't getting it. That said, I didn't find this analysis convincing for the reasons above.
some people just walk up to your desk/office without checking the calendar to see if you're in a meeting. I'd guess this behavior correlates pretty well with not sending a quick slack message to see if you have time to talk.