skysight-inc/HackerNews huggingface dataset:
To add to the list of the multilayered problem:

- Sabotage and subversion. (It is easy to forget to add this one to the list...but there is probably quite a bit of this going on at various levels).

- Lack of "Jokers" or lack of the right kinds of them...? [1] [2].

The Jokers bit is interesting. To quote [2], "Jokers are crazy, sadistic bastards who care nothing about the group benefit (so they don't consume it), but they do care about destroying things. They usually do so while cackling and making bad puns. They closely resemble Cesar Romero, Jack Nicholson, or Heath Ledger (depending on the decade), or sound like post-Star Wars Mark Hamill (the best Joker of all time)."

Interestingly, in a public goods game involving Cooperators (your good institutional contributors), Defectors (your bad actors), and Jokers, there are three possible outcomes:

1. Without Jokers in the game, Defectors do better than Cooperators.

2. With semi-effective Jokers in the game, an indefinite cycle of (a) Cooperators doing well, then (b) Defectors taking over, then (c) Jokers beating out Defectors happens.

3. With super-effective Jokers in the game, they take over and beat out both Cooperators and Defectors.

[1] https://arxiv.org/pdf/1103.3257

[2] https://thegoodreads.quora.com/Why-The-Joker-and-Not-Batman-...
This type of attitude completely ignores regular desktop users who may one day want to use Linux over Windows.
Preface:

1. I use Arch Linux for my desktop and I like it.

2. I hate docker's repository systems (and other upstream packaging)

But this article writer sure is putting the maintainers on a pedestal.

More fundamentally, the maintainer is the primary line of defence and interaction between users and developers. Maintainers shield developers from uninformed users, allowing the devs to write software with less support overhead. Non-bugs are caught and filtered out. Low-quality bugs reported to the distribution's tracker often becomes a good bug when the maintainer reports it upstream.

...

Maintainers also shield users from developers, offering a layer of quality control...choosing a subset of the (subjectively) best software FOSS has to offer. Maintainers will disable features that they feel act in bad faith. Maintainers' greatest power is the ability to outright say "This is not good enough for our users"

Really? Then what about this poor sap who had the misfortune of releasing one buggy minor version, and is now forced to support that for the next 5 years even though the bug was fixed in the next version?

https://news.ycombinator.com/item?id=11452432

The maintainers actively tried to sabotage his attempts to tell people to upgrade to a new version in the name of 'consistency.'

Sure, consistency is great, but only if we (the maintainers) don't have to do any work (such as backporting). We offload all the supports to the developer and have him do support work for us. Then when he complains we will call him a whiner and laugh him off...
When Uber Leaves, What Happens?
Sure, there are a lot of potential things to do - either by enumerating towards the full "brute force" loss partway as I think you are hinting toward, or treating as a subsequences, or something else [0, 1, 2]. The point is, IMO RNNs do need some kind of structured loss (more than per step likelihood) to be competitive with HMM approaches using Viterbi decoding, in addition to some sequence smarts (such as beam search) in decoding.

At least in NMT, enumerating the possible decisions as 3n + 1 is almost impossible since the softmax size is generally the memory bottleneck in training - and a bigger vocabulary is typically a huge win. It is more feasible in speech, but often your labels are themselves triphones and you end up with a pretty large vocabulary too.

Figuring out how to get RNNs closer to on par with DNN-HMMs with Viterbi decoding (or full on sequence training [3]) through something like "deep fusion" with a language model (or something else) is something I am very interested in.

[0] http://arxiv.org/abs/1312.6082

[1] http://arxiv.org/abs/1511.06456

[2] https://arxiv.org/abs/1511.04868

[3] http://www.danielpovey.com/files/2013_interspeech_dnn.pdf
It is like they want to prevent people from using password managers and strong lengthy passwords!
> Except, Google themselves now do "google-chrome-autocomplete-off" and "both" and similar values instead.

