jkeisling/hacker-news-corpus-2007-2022 huggingface dataset:
Not the first time, but possibly the biggest thing I've drawn in it...

There definitely are some weird things when you try to plot complicated things, fighting with weird placement, clusters etc. But not sure if it's me or Graphviz to blame for this. But I don't really know a better tool. If I knew how the diagram would look in hindsight I might have drawn in manually in inkscape or something, but when I started I didn't know what I would end up with, so needed to be an automatic tool :)

To minimize the manual work, I ended up with a mix of DSL in python and raw graphviz commands: https://github.com/karlicoss/myinfra/blob/fc6345c31c4e49b534...

Depending on the things you want to represent a better fit might be force layout, for example something like https://observablehq.com/@morvasaaty/d3-force-notes
It guess it's not hard to put a deletion timer and send warning emails before actual deletion. Not every service out there requires you to send an email to delete your account.
Are they mechanical keys?
I would not accept your wager. That being said if this was a “really big problem” I’d bet you that most developers on HN would have an idea how to address it.
> and expect nothing in return

Aside from the expectation of unwavering loyalty to the Communist Party of China, you mean.
Firefox already lets you disable that using the browser.backspace_action setting in about:config: https://support.mozilla.org/en-US/questions/924490
Was anything they said here particularly sensational? They didn’t even mention the A word (aliens), just pretty much stated what happened.
Especially now that Jira is removing it's self hosted option, someone should be able to come and fill that niche. It'd be surprising to me if that niche is unmaintainable these days.
Seems like a reaction to yesterday's Google post.

Does anyone know how interviews at Apple and Facebook are like? There are often praises of Microsoft's interview procedures and bash on Google's on HN. Wondering what these two other companies are like.
Well, there was - web apps, but discovery/market outreach, payments management, versioning and distribution are all issues that the App Store assisted with/handled thus warranting most of the 30% cut.

In this case, there are other forums and other ways to get "helpouts" not to mention if it really does take off, expect other major sites to launch their own helpouts efforts and ignore Google's offerings.
If I have two candidates and the only signals are (resume, portfolio), then I will select the highest signal. I am sorry, but I can't in conscience decide to take someone without proven work over someone with proven work without other information.

If your resume is significant, then I will probably add to the signals with a phone call followup. I'm not looking to create false negatives.

I also want to point out that taking some time to develop a small and interesting project (say, a pure left-leaning red-black tree with deletion - not much code, but tricky to get right) does not take that much time and massively demonstrates your capability over having nothing at all. It also demonstrates your social awareness of the state of the field when you have a github account with projects in recent technology.
As a Soviet immigrant, I take issue with the realism of your claim.

Yes, the country effectively had closed borders, and yes, it was downright impossible for most people to leave. A trickle of emigrants who were begrudingly permitted to leave officially began in the 1970s owing to international Jewish repatriation policies and so on, but that was not an option for most people.

Nevertheless, to suggest that people were simply shot for attempting to leave is an absurd level of hyperbole. They weren't shot, they were just prevented from doing so via the usual bureaucratic means.

There is the small number of people who attempted a beeline across the border - similarly to the Berlin Wall climbers - past the spotlights and the guards and all. Thankfully, there were not many of them, as this is a very stupid approach to crossing any national border anywhere. The American-Mexican border may prove to be an unusual exception.
It's hazing. They don't need to accomplish things, they just need to work hard. A banking intern acquaintance of mine recently bragged to me that he was up until 5am printing and binding things.
Some things are cheaper off Amazon, yes. But for many people, myself included, it's far easier (and sometimes cheaper in the end) to buy from Amazon anyway, because the stores that sell them may be very far away from where we live. I'd rather pay $5 more and get it in two days than drive 50 to 150 miles each way to a store.
Given how many times this has come up on this site, it is becoming more akin to beating a dead horse and may serve to simply annoy and hurt the 'women in tech movement' if you will, than help it. I have yet to see proof of causation between male social tendencies in tech industry and a barrier to entry for women in tech industries. Anecdotes are not substantial. As you say, so what? Does it all have to be about you?

I have a hunch that on account of the fact that your cousin is female and has engineering proclivities that you will give her significant unabated attention, hell you swore before God...This all really because she is female regardless if reality requires extra help or not (unproven as of yet). I'm pretty sure that's sexist entitlement.
Like making social networks entirely responsible for the content posted by their users so that it’s impossible to grow beyond a certain scale and still be functional

