jkeisling/hacker-news-corpus-2007-2022 huggingface dataset:
Nope.

It was known that some could have perfect memory.

I read in my childhood about man who remember everything. He worked as a reporter and never wrote down any tasks editor gave him. That man told the editor that he won't forget and he did not forget anything, really. So editor send that man to psychologist who discover that he had perfect memory.

)the story was about 60-s or so)

The perfect rememberer had a mild case of synestesia, but he used it to his own advantage. He put so many hooks on anything that he couldn't forget even if he try. He remembers conversation by their content, sound, color, texture and taste (and much more). So every word has its own color, texture and taste, they make a web of them, much like labyrinth or city map.

When I need something I shouldn't forget, I also try to put as many markers as I could. It hepls sometimes. ;)
I'm not really sure I understand your question. RVM is a tool that can do all of that for me, and it's used and vetted by a large community. I don't know why I wouldn't use RVM.

RVM automates the compilation step. I'm not sure why I'd want to do that by hand instead.

Gem installation is done on a per-app basis using bundler[0] or RVM's gemsets, so the gems for each application are kept separate anyway.

Running different applications on different versions of Ruby at once is also easy with project-level rvmrc files.

And if for whatever reason you want different RVM installs for different users that's easy too: RVM only installs for a single user by default.

Now, granted, I don't do anything like run a shared hosting service, and there may be cases where RVM lacks the flexibility to do what's required, but I've never run into them.

[0] http://rubygems.org/gems/bundler
Officially, no. That's against the Apple developer guidelines.

Whether Apple will have the courage to enforce them is another matter. We've already seen evidence that their new "privacy nutrition labels" are sometimes inaccurate with no consequences for the app developers.
Sure, you probably don't want to run your business on it; we agree. I think it is a missing opportunity for DO to allow growing smaller projects to continue to stay on their platform.
>"If Microsoft had to pay the costs of vulnerabilities"

Yeah, ok but lets trade out MSFT for FOSS, Firefox or small iOS app developers.

At some point, we should ask to see if we are inadvertently advocating for scaring people into doing the right thing. Worse yet, for something that they couldn't see or anticipate.

What about the standards makers? Are they going to be held accountable too? When is the last time you've read OWASP articles? Have you seen the state of that sort of literature? Its a mess. Have you seen how arcane and arbitrary the NIST-800 series is? What is the limit to this sort of "accountability"?

At the risk of being even more trite, ideologically motivated statements like this look cool only because its on the internet.
Thank you! That's perfect! And a bit ironic that the RSS feed is on a Google product aka the company that kill Google Reader.
I have no experience with Microsoft documentation. Still, I don't expect you can extrapolate from aspnet core docs to the whole Microsoft docs including kernel, userland and UI, compilers, programming languages, gaming products, etc.

What other products with unusable docs have you had experience with? Can you point to some particularly bad examples from aspnet core for my own education?

Also, I'm curious about how awful/passable/good documentation is distributed among the many tech products Microsoft owns and publishes docs on. Do you know about any good docs from them?
It is a combination of both. Clicking this will deny the app access to the very useful IDFA identifier, so this part is strictly enforced.

However, when phrased like this, it does not JUST represent the access to the IDFA, it is a direct request from the user to not track you in any OTHER way either. And yes, the app can ignore that, but then Apple is free to deny it access to the App Store.
Preface: this is why people like to complain about YAML, but really I think it's a feature and not a bug that you can write strings in so many different ways, to serve the many different needs for entering text into config files.

This is probably not a common piece of YAML knowledge, but it's arguably better to use "folded" style for a password:

password: >-2\n
asdjoi'";j;oj;90\[2301@