That's clearly a suboptimal practice by Google's web team. Which doesn't make Google's Chrome team wrong, but maybe the latter should have a word with the former.
How the Windows Subsystem for Linux bridges file systems
If you follow the link to the next discussion it quickly becomes pretty clear that it's a bad idea: https://bugs.chromium.org/p/chromium/issues/detail?id=587466

Anyone who has to fill forms for other people is going to end up putting his own personal information into the fields by mistake.
How many people are afraid to speak out here, despite disagreement?

What, with the horrible consequence of being downvoted looming over them? Probably a lot fewer than are afraid to speak out about charismatic abusers who have threatened to ruin their personal and professional lives if they speak out.

This is a pretty classic example of a common phenomenon -- to paraphrase Alana Massey, people often mistake the discomfort of being confronted with their own violence for the suffering they caused by it. Appelbaum's "victimization" isn't remotely close to the suffering of the his victims.
Thanks! Can't wait to dive in
That's the online equivalent of bombing a church. Assholes.
Yes, they/we must pay the rent for their Manhattan location...
The one that I wouldn't mind changing is when the site somehow blocks pasting a password into the field. Yes, I'm not typing it because I use a password manager thank you very much!
The issue with YT isn't with people getting access to ripped content. It's with Google running occasional ads on top of that content, and getting "access" to advertisers' big, fat, greasy dollars -- without any form of compensation (or yielding of rights of artistic control) to the creators.

Unless they take very aggressive action to force Google to do otherwise, that is.
LiquidPiston X Mini 70cc SI engine animation
BadTunnel Vulnerability Hijacks Network Traffic, Affects All Windows Versions
If I remember one talk correctly ZFS was designed with persistent memory in mind, so I don't think SSDs are far out of their design thoughts.

[edit: it was a BSD Now episode]
Derpy enterprise folks have had too many traumatic turns with Microsoft tooling. There is a reason for this apparent or perceived "stupidity". It isn't stupidity. It is caution.

The trauma really began with VB6, then ASP, then continued with Webforms, then Silverlight, then WPF ... if you thought that the current cohort of JS developers have framework fatigue, you should see surviving Microsoft "derpies" nursing technical debt such as LINQToSQL or strange extensions of Sharepoint.

The Java folks were less traumatized in this regard. But they had their moments with EJB (entity beans anybody)?
Emoji reporter for mocha
Confident Cannabis (YC S15) is the stock exchange of weed
How hard could it be to get people to believe a fake political poll?
11 Incredibly Valuable Insights You Can Get from Website Surveys
I read "edit users profiles" to mean their Chrome profile, so my mistake in misreading that.

(That said though, doesn't Autocomplete in chrome only work if you select the text in the drop down and hit enter/tab? For an address field, for example if you type "123" and the box appears to select "123 Maple Street", can't you just bypass that entirely by continuing to type and not clicking on the suggestion?)
Counter argument: Chrome doesn't ask you, and they don't provide any way for you to respect the standard behaviour.

If it breaks websites you use then your only option is to completely disable autocomplete.
As to your latter question I think it's a kind of elitism. "Real men code with vi" type stuff.

I've always loved and always been a fan of OSS, but at the same time I have never been a fan of the arcane obscurantism that goes with it. I used to see it as just a function of not having time/energy to polish UX, but now I think it's somewhat intentional. They like things to be arcane since it's a status symbol to know arcane things.
https://github.com/defunkt/dotjs
The TSA Is Bad Because We Demand That It Be Bad
That may be true but with a pulled db backup and a good recovery strategy you'll be back up relatively quickly, without you'll be DOA.
The point isn't to eliminate income equality. That's next to impossible in a capitalist society with a relatively free market and wealth ownership.

The point is to raise the level of the bottom to something people can live on safely and with some level of dignity.

And with UBI in particular, it's to shift the impetus of your efforts from basic survival to improving your lifestyle from the lowest common denominator. People make shitty decisions with a gun to their head--with some room to experiment they'll usually be more successful.

Further, they might find other ways to individually create societal value (art, science, invention, philosophy) than just simply making their employer money. The only way you can do that right now is if you're already well-off or if some committee somewhere agrees what you're doing is valuable and subsidizes it. That's not a great way to innovate.

