skysight-inc/HackerNews huggingface dataset:
I still must emphasize that you picked the incorrect governance system to include in the conflict with the developers in the open source community. The governance choices of Apache OpenOffice were largely irrelevant. Sun owned StarOffice, and continued to pay developers to work on the codebase after releasing it as OpenOffice.org. This justified their strong control over the governance of OOo, despite the friction this caused for the community. Had the community forked, it would have been uncertain which codebase would have won (gotten the most development and usage). The governance system in this case was not that of a pure open source community, but rather heavily influenced by a single corporate entity.

When Oracle acquired Sun, they ceased to govern and pulled their developers off of the project. At that point it became impossible for the community to continue working within the existing project, so the remaining developers forked to create LibreOffice. It is not adequate to say that "governance choices" killed the project, Oracle killed it but held on to the trademark.

I can think of no reason why Oracle would decide to donate the OOo project to the Apache foundation other than to generate confusion in the marketplace and deflect criticism.

At this point, I don't think the AOO has done anything wrong governance-wise, but there's just very little reason for LO to work with them. AOO development is mostly stagnant, and going through another governance restructuring and licensing change probably doesn't seem appealing to LO. I doubt the Apache project will donate the trademark to LO because they probably don't want to give up on an Apache-licensed project.

I do completely agree that governance requires assent by the governed, and the project owning the OOo trademark does not have that, but your post mis-attributed the who and the how.
Well aware of the pitfalls; I've worked in neteng for most of my career. But your statement of '15 seconds to a couple of minutes' - there's the rub. Do that more than once and you've blown your SLA.

Don't misunderstand me, I'm not defending Peakweb, simply saying that running a five nines network is hard - it typically requires deep experience in diverse problem domains.
Confluence. Horrific editing experience but good enough for simple docs and understands Jira links.
I do not mean any offense. I really don't.

If you can think of a nice way to convey the same sentiment/message, but without the offence, I'm all ears and would happily edit the post.

Again, let me stress, I think there are arguments for long and short. I do not advocate for right and wrong, merely try to convey the reality I'm in, given that it's so different apparently from SF.

Realise also, in good faith, how offensive the "1 page resume" sounds to my ears. There is not any hyperbole present when I say I haven't ever seen one. Indeed, the only reason I believe it exists is because otherwise intelligent people I respect have told me it does, and now hacker news backs that up.

Really though, is it so hard to believe that people think that summarising yourself down to a page (as opposed to three or four...lol) is also an offensive idea?

Are we really so departed from one another that we believe that we can't just agree that the way our two respective cultures do things is offensive, especially given the fact that neither of them appear to have much success with outcomes regardless of which culture is in play?
Would you also encourage such a network be built with diversity of parts suppliers? I ask because it seems like you'd want to be able to also resist attackers exploiting a bug in a single vendor solution.
This is obviously much better than proprietary as people can potentially benefit in the future from your work and I thank you for being so kind as to share it and yet I would probably use something significantly crappier to have real open source and several other things seem problematic.

-- Others are unlikely to contribute to the proprietary fork.

-- What do you do about contributions to the gpl3 version they would be copyright their creators and couldn't be part of a closed source version even the authors without copyright assignment.

-- Do you backport fixes to the gpl version. It would be far simpler to say use the new version wherein issue foo is fixed. If you do its a lot more work if you don't the gpl version isn't just a older version its a known broken pos that will never be fixed.

-- What if people offer fixes to the gpl version will they be expected to assign copyright so you can use them in the proprietary version?

-- 3 years is an eternity. In 1 year someone could make their own version of whatever it is you are doing that is actually open source if it was really worth having it would also have none of the above complications.
"C++ did it right" seems a separate position from that put forward by the parent comment.

I definitely think there's benefit to being able to view interface as separate from implementation, although that might well be better supported by tooling (editor folding, documentation generation) than manual maintenance - which you seem to be doing well.

I don't know whether there is benefit to being able to edit interface separately from implementation. Probably not much of one, but I could certainly be convinced otherwise.
That's more likely to do with that foreigners will not know perfect Japanese so you'll reflect badly on the company. It's not racism lurking. Especially since the language has so many levels of politeness that means that even bending of the words are different depending on who you talk to. Business Japanese is very difficult even for Japanese. But it's always easier to hide behind anger. Just realize that many of the things that make Japan great has a drawback to them. But I prefer that countries are different so you can find a place that suits you.
Not if you are iPhone 7
What about asking no one? :) Some of us prefers to drink our coffee by ourselves.
> You really got caught up in your rant

You may not have defended it, but you also didn't criticize it. So I added that, like draping garlic about, to increase the safety of this space.

> The fact that two wrongs don't make a right is taken so, so far by some reactionary people, that they basically end up pretending that the first wrong is blown out of proportion or doesn't really exist.