Or use single quotes, which signals to the YAML parser not to treat any characters as special, but then you need to escape the literal SINGLE QUOTE character (') by doubling it:

password: 'asdjoi''";j;oj;90\[2301@'

This is completely valid yaml that reduces to the JSON equivalent:

{"password": "asdjoi'\";j;oj;90\\[2301@"}

And of course you can always write JSON syntax for when the text escaping gets hairy, because YAML is a superset of JSON.

Here they are together:

password1: >-2
asdjoi'";j;oj;90\[2301@
password2: 'asdjoi''";j;oj;90\[2301@'
password3: "asdjoi'\";j;oj;90\\[2301@"

See here (https://yaml-multiline.info/) for a summary of the various multi-line text styles.
The irony in this is that I'm pretty sure that 70's era string-based languages are better designed than many, many configuration file formats.
That is true. But liberal arts schools are also the least likely to be priced out by MOOCs. Liberal arts schools are more affordable than most, if you can get in.
No, it's not that. It's that it may very well be possible to trace this conversation back to a single person and that could easily jeopardize that persons employment.
So if I understand correctly, this experiment is demonstrating that prior to Bob's measurement the wave function is spread out between the labs. I don't think that is the same thing as being able to detect a non-collapsed wave function (the design just assumes it exists, and the outcome implies that it is a useful description).

Are you talking about something more than that?
The example they use is detergent because showing someone reaching for toilet paper and realizing she needs a refill isn't such an easy commercial to shoot.
An awful lot of people pluck down premium-level bucks for iOS, which is even more neutered than ChromeOS. Consumers have spoken, they do not care.
No, it's not "like OCD". For some reason people think OCD means "haha I like to have my kitchen pots organized" when it's really an often debilitating, life-changing disorder. Please don't contribute to the trivialization of the term.
According to SearchYC this has been posted twice

3 years ago (3 comments) http://news.ycombinator.com/item?id=79405

9 months ago (no comments) http://news.ycombinator.com/item?id=1115919
Bhutan seems (mostly) pretty nice.

Yeah, there's not a lot of them.
For now, yes. But the history of the Internet is one of distributed solutions winning out over proprietary walled gardens.

For instance, a lot of people are on niche or community-driven social networking sites, alongside facebook. If those sites could communicate with each other, facebook would lose a lot of mind share.
I think one could make a not-entirely-unreasonable argument that by streaming the DVD you're making an unauthorized copy of the data on it.

What are they doing, after all? They read bits off the DVD, make another set of bits which contains essentially the same information compressed, and transmit it to a remote location. Sounds like making a copy to me.
Kind of unrelated, but when he says it's a living document, he means it. I just watched him add a few bullet points and notes in real time. Google docs is pretty cool like that.
Your example relies on the idea that government negotiators will be more benevolent and peaceful - will work more towards the common good - in secret than in public.

Maybe that happens once in a while. The far, far, far more common case is that secret negotiations amount to a conspiracy by the powerful against the weak.
They're just left on the tables all day, and didn't end up getting in the way for us any more than a salt and pepper set would.
And man, is that title dense or what?
There are plenty of useful things to memorize that let you flat out skip steps. Some of this stuff might feel like party tricks, but don't assume people are using the same steps subconsciously.
Isn't the one mom and pop shop which benefits from social media an exception to the rule?

If you are a dentist in Scottsdale, Arizona, how many people could be talking about your business online to justify investing time in social media monitoring tools?
I used to work in NYC but I've been working from home for a couple years now for an agency based in NYC (I live in CT now). I make good money but I've been offered a 20k+ raise and other bonuses to work in the city. Barely considered it.
Restaurant owners will never pay waiters enough. They're too disposable. The only reason to want to keep one on the job long-termish/for better pay is that the waiter is well-known or is well-trained and knows a lot about how the restaurant operates. But they tend to float away anyways...
Ive been working from home since late 2006 until early 2011. I was pretty happy with it despite always having the feeling of not getting enough done.

I now work in an office in my own startup and simply love it. Conversations with other engineers, the whole energy of people working on the same thing in the same room and actually being able to differentiate between work and being at home are things i really really love right now.

I now have to commute 20min (one way) by car, but i dont really care. Sitting at home all the time and having your highlight of the day being a walk to the grocery store is depressing after several years ;)

I wouldnt want to work in a coffeeshop though, maybe as a writer, but as an engineer i need my large screens, comfy chair and big desk.
When they're out of money and they say they want to.
When companies use recruiters, they will typically pay a fee equal to 15% to 25% of the employee's first year salary. I'm sure HubSpot uses recruiters, and is used to paying $12k plus for top technical talent. The only difference here is that they are allowing non-professional recruiters to collect a fee for referring a candidate.
The problem is that it's an unfortunate situation, whether it's governed by laws of business or not.
Neat trick, if you're so inclined to use such tricks:

$ cat .ssh/authorized_keys
command="tmux new-session -A -s base" ssh-rsa [...]

Automatically creates or joins a tmux session named base, and disconnects the SSH session when you disconnect from the tmux session.

So, yeah, why don't we use SSH for more?
Is it really 20% turnover for knowledge workers or across the whole company? I am sure that turnover rate for the envelope stuffing must be very high. Those types of jobs always have high turnover.
Sigh... Amaercians and their second amendment.

There is so much anecdotal evidence in this thread. I thought that the HN community would have a greater adversion to firearms as even their ownership by a community increases the chance of fatal violence.
That's actually the most important reason to use SSL. I'd much rather have my HN account compromised than everything that shares a password with my HN account.
Demonstrable revenue boost? I'm not convinced, although I'm not a restaurateur. My argument: those annoying pagers/buzzers keep the party tethered to the establishment, which means that the guests are likely to

a) Sit at the bar and order a drink
b) Sit in the waiting area and read posters/chalkboards about upcoming events, happy hour specials, gift certificates/loyalty programs, etc.