How would that fix the problem of Turkey's government controlling what gets posted and what doesn't? That'd exacerbate it.
> "The winning specimens are donated to the animals at the Alaska Wildlife Conservation Center"

Said enough
Around that same time the fart app on Apple was bringing in 10k per day.

https://www.wired.com/2008/12/iphone-fart-app/
Friday a cop was murdered at a traffic stop [1].

The same day a cop was killed working security at a high school basketball game [2].

We need a publicity machine to remind people that cops do many positive things and pay great sacrifices.

[1] https://www.whsv.com/2021/02/28/community-members-come-toget...

[2] https://www.nola.com/news/article_1697430a-7953-11eb-a434-77...
Why not? You can now have all browser vulnerabilities directly in your chat app!
Definitely extending the usefulness of the analogy, but when I am riding my bike a lot and then take a break for repairs and walk more instead, I quickly get sore. Even after walking distances that I dont normally get sore from if I am bike free for a while and walking more regularly.
The problem is that chipmakers have historically made their development environments closed-source and, often, not very pleasant to work with. Maybe this is more of a problem with demonstration boards meant primarily for embedded systems people, but if you rely on TI, for example, to provide a compiler, they'll give you a closed-source IDE for their own C compiler which may or may not be especially standards-compliant.

I hesitate to imagine what it would take to get a hardware maker to contribute patches to LLVM.
I posted a question for the co-founders, it's next to your comment. Would you mind taking a look, please?

https://news.ycombinator.com/item?id=26298288
I felt the same. It was good for the basics, but lost me when it came to objects and classes and more creative parts of programming.

I tried out a few Ruby classes just for the heck of it, and with Ruby, somehow things fell into place.
The only thing the average web user would take away from such a popup is that github.com is annoying or spying on them, and then proceed to bombard github with messages to knock it off (reminds me of when a blog temporarily became the #1 search term for "facebook login", oh the hate that blog received for "breaking my Facebooks")
Its really pretty simple. Mr. Torvalds has a community and communities tend to defend their own. Happens in politics all the time because that's what humans do. Zed doesn't have as big a community and he offended some in the Ruby community. I think Zed's lecture in Toronto was an amazing presentation on values, but I've not read his books.

Its also why people say they "hate" a politician, leader, or band without listening to one word they say or believe snippets represent the whole of a person. The group think spreads quite nicely. At the end of it all, there is so much information and we have so little time, we outsource some of our beliefs. Comedians tend to use this to craft some jokes and sometimes abuse folks. For example, President Ford slipped a couple of times in slick shoes. Chevy Chase made him out to be a klutz and un-athletic on SNL to great merriment. President Ford was probably the most athletic President the US has had. He played linebacker in American Football and was consider a decent athlete.

My Dad was not a fan of this and did tend to scold his children that "if we were going to hate someone, we better damn well know why". I do admit to failing at this since there is so much, but it is a good lesson and tends to result in new joys.
"Remote Server" Doesn't necessarily mean "Production Server"
If I were Github I would redirect the attacker back at one of their own resources.

A attack reflection of sort.

Edit: You're technically not attacking you're reflecting if the attack stops there's nothing to reflect.

Just like in martial arts you don't just take a beating you defend and return the opponents attack back at them. Seems fair to me.
I use ssh + tmux + emacs. Security policy states no local copies of development files are allowed at my workplace without special authorization, which I never bothered asking for.

Migrated my emacs configuration to the remote server as a git repository, along with any programs that aren't available (e.g. git, which I use for unofficial code; official code is managed via perforce). Use GNU stow to move those configurations and binaries to the right places. If I need to move non-confidential information around I collect it in an emacs buffer and then use M-x compose-mail to send it out. The home directory is an NFS mount so I can also mount my home directory and exchange files that way. Etc, etc.

I also set up a lightweight Arch virtualbox VM that I SSH out of, because I really don't like the available Windows terminal applications, and every so often I need a local Unix box for some random reason.

A lot of my coworkers use Sublime and remote file editing, but I work faster when using Emacs (comint-mode is a godsend). We mainly work in Perl, Javascript, and HTML so none of the bigger IDEs are really appropriate.

Edit Since people seem more interested in the Sublime workflow, I asked for a few more details. Coworker replied:
"Sublime SFTP [...] you might want to mention that the only advantage to SFTP over remote mounting the server is the save time, as with SFTP, you save local and push in the background, meaning frequent saves don't constantly stall workflows. Otherwise, there is no real advantage over just mounting directly."
It is worth noting that he is working on a Mac, which has some severe bugs [1] when it comes to NFS mounts, and Samba has some latency issues in this instance.

[1] https://www.google.com/search?q=nfs%20slow%20mac
Or Washington, DC until 2012:

http://www.prgsonline.org/

Not that it's even remotely comparable. DC's air quality in 2012 was still unimaginably better than Beijing's. (I say this having experienced both.) But still, these things can move slowly.
Sure. Couple of scenarios where I've seen people working on a server and why that's bad:

1) The developers in this company that work with ColdFusion develop their software on a dev server because they would otherwise require expensive licenses for each dev machine. This means that devs often find themselves editting the same file. It also means that one dev can break the software for all other devs. Last but not least, it makes version control a ton harder.

