skysight-inc/HackerNews huggingface dataset:
> We live in an age where if an action is not explicitly called out as unacceptable, a significant number of people will perform said action, because if it's not explicitly unacceptable, it's obviously acceptable.

I don't think this is a good argument, because you might as well say

We live in an age where if an action is explicitly called out as unacceptable, a significant number of people will perform said action, to protest the very idea that it was made explicitly unacceptable.
Daniel Kahneman, "Thinking, fast and slow"
This is probably a parallel, but I still think Apple came up with the best, most self-disciplining code of conduct of all times:

> We will reject Apps for any content or behavior that we believe is over the line. What line, you ask? Well, as a Supreme Court Justice once said, "I'll know it when I see it". And we think that you will also know it when you cross it.

Yes, they do publish more direct rejection reasons too. But those reasons were enumerated by experience and were repeated over and over -- like religious hate. What I like is they did not start with a committee of people saying, "Let's brainstorm what could go wrong."

To be able to deal with a large fraternity of people, the better approach is to not imagine a nominal case. You have to start openly, then establish a nominal case with experience.

Mark Stehlik once said, "But, you don't make policies around edge cases; you make policies for the nominal case and deal with the edge cases as the exceptions they are." I like this because this enforces a clear intention of being able to deal with edge cases. This is just like Apple's review guidelines. Firstly, they call it guidelines and not code of conduct. That enforces that they are human and flexible.

The problem with having a code of conduct with a large fraternity of people is that you immediately give the community an intent of what you like and what you don't like. That discourages you to find things that you may have liked but now will never get to see. That also gives idiots in a community a chance to police potential talent based on now written code of conduct. That's a grammar-nazi behavior. You may get great English teachers in that community, but I doubt a Hemingway would want anything to do with you.

Also, it has to be unique to each project. Having a blanket open source code of conduct is bad. It follows what you know, and discourages what you don't. So it's essentially an inbreeding system. And if an open source project accepts and celebrates an inbreeding system, then it is just a proprietary company with no money and wget-able code, essentially failing on both ends.
Bottom line is: People will find ways to feel offended.
I deal with it with an old trick.

(1) Backing away. Pushing through stressed produces inferior results.

(2) Using a different constraint. That's the real trick.

Only I can't make myself pick the right constraint from the get go if I'm feeling stressed, so I stay stuck in a loop. I need to back away for the subconscious to reveal the right constraint.

It's as if I have to give up first. It seems it's only then I finally let myself attempt a solution I haven't tried before.

So ironically the way to deal with the stress of getting stuck and having deadlines is to manage to reach the point where, after trying everything, you sincerely no longer give a damn.
The Django ORM or sqlalchemy good starting points. Metaclasses are what make them tick.
Just to be clear, the simplest gloss on Eagleton's landmark essay (it's really too short to be a book) is that it's a takedown of belles lettres-style criticism.

Loosely speaking, Eagleton is best known for Marxist literary theory (dialectical materialism).

[Edit: removed html-style tags]
Four Italian restaurants. Did you completely miss the point? Of course you did.

Regional cuisine in Italy is obviously richer than the cuisine of the whole UK

I live in a town far smaller than Naples. I have, almost on my doorstep, Thai, Italian, French, Japanese, Chinese, Indian, Pakistani, on and on. Repeat around the country. Britain is far better for food than Italy. I can far more easily access a far greater range of food in Britain than Italy. I bet that violates some ingrained cultural belief, but facts have to be faced.

It's from Game of Thrones, not Downton Abbey.

Game of Thrones is a soap opera.

At some point you're going to need to learn how to cook. The sooner, the better.

That was an immature, juvenile response and you know it. Grow up.
https://www.ftc.gov/tips-advice/business-center/guidance/sta...

Read section 4 specifically.
I think many people who criticize the idea feel that it's been heavily pre-politicized to push for a particular version of "social justice" meme-complex. And if you discount that driving force and that motivation, it isn't clear that a CoC is either needed or useful.