Either way, the restaurant comes out ahead (especially at the bar, where alcoholic beverage margins make every restaurant owner smile). I wouldn't be surprised if a restaurant saw a decrease in drinks purchased if customers were allowed to freely wander beyond the range of those pager devices.
Perhaps Salesforce framed the message this way to avoid the negative publicity that comes with transitioning a free service to a paid service?

It may not be the most sound logic, but at least it would make some sense.
To add: this is Red Hat Linux 6 or 7, not Red Hat Enterprise Linux - I fondly remember RHL 7.3 in 2002 as the last RedHat I liked; updates were still through RHN or Red Carpet (don’t remember if yum was already used).

RHEL, Fedora etc arrived later.
Whatever you do with internally generated energy, you either get it out or it accumulates, overheating you.

You need 3-10 m^2 of radiators for every kW of power you use. If your ship is powered (I mean internal power, not engine exhaust) by a 1MW reactor, then you need radiators close to the scale of a football field pushing out waste heat, no matter what tech that reactor uses.
We have a handheld product (custom hardware) that we struggle to test. Currently it’s all manual testing but lately I’ve been wondering how to increase test coverage and automate it too.
> “Statements that are false” are an entirely different ballpark of discussion than “statement that incite violence”.

No they're not, instead they have a massive overlap. If I lie to my neighbor "Hey, Bob across the street has been stealing your mail", and my neighbor punches Bob in the face, my "statement that was false" led to violence and it can be argued that was my intention the whole time.
Socrate's demon not mentioned? https://en.wikipedia.org/wiki/Daemon_(classical_mythology)#S...
Scifi ships tend have engines with stupendous power ratings (Gigawatts and higher). Even with 99% of efficiency they'd have to shed megawatts of heat. Since there is no convective or conductive cooling in space your steady-state option is radiative cooling which is constrained by surface area, temperature difference and emissivity. You don't have much flexibility on the latter two. So you need to increase surface area. The ISS' radiators take up about 200m² and can reject 70kW. There are non-steady-state options such as sacrificial coolants or plain thermal mass but that would require extra mass, resupplies or additional downtime. In The Expanse the ships just don't have enough area considering they're powered by fusion reactors burning constantly.
I program in Haskell and quite enjoy it.
Exactly. The choosalicense site is designed to be neutral enough to avoid overt bias. It wouldn't work if it didn't appear neutral. But it is not neutral.