I know that, and I resent that as well. But I see nothing in the comment you replied to to indicate that at all, they probably weren't thinking of ALL kinds of groups that exist, but merely advocacy ones etc. I don't know, but why presume either way on this little data? You basically said the poster implied "exactly" that they are reactionary and in denial. Maybe you two have history, but this is a really odd style of discussion to me.

> Which is exactly what that poster implicitly revealed by offering up that thought experiment. Imagine men saying to women "you are not welcome here". Yeah. Imagine.

Yeah, we don't have to imagine it, and "we" for any given "we" know how we react to it in what we consider polite company. Hence the same reaction to girls clubs, at least where it crosses the line from immediate safe space and support to political outlook and whatnot.

In that sense, there is kind of a double standard, there are plenty of people who find that benign or even cute when women do it, but would instantly recognize it for what it is in other contexts. Hence an allergic reaction to anything that might contain it and doesn't contain proof it doesn't. I guess your reply was kind of similar, assuming an reactionary outlook of a specific type based on very little.
It depends on the mode of failure, but these problems happen when a battery is stressed. Charging or discharging at a high rate especially with high temperatures and during/after physical stress can cause runaways.

Protection circuitry is supposed to prevent runaways, something is obviously failing. It could be an overheating component or faulty high voltage protection circuits or simply just bad thermal design.
Yeah I didn't think that there was a definitive answer in the article, kind of says that dropbox will just keep asking for it on boot. I was asking to see if anyone knew what APIs dropbox might be hooking into, but @szhu in a post above has kind of confirmed that nothing really happens. I took a look at this 2009 post. Interesting.

pretty disappointing really.
Bluetooth has been common if not standard, in even low-end models for the past 3-4 years.
Kredit Mobil Murah – Showroom Mobil Tikungan
This was probably at State Department. They have difficulty communicating security guidelines to staff and management.
You should be able to build a lot of redunandcy into your network on $4 million a month, but that would eat into margins, wouldn't it?
such a nice tumblr theme
I particularly miss paid holidays, paid vacation (or PTO), and paid sick days. I tell people that I only take off when the office is closed and they won't allow me to work, because if I don't work, I don't get paid.
a) Site is down, google cache is here http://webcache.googleusercontent.com/search?q=cache:NBcmXVo...

b) The license file on GitHub does not mention GPL, a time frame or something even remotely related to the post - looks like some sort of shareware license.

c) If it's a good product today, will it still be a good product in 3 years? In today's version? I doubt it.

Still better than just selling binaries, but not by much.
Interesting timing, I actually want to do this with my Pi (but wired). The only thing holding me back is the cost of the display - any suggestions for a cheaper non-touch display?
I've done freelancing for last 5 years. Don't under estimate time it take to run your freelancing business. e.g finding clients.
They make great gifts though, then the downsides are someone elses problem.
People rarely discriminate against young, upper class, white men, though.
It seems unwise to gate-check a bag with a laptop anyway, given the way the luggage handlers throw bags around. Gate-checking a roller board suitcase with clothing is one thing, but I wouldn't check anything fragile or particularly expensive.
Coupa S-1
1. Why would that be astonishing? The "+" in TLA+ is FOL + ZFC, the same foundation used for virtually all of math (except some branches of logic).

2. I am not a logician so I don't know of the formal particulars of measure theory, of any limitation ZFC has in formulating it, or of any TLA+ specific limitations in that regard. However, TLA+ is not a general proof assistant (it can certainly be used to prove general math theorems, it just wasn't designed for that task), but a language for specifying and reasoning about algorithms and large software systems. In that, it is as powerful as Coq.

3. There are completeness proofs for TLA, i.e., that anything that you can state about a computation, you can state in TLA, and anything you can prove about a computation you can prove in TLA. Now, this isn't quite accurate: TLA is a linear temporal logic, and there are some things that you can state and prove in a branching-time temporal logics that you can't in a linear logic, nevertheless, as Moshe Vardi says in Branching vs. Linear Time: Final Showdown[1], it makes more sense to prefer linear time logic because empirical evidence suggests that it's far more useful. There is one glaring downside: TLA is unable to reason about probabilistic algorithms[2]. However, it is possible to embed reasoning about computation in the + part of TLA (i.e. ZFC) and reason about probabilistic algorithms in that way, and I assume that this is how it would be done in Coq, too. So you could do everything in TLA+ without the TLA bit, but that would be inconvenient, as the natural representation of algorithms in TLA is especially convenient and the main justification for the approach. So I would be very interested in seeing an extension of TLA meant to deal with probabilistic algorithms.