And they might not create value. Some people will sit at the bottom. But that needs to be OK--they do that now anyway while being a distinct drain on a society that wasn't built to accommodate that basic human nature. Nothing is perfect.

Most people work for their own self-validation if you give them a chance, though. Think we've all had that experience during time off where you're eventually compelled to do something productive just so you can know you did something.
One is `autocomplete`, the other is `aria-autocomplete`.
Actually the nice thing about gravitational waves is that we are sensitive to their amplitude, which scales as 1/r, and not to their energy, which scales as 1/r^2.
Well, there’s no alternative.

You don’t want the Google search box, or the hidden textfield in Google Docs, or so, to autocomplete.
Senate Votes to Require Women to Register for the Draft After January 1, 2018
I don't think it's so black and white. In this case, the "punishment" isn't literal. It simply comes in the form of more grunt work, which people trust you with because you have taken it on before and did a good job with it. You may actually be rewarded too when the annual review comes, if you know how to spin it.

Furthermore, grunt work can be an excellent opportunity to shine. For example, you can figure out a way to automate it so that the next person who works on it (which may be you again) has to spend only a fraction of the time on it. Things like running reports or generating documents tend to lend themselves really well to automation, and a little programming ability can take you a long way.

So yeah... think twice before turning away grunt work, even if you believe that you may be given more of it in the future if you agree to take it on now.
Why use a Word document? I put all my security passwords—especially the ones that won't autoflll or that make me change them often—into a Google Docs spreadsheet online. That way I can get to my passwords from anywhere.
Well, you might think it's a distinction without a difference but in fact it's not a leak. A leak only occurs when the handle one might use to deallocate memory/resources is itself deallocated.

Whether "I added one FramistanObject to the FramistanObjectLog for every single HTTPConnection" is a logic error or not depends on what the intended design was.
No, it's an outward facing password to preview non-live sites, like Shopify or Squarespace have. More of a beta code than a password.
I'm guessing the archive includes some ISIS sites that this person finds objectionable? Idiots.
There's interesting restaurants in the (Chicago) suburbs too. They might not be as gimmicky (no "say the secret password to get in" types), but you can find just about every cuisine and the food is usually just as good.

Museums are great, but they're something I only get the urge to see a couple of times per year.

Live music (and you should have said shows/theatre also) is definitely lacking, but if I want to see that, I can drive an hour to go downtown or take the train to see them. Even when I was super gung-ho about going to those, I didn't go to more than a show per month. And several of those were in the suburbs (Ravinia, Oddball Comedy Festival, Chicago Improv, etc).

And parks? Except for the beach at Lake Michigan, the suburbs has the city beat in parks by a huge margin. Tons of forest preserves and parks out here, plenty to explore.

There's a lot more smaller but still enjoyable things in the suburbs too, community theatre, smaller concerts, sports events that don't cost a minimum of $80 per ticket, and town festivals which I prefer to big city events because you can actually walk without being constantly smushed by everyone else (literally true in Taste of Chicago).

But yeah, those don't want to use cars need not apply. And granted, there will be people who want to see a show 2 or 3 times per week and visit a museum at lunch every other day, who would of course prefer living in a big city. But it's not for everyone.
Given the autocomplete detail tokens[1] - my first thought was

autocomplete="section-disabled disabled"

Or something similar.

[1] https://html.spec.whatwg.org/multipage/forms.html#autofill-d...
I feel like this article is sort of attacking a straw man.

> The promise: Sandboxing makes you immune to bad ISVs. The reality: It protects you from some things and not others.

Well yeah, but the same could be said of maintainers. Maintainers let things through all the time, and sometimes they cause problems (hello, Debian weak keys).

The reality is a bit complicated, and it boils down to something boring like: if the maintainers are better than upstream, maintainers are good, and if they are worse than upstream, then they are bad. But that is both tautological and vacuous, so it is not especially useful insight.