2) Another scenario is where you fix a bug on the production server to roll out a fix as soon as possible. Sometimes this is acceptable, but there's a big risk because you no longer have the ability to test the code first. This also makes version control harder, because the next time you deploy your code, the changes will get overwritten.

3) Working with a remote IDE or just having your own development server: doesn't really make any sense, most devices (laptops, PCs, tablets) can run some kind of IDE/editor locally and allow you to run the code locally. Using remote software only adds a huge dependency on having a working internet/network connection.
Hey,

That's a fair question. I wrote the open letter and sent it to RMS in addition to publishing it; given that RMS doesn't frequent HN, it seemed insincere to do otherwise. I did not ask for explicit permission to publish his one-line response; that said, this was a response that I had heard RMS use in conversations while he was here, and did not feel that there was any reasonable violation of privacy in publishing what I considered to be a boilerplate response.

As to my intentions: certainly, influencing RMS would be fantastic; that said, from reputation and from meeting in person I've found RMS to be a difficult person to convince (I tried inquiring about his position on certain issues in person, and was interrupted/dismissed several times until I gave up). More realistically, I was looking for a way to collect my thoughts on the matter and did not expect quite this much attention. If I have at all influenced any Free Software advocates that the best argument for their position is a dignified one (cynicalkane proposes William Buckley as an example), that would be a happy accomplishment.
drew from dropbox here. i hope you guys can give us the benefit of the doubt: when something pops up that encourages people to turn dropbox into the next rapidshare or equivalent (the title on HN was suggesting it could be the successor to torrents), you can imagine how that could ruin the service for everyone -- illegal file sharing has never been permitted and we take great pains to keep it off of dropbox. the internet graveyard is filled with services that didn't take this approach.

so, when something like this gets called to our attention, we have to do something about it. note that this isn't even by choice -- if we don't take action, then we look like we are tacitly encouraging it. the point is not to censor or "kill" it (which is obviously impossible and would be idiotic for us to try to do), but we sent kindly worded emails to the author and other people who posted it to take it down for the good of the community so that we don't encourage an army of pirates to flock to dropbox, and they voluntarily did so.

there were no legal threats or any other shenanigans to the author or people hosting -- we just want to spend all our time building a great product and not on cat-and-mouse games with people who try to turn dropbox into an illegal file sharing service against our wishes. (for what it's worth, dropship doesn't even work anymore -- we've fixed the deduplication behavior serverside to prevent "injection" of files you don't actually have, for a variety of reasons.)

that said, when we disabled public sharing of that file by hash, it auto-generated an email saying we had received a DMCA takedown notice to the OP, which was incorrect and not what we intended to do, so i apologize to dan that this happened.