4. In the end, what matters isn't theoretical strength (by which Coq and TLA+ are equivalent in anything that concerns algorithms), but convenience. I am sure that there are some problems that are easier to formulate and reason in Coq than in TLA+. But the fact that no one has ever used Coq for a large software system, and that the handful of use cases in industry were always done in cooperation with academic experts while TLA+ is used in very large projects by "plain" developers speaks volumes to the strength of the approach.

[1]: https://www.cs.rice.edu/~vardi/papers/etaps01-ver13.pdf

[2]: You can describe any probabilistic algorithm in TLA (i.e., state that an algorithm performs a certain step with a certain profitability). What you can't do is then state a probabilistic theorem about that algorithm, as "in 70% of the cases, the algorithm gives the right answer".
> But why do you get to question Facebook's idea of morality?

well, its literally a discussion on facebook's morality. Its a bit hard to talk about that without questioning it.

> To question someone's morality solely due to it being different than yours is, bluntly, a waste of time.

I'm not trying to change facebook here, I don't care /that/ much. I saw a discussion ("its facebook's morality") that I wanted to contribute to ("But its a weird sense of morality innit?"). Isn't that what discussions are for?
If you read most any SLA - pre announced maintenance with advance notification is categorized differently than unexpected events, for contractual purposes. JunOS and IOS upgrades need to happen, crossconnects need to get moved, agg switches get replaced, etc. Customers know this.

It definitely requires ccie level knowledge and at least 10-15 years experience, plus advanced Linux/BSD server admin skills to really do five nines right. It is indeed expensive and requires enthusiastic cooperation from non technical management responsible for budgets.

I worked my way up from a level 1 NOC type position, so I'd like to think that after 20 years I have a good understanding of all the possible OSI layer 1 failure modes (and things you can fuck up in configuration at layers 2 and 3), yet the things some other partner and competitor regional ISPs do continue to surprise me.
I certainly wouldn't recommend to use your primary domain name for sending out large e-mail blasts that might get marked as spam (whether they are "legit" or not).

An alternative might be to set up a subdomain (e.g. marketing.example.com) for those outgoing e-mails, create your SPF RR for it so that only MailChimp's sending IP addresses are permitted, and let your users use their preferred tool (Mailchimp).
I'm guessing your way is most applicable when working a relatively low number of hours, like 35-40 weekly. Once you start pushing into 80-100 hours at work each week, being friendly starts to make more sense, if only to avoid going crazy from isolation.
How about it with gif animation?
https://github.com/chidea/FBpyGIF
Here it is a very risky job in the world
Regardless, bitcoin had nothing to do with it. It's the fact that he sent the item before being payed that allowed him to be scammed. Method of payment was irrelevant. I have to agree with the parent that this seems like self promotion without bothering to more than skim the article.
There are a great many ISPs successfully using a mix of juniper, Cisco, arista and other stuff. You will find extreme and foundry 1000baseT switches all over the place still. I would never encourage a monoculture of one model nexus 3000 or anything similar to that.
They can, but they won't. How many Notes have been sold globally, a few million? The chances you're on a plane with someone with one in the U.S. or elsewhere is miniscule.
I really enjoyed going through the quickstart. It doubles as a really great teaching tool for people coming from front-end and design. It made a lot of data modeling concepts stick.