First of all, it says that the main default simplest license should be the permissive one. It chooses that first on purpose. Second, they say that you should use Apache if you care about patent issues when actually GPLv3 is arguably superior for that. So, they worked to actively relegate GPL to the last choice.

And you picked out the small text. The big text is "I care about sharing improvements" — what does that mean? It's much more wishy-washy than "I want to block the code from being used in proprietary projects" or "I want to require that derivatives stay free". The motivation behind the GPL is about freedom, not about improvements. But GitHub doesn't want to talk about freedom, they only want to talk about code improvements.

Anyway, it's already aggressive to encourage people to use GPLv2 instead of GPLv3, given that v3 specifically closes loopholes that GPLv2 has.

Anyway, it's not a lie… watch https://www.youtube.com/watch?v=-bAAlPXB2-c to hear the GitHub co-founder explicitly tell people to reject the GPL in the very presentation in which he announced the choosealicense site.
CryptDB doesn't use homomorfic encryption. It is doing sortable deterministic encryption. E.g. after encryption the server can determine whether a > b or a == b. They have a very good understanding of what data does it leak, when can you do that and when cannot.

In our db, random observer cannot see how data are ordered or whether elements are equal to each other.

Homomorfic encryption would be ideal of course, but it is slow and impractical for the moment
I appreciate how Japanese works can defy a canon. I am thinking of Tenchi Muyou, or the Evangelion reboots, or the endless doujinshi made of every story. Redo all the characters, if it's interesting. In contrast it almost feels like Western media and fandom is obsessed with finding the theoretical "correct" version of a story, and declaring it canon. Arguments over Star Trek physics, and "retconning" remind me of this. The fact that Legend of Zelda games cannot be rectified with each other doesn't bother me one little bit. Nintendo games aren't lesser because of it.
Fever and strong painkillers. Is almost certainly nonsense after a cursory check.
https://outline.com/enxGLX
My work over the last decade has also been in distributed systems and I completely agree most people don't need that scale. These new massive scale solutions are exciting for the few large companies that need them but it feels like everyone is being pushed onto these platforms as well—whether it makes sense or not.

Let me know if you end up giving Litestream a try and how it works for you. I'm really working to make the developer experience as easy as possible and I'd love to hear feedback.
Researching how taxes are calculated takes up valuable time and mental capacity, and you have to reeducate yourself every couple years on whatever new tweaks to the tax system happened.
Another whitepaper-based crypto project. Didn't that fall out of fashion in early 2018?
Yes, that was my point in the higher comment:

> Should also note that MasterCard crypto transactions almost certainly won’t be settled on the blockchain

This is just an exchange service where Mastercard collects exchange fees, in the same way that PayPal offers cryptocurrency payments.
This is C, not C++. Modern C++ is kind of a mess with how much stuff they’ve added to the language. This is not relevant.
They said "without justification"
If we don’t change, we don’t grow. If we don’t grow, we aren’t really living
Trixter, yes, I have it ready because I did all these audits already as part of company security policy; and not because of customers and I can share them on request.

A company that never did a pen test or security audit or doesn't want to share them doesn't give me much trust to use them as a partner.
Who would willingly make a new x86 design these days?

I would think this would crack ARM's control over their instruction set though. I can't imagine it'd be worth re-implementing literally the entire thing from scratch though when ARM will willingly sell you IP blocks, as opposed to Intel or ARM which will certainly not.
Even most ”normal” people (= people who dont care for partisan hackery) have lost trust, interest and willigness to consume modern agenda journalism. Where can you turn to for information in that case?