(*edited the last paragraph: we didn't send a takedown notice, we sent a note saying that we received a DMCA takedown notice, which was also in error)
This is my point in a comment in the post, before reading the comments here in HN. Burning books because they have forbidden knowledge.
Getting in is really a step number 1. Your real goal should be making your "core" idea for the business a success. Being a single, non technical founder in an environment that is very, very technical will present you with a massive challenge ahead...
So, good luck...
He has sent a bunch of them home. The number is down significantly from when he took office, and most of the remaining prisoners have no country willing to offer them asylum. I have a big problem with gitmo but the Obama admin did try to push on it for quite a while before apparently concluding they'd dumped enough time and capital into it.
It is interesting. For the first few years My education was very unstructured, I'd learn new stuff as I found out about it. I think after 3 or 4 years I started to get into the habit of reflecting and defining learning goals the day after new years. I really enjoyed this, it's about the only new years resolution I've ever been able to stick with.

Last year I did this and bought my books and then never read them.
AIM used to ask for a cryptographic checksum of a randomly chosen byte range of the AIM executable. The Gaim (now Pidgin) developers had to set up a server that would return checksums on demand. This doesn't meet your requirement of the verifier needing a small key.

Given that Dropbox apparently has no qualms about perjuring themselves in order to stop Dropship (or, as discussed in an earlier thread, lying about their security measures in order to defraud their customers), they could probably also take retaliatory action beyond just denying service to the user. Here are some possible retaliatory actions they could take:

* they could publish the user's private files, or simply look through them for the user's credit card numbers.

* they could sell the above data to the highest bidder.

* they could use it to attempt to impersonate the user to their bank in order to empty their bank account.

* they could randomly corrupt the user's data. (This might require a backdoor in the client software.)

* they could wait for an unusual volume of requests from the user (perhaps indicating that the user was trying to restore from backup) before terminating the user's account without warning.

* they could carefully comb through the user's files looking for evidence of any crime (illegal drug use, underage drinking, copyright infringement, possessing seditious literature, importing obscene material, defaming Islam, apostasy, embezzlement, tax evasion, whatever is the biggest no-no in their locale) and anonymously tip off the appropriate authorities.

* they could insert faked evidence of such crimes into the user's files, and then tip off the appropriate authorities.

Perhaps potential Dropbox users ought to be wary. This is a second data point in the company's history of seriously unethical behavior; one hopes they wouldn't engage in any tactics like the above in a dispute with a former user, if their extremely polite requests failed, but my experience is that people who behave unethically in medium-large ways often behave unethically in larger ways as well.

Caveat utilitor.
I agree that the removal of the code from your site is not censorship...

Disagree. Of course it's censorship. It may be justifiable, and the content in question may be against Dropbox's ToS, but it's still censorship: Dropbox is removing access to content it does not like.
There are no performance implications for Scala apps.
But CAP_SETUID, unless I'm confusing it with something else, can be used to set the UID to 0 and thereby gain all the same privileges as if the program had been started as root, can't it? Presumably it has some advantage that I'm not getting – does it have to be combined with e.g. SELinux to be useful?
"until they offer ISP"

https://internet.org/

Also, in some countries such as Germany, WhatsApp serves as a virtual mobile provider.

https://gigaom.com/2014/04/08/whatsapp-becomes-a-virtual-car...
I haven't, most of my experience is VMware (on server farms) and VirtualBox on desktop.
A bruteforce attack against the PSK handshake requires only a single handshake to be captured. There are no known techniques to speed up the attack if more handshakes are captured.

Man-in-the-middle attacks against WPA are not trivial at all. The client and access point perform mutual authentication. If you don't know the password, you can't put up an identical rogue access point. The passphrase is never explicitly included in the handshake, only in "protected" forms (in challenge/response messages).
In addition to this, the release duration is somewhat experimental.

Why such short support windows? The strawmen of three
months between releases and a one month grace period are
ridiculously short support windows. The reason I propose
them is because- like I mentioned in the design goals- we
want the smallest delta from how people work today. Right
now, there is no concept of stable versions, and we're
trying to introduce it. Starting off with a more standard
support window of something like two years would be a
radical shift in how library users and authors operate
today. Three months is very short, but it's long enough for
us to test the process. As time goes on, we should have
serious community discussions on how long a support window
we should have. (I, for one, am fully in favor of extending
it well beyond three months.)
I think you misunderstand the architecture of Nix. Every package in Nix gets put into an immutable /nix/store. Packages are identified by a hash of their contents, so a small mutation of any package definition gives it a new identity, and thus, a separate package derivation.

Every package in the store has exact dependencies - they reference the hashes of other packages only. When a package is built with Nix, only the directories for these packages are exposed to the chrooted environment in which the build occurs - so it is simply not possible for some randomly added junk in the filesystem to make it's way into a nix-defined package.

Contrast this to building software on another machine, where I might depend on "glibc" version "1.0". The combination these two values hardly represents a unique identity, as I could make any random package that fits those requirements. It's much more difficult for me to create a package which results in an hash collision though.

One thing that makes the other systems so unreliable is the presence of multiple repositories. If you were going to deploy packages from a single repository, then you can do careful planning in such a way that packages do not have any collisions. Assuming no user mutates the directories under control of the package manager, such system will also be effectively reproducible. Current mainstream distros work surprisingly well because they basically use this model, where a default repository provides most users needs. These distros quickly break down when you start adding third-party repositories which bundle alternative compilations of the same software that sits in the "official" one.

Basing packages from hashes (identity), rather than names and numbers, and making sure all of the files for each package is held in an isolated directory ensures that collisions won't happen, even if two different repositories provide the same software name and number, they are represented by different hashes, and will be treated as distinct pieces of software.