There are some bugs here and there, but keep up the good work!
I think I agree with that. By pre-industrial I meant that for many people where they lived and where they worked were geographically either identical or close enough (baker baked in their house, butcher slaughtered in the back yard, spinner spun in the house, serf worked at a nearby lord's land, etc.) I think there are some negative connotations simply because serious disease was untreatable and incomes were meager among other things (like power inequality and very low education).
Humans are divisive. We discriminate in all sorts of ways (positive and negative), and that discrimination becomes part of our culture. It's natural. If we don't talk about how our biases affect our interactions, the kinds of people who have historically gotten screwed by biases are going to keep getting screwed.
Agree Running Lean is the go-to book and of all the credits, the author forgot to mention this book and the author as well despite using The Lean Canvas as a base for the entire blog.
Yeah I agree... I like this idea in theory. But in practice I think you will end up with two major versions: "latest commercial version" and "latest GPL version".

And then people will want to patch the GPL version and not the latest. 3 years is a lot of delta... git is really good at applying patches, but I wouldn't want disincentivize massive refactorings.
I don't use Gmail at all and have only used PayPal perhaps twice in the last three years so I can't be certain but you're not referring to their visual indicators for encrypted e-mail [0], right? You're talking about something different?

[0]: https://gmail.googleblog.com/2016/02/making-email-safer-for-...
You are pretending to be civil, yet call people who use a one-page resume "an indian from mechanical Turk."

It's fine for there to be cultural differences. It's not okay to insult people just because their culture values short resumes.

I will be reporting your comment to the moderators. It's abusive and absurd.

> Realise also, in good faith, how offensive the "1 page resume" sounds to my ears.

How can a mere phrase be offensive to you? What offends you about the notion of people using succinct resumes? There are literally thousands of 1-page resumes you could see online, including mine (which I just linked to).

Everyone who uses a 4-page resume is a narcissistic asshole, especially you. Do you really not see how that is an offensive generalization?

Your original comment could have easily been reduced to "in Australia, we typically write longer resumes." There was absolutely no need to insert absurd character generalizations on the millions of people who use short resumes.
> Yes, this is indeed my implication. That he could not have possibly already talked to very many women.

Wait, me? Heh. That proves, as a matter of fact, that you don't know shit about me.

> I would say the same thing if someone were to claim "Racism in America is over!"

Except I didn't make any such declaration, I said what I actually said, and you deflected from those actual words by fantasizing about me based on a straw man. I didn't say everything is fair for women, I say there is way bigger unfairness on other levels, up to murder and carpet bombing, and I know plenty of intelligent strong women who exactly zero problems not only realizing that, they'd feel insulted if I didn't assume they know that. I mean, geez.
Well I do appreciate you trying, but I disagree with you that it is pedantry that doesn't matter. This conversation is the best possible example of why we can't allow the corruption of previously well defined words - it causes confusion for no good reason.

A backdoor doesn't need to be remote and the user isn't necessarily an attacker. It is simply a secret method of access that the designer put in place, it isn't designed for end-user use. It is almost always security through obscurity, and it is always a bad idea. It can be activated in a variety of ways: port knocking, hardcoded passwords, preinstalled remote software, shorting ground to some magic pin, an undocumented serial terminal, etc.

A rootkit doesn't need to be remote and the user isn't necessarily an attacker. It doesn't need to have any functionality for user interaction - which means no "escalation" occurs (It could simply scan memory for passwords and log them to a file). It runs above user space, and can therefor be completely hidden (but it isn't always, see DTrace). It runs with the same privileges as the OS that it is part of. That is important to keep in mind, the rootkit becomes part of the running OS - that could mean any of the OSes running in your tower (CPU, HD firmware, BIOS, etc).

Your definitions work fine in a vacuum, but they quickly fall apart in real world usage. For example, by your definition: a remotely accessible privileged service is a rootkit, because an unprivileged internet user can interact with it - accessing data and executing code in the service's privileged context. 'sudo nginx' is not a rootkit.
Unfortunately, this doesn't support regular expressions, which is a very useful feature for a code search engine. See https://github.com/google/codesearch for one implementation of this.
Nice write-up...gave me some ideas, although I am still new to my raspberry pie.
Now e-coli is raining from the sky! :D Seriously though, I really hope drone delivery takes off. If I could get random things that I need delivered to my house in under 30 minutes by a little flying robot, that would just be so neat and convenient. At least, until it gets stuck in the neighbor's tree on the way to my house.
I remember Stallman once advocated a license similar to this (for things like games, so people can make money on them, then release shortly after. His timeframe was more like months though iirc).
The real, non-political competitor to the OpenOffice lineage has always been Calligra[1]. It sees dramatically less development, but it is also one of the KDE related projects that has a knack for using its toolkit to dramatically reduce its own code bloat - what takes hundreds of thousands of lines of reinventing the wheel in OO/LO is several hundred lines of extremely well maintained Qt data structures.

Even when the zombie AOO dies it does not mean the end to competition in the free office suite space. Even beyond Calligra there are some Gnome based efforts and third party projects (including web based ones) that provide similar tools. There is no shortage of competition, and if there were ever a slowdown in LO we would just see another fork akin to the Oracle escape.

https://www.calligra.org
Very cool! a couple of friends and I put this together for our living room: http://blog.shriphani.com/2016/08/03/a-frame-that-listens/

It is a pi + a condenser mic which generates visualizations in response to sound.
Why is it only acceptable in those cases? Why not treat 'right to live free of racial discrimination' as a human right?
Where can I contact you? I run a website in the vacation space that ranks well on Google for over 100 keywords. I was planning to expand my website and build a drag n drop feature like the one you did. Let me know if I can reach out to you via email, or you can send me one at thepredestrian@gmail.com
Stock dropped 3% on the announcement.
"I'd stay away from these issues on HN unless we really have something valuable and new to add."

Enough with this rubbish - your comment is that of the totalitarian.

Homes are not businesses, and people have a right to decide who they let it - and not.

It's not a simplistic decision, and there are probably many factors. Personally - if someone looked like a scruffy bum, I don't think I'd want them renting my AirBnB if I had a place. Frankly, I don't care if it's 'discriminatory'.

More importantly - shutting down the discussion with political y loaded ideology is just wrong. These are nuanced issues, you don't get to win by saying the word 'racist'.