The real insight is this: there just aren't enough maintainers to go around. Debian has 1500 contributors and 57,000 packages, which is 38x as many packages as people. Now maintainers have a lot of tooling to make that more tractable, and upstream developers have their time split between multiple packages too, and some packages are important enough to get the attention of several maintainers fulltime. But do we really believe 1/38th of a person is judiciously considering how to overrule upstream's decisions, attentively investigating user bug reports, and so on?

More likely, the maintainers do not even claim to be doing that, because they have not packaged the software at all. I use lots of unpackaged software; until recently nobody was packaging Chromium for example. Java packaging is really unreliable. And so on.

Ultimately, Ubuntu Snap exists because there is a lot of unpackaged software, and a lot of software packaged poorly. It would be nice if we could wave a magic wand and get 38x more maintainers, but we cannot.
i.e. probabilities.
I � Unicode
People forget that Microsoft has perennially had their Cairo/Object/Whatever FileSystem in development.
> In general, physicians, like all humans, are incompetent and self-interested

Self-interested, perhaps. But assuming that physicians are representative of the broader population when it comes to incompetence is really poorly-grounded.
We did, which caused the problem. (We had a "show password" option, but even if we didn't, it'd still be visible in the HTML)
Google isn't the new Microsoft, it's the new Halliburton.
> Well, there’s no alternative.

Sure, there is. You could do a meaningful semantic autocomplete tag that isn't one of the recognized ones, rather than a variant of "no, really, don't autocomplete this". (Actually, "body" is probably not a bad practice, but the other one was.)
I find that there's far more times I'd rather have autocomplete than have it actually disabled... I hate when sites force it disabled, when there's no real reason to, and as a user it's irritating.

The only time I find autofill annoying is sometimes (on my phone) lastpass will fly open at inopportune times, when entering something in a password field that's not really a password, etc.
Yep.

tl;dr - people over value loses, and undervalue gains.

If we have a coin toss game where head=5$ for me and tails=5$ for you, you will only play if the game is something like 70 / 30 in your favor.
Check my profile and drop me a mail with stuff you would need for that I can tell you if it would work.
Take a day off and get familiar with ansible, it will save you tons of time in the long run and simplify your dev/staging/prod environment for years to come
iOS and Android stats (we have seen some iOS 10 already)
Design of breakout boards and open-source hardware
>For example: --some-long-option comes to mind, or lack of proper manual pages ("see the texinfo page"),

What are you even talking about here? man/info works wonderfully, if I want more readable information a terminal sure as hell isn't going to give it to me easier than searching a wiki. And solaris absolutely had problems with documentation on their larger packages.

> lack of backwards compatibility support

Hardly even a real issue if you actually maintain your damn systems more than once every half decade.

>tar -z (tar is a tape archiver, not a compressor!)

... It still is a tape archiver AND a compresser AND a 100 different but completely valid and usable things.

ZFS absolutely is usable.

Why do you enjoy DBX over GDB?

SMF? One would think you would love and embrace systemd.

FibreChannel stack that works?
https://wiki.archlinux.org/index.php/InfiniBand

I can't refute all that you have said here since I am not familiar with all of it. But, have you considered you are just doing it the wrong/difficult way?
The rationale for ignoring autocomplete=off makes sense to me. What I don't understand at all is the suggested "workaround" for disabling autocomplete:

> In cases where you really want to disable autofill, our suggestion at this point is to utilize the autocomplete attribute to give valid, semantic meaning to your fields. [...] As an example, if you have an address input field [...], you can give it semantic meaning that makes sense relative to what you're asking for: e.g. autocomplete="new-user-street-address". If Chrome encounters that, it won't try and autofill the field.

So essentially they encourage authors to make up random, nonstandard values for the attribute that may or may not do what the author is hoping for.

I don't see what this will archieve except making the autocomplete attribute a pain to use in practice.

(Which might be what the Chrome team intends, but even then, a more straight-forward and more honest way would be deprecation.)
This is why we recently retired FreeCodeCamp from Changelog Nightly[^1]. It was in the Top Starred list each and every night for months on end. Impressive, but not very interesting.