The only surprise here is that ONLY half of republicans actually believe these accounts.
Frankly I think it's more likely that they took it down because they want to sell more books: https://shop.economist.com/products/the-economist-style-guid...

The book has almost identical content from what I recall. I think they may have admitted defeat on the use of "he" for a hypothetical person of arbitrary gender.
Had Justice Thomas' opinion prevailed, most everything within POSIX was originally copyright by AT&T USL as part of System V, and would be owned by the current holders of that intellectual property.

Anyone using fork(), stat(), open(), or other basic parts of the UNIX development environment would be in violation.

Those copyrights were purchased by Novell at some point, and I believe ended up with Attachmate.

One would think that the C Programming Language is also covered by copyright via the K&R books, which would put anyone using printf() in the same position.

That is truly a nightmare scenario.
She was not a child when it happened, FWIW.
The dissenting opinion is stupid. Thomas may be a bad justice, but he has even less of a clue about software devolopment. Of course there is a difference between an API and the code in general.

This decision sidestepped the question of whether APIs are copyrightable or not by declaring that this particular instance was fair use.

Reimplementing interfaces has always been fair-use, they are definitions. Re-Implementation of these interfaces has been a cornerstone of FOSS since its very beginning.

> So if fair use is granted for theft of copylefted code in a non-copyleft manner, it doesn't matter heavily whether that was "declaring code" or "implementing code".

I don't think these words mean what you think they mean. There was no theft and of course there is a difference between declaring code and implementing code.

Shesh...
Run their own nodes on the respective cryptocurrency networks they use.
As the climber/founder speaking in this video let me clarify - I wasn't referring to any of the trust issues mentioned in the thread. I was specifically talking about the focus and clarity climbing brings and how important that is at a startup. While climbing you're 100% focused on the task at hand, which is unusual in the vast majority of our daily activities. The point was simply that when working on a startup, it's important to have a release to completely clear your brain of the clutter. I'd actually say the trust aspect is overrated.
It sounds like they might be planning to charge for the software, include (limited?) access to the source with purchase, and put a no-derivative-works-or-redistribution clause in the license.

Actual FOSS would be nice, but non-free software + source still beats regular closed-source proprietary software.
There are legitimate criticisms, but the way this is phrased is absurd. Security is always about tradeoffs - he's chosen his, and he's made you aware of the ones you're making.
Just curious but where do the funds go when the transaction is 'destroyed'?
Even more about money. My understanding was that NASA came up with a big, awesome plan for a reusable spacecraft kinda resembling the shuttle, and only doing stuff that NASA and their science/exploration missions needed, but they couldn't get anywhere near enough money to build it. So they went to the military to try and get some more money, and they said that they'd kick in some towards it if it could do these other missions they wanted too. They took it and ended up building something that didn't do anybody's mission really well, but it was the only way at the time to get enough money to get something off the ground.
So do you think a service that helps you narrow down the list of companies for you to work would be helpful?
I hope you ask Pando.
Does anyone know whether their changes to the BEAM ever made into the official Erlang BEAM?
c) Institute a Logan's Run policy where you get 80 or 100 years of good health and are then painlessly euthanized.

I think we can do better than c, but it's a lower bound: it avoids your concerns and is still a large improvement over the status quo.

I'd like to live forever

Curing aging doesn't let you live forever. There would still be diseases (at a much lower rate), accidents, murder, suicide, natural disasters, etc. All it would do is prevent the deterioration of our bodies and often our minds that generates large medical expenses, prevents us from being productive, and impairs our quality of life. It would also give us the option of living for several centuries longer than we do today, which we could take or not.
Ah, yes, if your site is uncachable anyway, then that really is the way to go. Caching two copies isn't unreasonable I guess, but in the context of Rails (which is the unstated context of this solution), it's more of a pain in the ass than it's worth.

[Edit: I updated the post to be clear that this solution does work if your page is uncachable anyway.]