If you try to think about it in a clean-slate way, sort of; forget "oppression", "microagressions against minorities" and all the other politicized jargon that the current version is peppered with, and ask yourself (answers are my opinions, obviously)...

Q. Is there a problem with some open source communities being too hostile, unwelcoming, potentially harassing to many people?
A. Yes. Some communities are clearly much more "nice" than others. Some are clearly much more welcoming of newbies, etc.

Q. How does this "bad behavior" manifest itself, in actual open source communities?
A. Mostly by how much rudeness and brusqueness some regulars of the community feel they can treat others with. If you hang around on forums, issues, IRC channels etc. enough you can get a clear feel of the "niceness meter". Sometimes there's also explicit misogyny, but that's relatively rare. Other explicit forms of hostility (e.g. racism, transmisogynism) are even rarer to nonexistent. It's simply that if the overall level of niceness is low, then people behave like assholes. Asshole-like behavior is easy to interpret as racism etc.

Q. Is this a huge problem? Should we invest effort in trying to make communities more nice?
A. I don't know, seems like a personal call. I personally like the nice and welcoming communities much more, and don't really see the point of being rude and hostile (I think it's counterproductive and not only wrong).

Q. Is a code of conduct a way to achieve that?
A. Doubt it. Seems like the norm set by the leaders of the community, together with a few clear examples of "we will not tolerate this kind of behavior", is how it's successfully done. Is there a project which went "not nice -> adopted CoC -> became clearly nicer"? I haven't seen any.
Their stores remind me of K-Mart stores.

(Dirty, poor displays, a lot of shelf space empty/out of stock, and always almost entirely empty.)
People who say that are usually people who define "racism" and "sexism" as "discrimination from a position of power" or "systemic/institutional discrimination". For them, just because men or whites are statistically more likely to be powerful, men and whites are powerful and "privileged" in general. Who cares about poor whites and homeless men!

I think that's pure bullshit, but a lot of people apparently feel the opposite.
The registry really does seem to be the most common use case:

http://ivansmirnov.io/python-metaclasses/#metaclass-as-a-reg...

This enables things like plugin systems, where you want the act of importing a plugin which defines some objects to load those objects into the available plugin list.
Is it just me, or does my reading this CoC say that not being nice is okay (and accepted and required) when dealing with people deemed not nice?

This is what troubles me - I was brought up to be nice and behave well to others. We are more alike than different. To say "we should behave different to others who are different" and "we can behave as bad to others because they are different" is wrong and only leads to conflict and harm.

Of course I could have read it wrong and am reading too much into it!

BE KIND
A related article with a bit more detail:

http://www.bbc.com/news/magazine-33166383
Show HN: Abache – HTTP server implemented in around 50 lines of bash
_The Power of Habit: Why We Do What We Do in Life and Business_ (2014) by Charles Duhigg
Still speculative, the original article mentions a lack of spotters and an io9 article mentions a depth of 30-40m.

For her this was child's play: freediving gets exponentially harder the deeper you go. She could've decided to go exploring a bit on the bottom - at that shallow depth she'd have 2+ minutes of bottom time.

With ~5 days of training, a person can get to 30-40m. Then it becomes harder (e.g. the air in your lungs gets squeezed to a smaller volume than a complete and total exhale)

http://io9.com/well-probably-never-know-what-happened-to-fre...
> Ruby is already not a super-popular language

is this opinion or fact?

> I also (personally) disagree with lots of the philosophy behind Rails.

You present this as reasoning but, doesn't make it wrong.
Can't wait to hear a legal professional's opinion vis-à-vis simulated back rubbing.

But seriously, I'm hearing about this for the first time. Can anybody explain to me why this particular CoC is more controversial than any other random CoC?
The Making of Atomic Bomb by Richard Rhodes, he stars with the science of the atom as it was figured out in the late 19th century and continues through the end of World War II
We'll never delete data, we will make the repositories private. You will have to move your public project elsewhere. For significant projects we're open to making it public when you've replaced the repo with one announcing the new location.
I'm curious if the author ever looked into HamWan. [1]
They provide non-commercial internet access for hobbyists who have their amateur radio licenses (very easy to get) and buy some basic equipment. They cover a number of places in the Puget Sound region. The author would have to build a tower to get above the trees but I can't imagine that this would run more than $4-5k (on the high end).

I am not actually a user of HamWAN--I'm down in Tacoma and my line-of-sight is impeded by terrain and building a tower in my dense urban neighborhood isn't an option. Also, I have biz-class Comcast.

[1] https://www.hamwan.org/t/Wiki+Home+Page
What Person A sees as a good sort of social justice may not like up with Person B's interpretation. It is possible for movements to sully the name of a stated positive goal.

Beware of reading books by their covers. That's the sort of thinking that got the US stuck with the Patriot Act or other sorts of legislation. Especially after a terrorist attack, people don't want to be opponents of "patriotism" (which gets defined by one side to mean a very specific thing).
Yes, it's called decision fatigue and it's a real thing. Don't make important decisions in your life at the end of a long day where you've already made many, many decisions.
The fastest way to encode these dense bitpackings is almost certainly with the Chinese remainder theorem.
Xlabs video compression
xilinx_guy - Really interested in your comment on that article about Xlabs. I'm a tech reporter and would love to get your feedback. You can find me @seancaptain
I'm just getting miserable by all the hypersensitive crybabies out there.

What about my feelings? No one's going to care because I'm white and conservative.
How does this compare with magit?

Also are there places where Preforce is still better than git/hg?
Except you can't bring your own non-verizon device, even if it is LTE, they won't allow it on their network.
"No one knows what happened to her. There were powerful currents in the deep water beneath her and she may have been somehow carried away. She may have lost consciousness."

I've been freediving for 20 years now and I've never heard of anyone (nor myself) having trouble reaching the surface because of currents. Strong currents affecting a freediver are lateral, not vertical.

Not trying to say currents are not dangerous for freedivers. I've friends who did end up lost for hours in the surface because of currents. Also, if you want to reach a certain spot in the sea floor and there is current you will consume more O2 and you increase your chances of blackout before reaching surface.

But dying because of being carried away? hmm no..

So, the only true thing is that she did black out and did not come to the surface. The current is the reason why they are not finding her. No one will ever know why she blacked out.

edit: typos
MeshLabJS
Sorry, I don't have detailed research or a percentage. All I can say from - somewhat anecdotal - experience is that it'll be at least a moderate PITA.

In general, i18n tools for Java are quite sophisticated so with Java it won't be that much of a problem. Other environments probably require some more manual work.

Some IDEs (Intellij IDEA and Eclipse for instance) allow you to extract strings from your source code and externalize those into a property file. However, those tools aren't perfect and will likely still miss some strings. So, at least some manual work will still be necessary.
Huh?

"Outrage" is practically uniformly worse than other, "non-outrageous" ways of solving problems.

Whenever the word "justice" is modified by another word, that's usually a very good sign that the expression doesn't mean justice.
> Bring back the mailing lists.

Huh? So you both support the CoC but also want to "bring back" a form of communication which is entirely unmoderated? That's super contradictory.
> If you die you die. What difference does it make
> if a second ago you enjoyed your life.

I don't know if you've watched anyone die but it isn't "fun" for most people (either the watching or the dying). Many people are there with their parents when they pass, or with grandparents or loved ones struck down by accident or disease. So in general I think everyone will likely watch as at least one other person they know and care about dies.

When that happens, you may find yourself sharing the dying person's pain, and that is a heavy burden. When I am listening to, or reading about, the death of someone. I wish for them an an easy passing, with as little pain and suffering as possible, for both them and their families and loved ones, because I know from my own experience how painful it is to watch someone die and be unable to help them. So for me, the living, it makes a huge difference if the person died doing something they loved (and thus were likely experiencing joy and satisfaction at the end) then knowing someone died slowly, painfully, and inevitably spending hours, perhaps days or weeks, moving toward their own demise.
I suspect Uber will eventually move into deliveries too. It's a natural extension.
Interesting. how does this work? based on statistics/reports I guess ?
Add to that: creating a mile long contract for what is and isn't proper conduct is guaranteed to create more problems and disagreement than it aims to resolve.
I wish I were that smart, but no - I have to spend extra time revisiting / researching concepts on my own time.
The phrases "political correctness" and "treating people with respect" describe entirely different things. They are not interchangeable without altering the meaning of the sentence, as they refer to two completely different concepts. Whether or not you agree with the intended meaning is irrelevant. The meaning is still there.

Just to be clear, I'm all for treating people with respect, as any decent human being should be. And political correctness is perfectly fine and necessary in most cases, but in most contexts it refers to conforming to certain narratives to avoid scrutiny and being ostracized, which typically only exists to serve some underlying agenda. It's been taken to the extremes lately and conflating "political correctness" with "treating people with respect" is a mistake, because more often than not, political correctness does more harm than good. Imagine there's a serious security flaw in some software but no one will speak up about it because it might result in ostracizing whoever does speak up about it because it offends people. The more freely people are allowed to express themselves, the better off we will all be, regardless of the message. But yes, when speaking freely, one should also be respectful. You can be politically incorrect and treat people with respect at the same time. That is why those phrases are not interchangeable.
I would focus his attention on the possibility that his card processor will cut him off for violations of their agreement. This would result in large-scale loss of business and it may not be easy to arrange for a new processor on short notice. Keep his eyes on the money.

I would not bother with a technical explanation of any of this stuff. He doesn't care, and bluntly it's not particularly easy to point to major compromises in which the lack of SSL played a key role. Most of the time, data is siphoned out of "PCI-compliant" shops that do use SSL, and they get it through database compromises and/or compromised POS terminals. MITM doesn't seem to be worth the effort, if only because the other stuff is so easy and yields so much data.

Nor would I bother talking about PCI. Most of their requirements are silly and do little or nothing to prevent exposure of PII or fraud. What matters to him is the agreement with his processor, not some 4000-page document that wants to tell you how to take a piss.

Eyes on the money. No processor, no business, no money. Keep it simple. If that doesn't do it, you've done your part and should walk away. It's not your problem.
The problem with blank statements such as this is that "the line" is a moving goalpost. I'd (reluctantly) support even completely arbitrary enforcement, as long as it's not retroactive. But if they first accept apps with Confederate flag, and then ban them later, that's IMO a very bad precedent.
The difference between setting some community norms and having a code of conduct seems to be writing it down. And, in writing things down, there's one reference for the rules/guidelines and everyone knows what they are. Is much prefer GitHub to set some rules rather than have year's worth of what would essentially become case law. Plus, community norms aren't exactly working either, so..

Overall, with a bit of editing (perhaps the code of conduct should be rewritten to avoid as many politicised words as possible), I'm not sure where the difference is between a well written code of conduct and a 'be nice' community norm.
https://github.com/cnr-isti-vclab/meshlabjs
> And what if I did? Learning to ignore things that could unreasonably sour your mood is a valuable skill in life anyway. Life itself doesn't really have a code like proposed.

De-escalated depending on the context of the situation.

Code of Conduct defines problems and could turn anything funny, innocent, etc. into an excuse to ruin someone's life.

9/10 times it's someone who doesn't program (an Adria Richards, Shanley Kane) who will be attacking someone who actually contributes.
Github really has jumped the shark.
"The management duty of most top-level domains (TLDs) belong to the Internet Corporation for Assigned Names and Numbers (ICANN)"

This is not a true statement. Each TLD is controlled by its respective registry, which is certainly not ICANN.
If a storefront on the web asked me for an SSN, HTTPS or HTTP, I'd probably file a police report for the attempted identity theft. There's literally no other plausible reason to collect that information, unless he/she is a registered financial institution extending credit to people.
"The Baby Harvest: How virtual babies become the future of terrorist financing and money laundering."

Terrorists are killing and selling our babies! Sounds like over-the-top far-right US political rhetoric.
Those are the motives of somebody who believes that no policing at all is better than half-ass policing.

We already have organizations that deal with illegal activities. We pay them for it and we give them a monopoly on violence, so why not use them instead of trying to replicate what they do, partially and poorly?
The first thing I'd think of with a site asking for SSN is an active intent to commit fraud: ID theft, or fraud. That's before SSL (which is obsolete anyway, only TLS should be considered now).

The second thing, the fact it's http and not https suggests he's collecting and storing this information, which is almost certainly a violation of his credit card agreement with his bank. Credit card information is not supposed to be stored, he passes that off through a secure connection with his processing service, who will only do that through a secure connection, and he gets a transaction ID and authorization and that's all he references from that point on.

So this is less about SSL/TLS as it is, he's doing it all wrong. And it's depressing that he's in business, only made possible by the ignorance of his customers who actually agree to give him all of this information, and on an insecure connection no less.
This is a very interesting dynamic because it is absolutely true that the phones are designed to last about 2 years. But the carriers also depend on this because in order for them to introduce new features and functions or to get new spectrum opened up for capacity, the count on the entire user base of phone essentially turning over every few years. If that pace slows down, it will be more difficult and take longer for them to turn up new spectrum.
There are many cases where this sort of thing would be useful, not just this edge case. For instance, automatically rewriting between a recursive function and a function with an explicit external stack. Or swapping between an eagerly evaluated function and a lazily evaluated one. Or swapping between different types of allocations (stack, heap, region + bump pointer, etc). Or swapping between different ways of parallelizing a function or loop. Or swapping between row or column based evaluation. Or specifying two equivalent functions and have the compiler check as much as possible that they are equivilant, calling both and asserting on debug builds and calling the faster one on release builds (or potentially even calling both in separate threads and waiting until either one returns). Etc.

All of these are things that you can do manually, and that you can leave to the compiler and hope that it'll pick the correct one, but currently good luck telling the compiler that no, you really actually want to do <x>. Or to try <x> and <y> and see which is better. And the amount of time required to do so manually adds up, even though they are all things that could be done by a compiler.

I personally wish that you could specify / annotate the range that you are actually intending to store in an integer (and have it optionally bound-checked) anyway, but that is another matter.

(Actually, I wish that you could specify types with an arbitrary (probably-pure) boolean function to indicate if something is or isn't a valid value in the type. But that is another matter indeed.)
From the chrome webstore page:

>Disclaimer 1: Plain Text Offenders Alert is not associated with plaintextoffenders.com, it uses their publicly available database.
Yes they will. If you have no written rules, when they get offended, you've got problems. If you have the written rules, when they get offended, you can kick someone out for either breaking the rules or complaining about something that isn't against the rules. So much easier.
Debug.Trace -> http://hackage.haskell.org/package/base-4.0.0.0/docs/Debug-T...

Whenever you want to see the value of x, replace it with traceShow x x
Your correct, it isn't funny, but when the Social Security administration decided my wife's uncle was already dead and he needed to pay back benefits they sent, she had them talk to him on the phone, where they tried to explain to them that because he was dead he needed to payback excess benefits.
Kind of. The Chinese Remainder Theorem tells that you that there exists a number that satisfies, and that the number is unique, but it doesn't tell you how to calculate it.

The standard way is to do it recursively - you can see my implementation here: https://github.com/hcarver/Netflix/blob/2136aa5d28a209f902d4...