[1]: https://changelog.com/recent-improvements-to-changelog-night...
Thank you for listening! I wouldn't be surprised if there were some sort of legal action eventually, but I also wouldn't be surprised if there weren't -- as mentioned, it's unlikely he left any hard evidence of wrongdoing. Though of course a lot of people who thought they were alone in their abuse are now learning that this was systemic, so they may be able to piece something together.
Reference counting is a form of garbage collection. You can have avalanches of objects being deallocated when as a consequence of one object refcount reaching 0.

You don't want any allocation or deallocation when you need realtime performance.
If you allow it to remember your login credentials it will autofill any input that it thinks is a login / password.

That leads to some random behaviour.
cd /etc
git init
git add *
git commit -am "before i screwed up"
We'd probably disagree on what determines a good reason. I've encountered plenty of admins that need/want god-like permissions in the app they are paying me to write.
I double checked my drive and you're correct with regard to mobile backups. That's reassuring.

It would be nice to have a utility to give a definitive diff of what's on your hard drive that's not on your: Time Machine drive / [Carbonite, Backblaze, etc] backup.
Linked-Out: Microsoft’s acquisition could open a box of trouble
Or if the TS declaration file format gets widespread adoption among flow, babel, ECMAScript etc.
You could argue that, but the user who owns the web browser has all the power in this situation. It's an arms race the website operator cannot win.
I can't check right now, but it's possible that the patent predates my use of the technique. Even if not, I don't know how I could prove it.

By the way, it wasn't done in code; I did it manually in Ardour [0].

[0] <https://ardour.org/>
...and if you only have $20, you cannot spin the wheel at all.

Quite a lot of decisions in life are barred by the severity of the penalty independent of the possible reward.
> Recent Intel x86 processors implement a secret, powerful control mechanism...

Recent is overflowingly unhelpful, considering AMT (a part of IME) popped up in ICH7 back in mid-2005 [0]. It is unfortunate that Doctorow is associated with this rubbish journalism.

For what its worth, anything that has DMA can takeover a CPU that is reading instructions from RAM. AMT/IME are just explicitly intended to do that.

For those concerned, and probably rightly so, about AMT/IME, the simplest solution is to use a non-Intel NIC [1]

[0] = https://en.wikipedia.org/wiki/I/O_Controller_Hub#ICH7

[1] = https://software.intel.com/en-us/articles/intel-vpro-technol... ["Intel Active Management Technology communicates only through the onboard network interface of Intel vPro technology. Additional wired network interface cards are not supported and are ignored by Intel AMT."]
Problem in Rust adoption
When I fall into this line of thinking, I sometimes realize that the efforts I spent building my own thing from the ground up gave me a lot of insight into how the thing worked, what tradeoffs existed at a lower level, and it was extremely beneficial to have spent that time, whether I use what I wrote or dump it for a packaged solution.

Do you think you were able to analyze your choices better, or understand the systems better, use them better, have more insight, because you spent time up front doing your own thing?

I rarely (if ever) feel like time I spent that way was wasted.
hey, we have the same logo

https://feedbackboost.com/

font-awesome FTW!
In some cases because their legacy systems can't support long passwords. I know my previous bank was restricted to 6 digits (maybe even just 4). Their solution was to add in those annoying security questions like "What was your first dog's name". Sigh.
I think that these devs writing spaghetti code to stay indispensable should never get their code into the codebase through code reviews. Then that person would fail to contribute anything.
The maintainers actively tried to sabotage his attempts to tell people to upgrade

Ah, poor maintainer. Releasing software with a self-destruct timer is not an acceptable way to "tell people to upgrade".
Three Gears Are Possible – Numberphile
i wish there was a way to 'force mono' on youtube so i could get the same audio from two sides of my headphones.

sounds like a really interesting talk, but it's painful to listen to from only 1 ear.
this is pretty good! haha i am gonna use it (:
Can you share what you were doing, and what they thought you were doing?

Do you also use Mailchimp to send marketing emails?
Welp, I upgraded from the previous version and I cannot open my connection file with this new version. I may be an uncommon user because I have an encrypted connection file. Just a warning to existing users who may be upgrading.