skysight-inc/HackerNews huggingface dataset:
I can not imagine developing this and thinking that it is Good. This type of product and platform completely ignores the reality of how it will be used and how police behave in American society.

In the demo video, their example has someone sharing a photo of "suspicious people" walking around outside their house, and has neighbors commenting "oh no!" on it. Now the police are alerted to this "crime" which may not even be a crime. Anyone who has an account on NextDoor knows the hysteria around a minor event like a car that someone doesn't recognize being in the neighborhood.

The next step is police or homeowner arresting or shooting someone captured on video and posted to this social feed as having committed a crime.

The developers, marketers, SV investors, etc who promote this type of surveillance as a good idea need a course in ethics and reality.
Assuming no pain is felt, what's the cruel part?
For anyone interested in this issue I would suggest taking a look a Neil Fraser's Differential Synchronization.[0] It took me 2 weeks as a solo developer to add real time collaborative editing to our product using that method.

[0]: https://neil.fraser.name/writing/sync/
Microsoft is gigantic, they loose absolutely nothing by competing against themselves.

People get caught up in the on-size-fits-all mentality. If you are a 20 man start-up it’s stupid to make 3 separate solutions that all compete. When you employ north of a hundred thousand people, it’s less of an issue.
This is not at all what the title makes it sound like - this is merely a portal for law enforcement in to what is in essence a social network feed. There’s nothing to be seen here that isn’t already publicly shared by Ring camera owners - heck, it’s not even stuff that people are sharing privately. People share this stuff on Ring because they want someone to get recognized or caught for committing a crime (or a perceived one).
Not even reasonable to say we're even discussing the same people given the descendants of the people who lived under Roman rule are more indirectly attested to by way of the Welsh, which was the last bastion of Celtic autonomy south of Hadrian's Wall. The modern Englishman is not really related to those Celtic people but is a descendant of the Anglo-Saxon invaders mentioned in the article.
> Sounds like a good thing for consumers and Android device makers, who will no longer be coerced by Google to install its apps "for free". It's a pretty bad thing for Google in the long term, whose apps will inevitably lose market share.

Google apps don't come standard on PCs, yet Chrome and Gmail have majority market share and Google Drive/Docs is widely used (in university everyone used it to collaborate, even profs). And that's on MS' own platform...

I really doubt Microsoft or Amazon apps are going to supplant Google apps on Android anytime soon, nor do I think Firefox/Opera/other browsers have a chance against Chrome on Android.
> "MongoDB may not meet the OSI definition of Open Source"

That's just euphemism for "MongoDB is not (certified) Open source". It either is, or isn't; and presently it isn't, for reasons that were entirely under MongoDB's control.
Huh, I’ve used this development pattern before, but never re-used the same branch after merging code into master. I’d keep the new feature behind a configurable flag so it could be enabled in local or dev environments. Multiple branches might get created and merged to master over time. The feature would be tested in the dev environment (and maybe on a subset of users in prod), before the flag is flipped to enable the feature in prod.
A solar-powered home inspired by a sunflower
That's the thing, it is not like all bugs disappear in equal proportions, more like some (agricultural related) go, some other -- come. And those are not necessarily nice ones.
I don't think they have to do anything here, GitHub is a different entity and afaik they want to keep it separated.
Do you mean you aren't sure of GPL2 (the plus just means they reserve the right to change any contributed code to GPL3 or above with out getting a new license agreement from the contributer) or that you aren't sure how that interacts with a web app?

In this case, essentially all your front end code would need to be GPL2+ as well (GNU considers dynamic linking to count for GPL purposes I have a hard time imagining you could sufficiently separate the CKE code from the rest of your code/site to satisfy them). If CKE requires any server side code your back end code technically would need to be GPLed as well but you'd never have to share it (back end code is generally considered to not be distributed hence the AGPL) so it would have no real effect and no one would know if you didn't.
Any plans on the European Datacenter?
Yeah I was talking about the harmonic table. Good tips, I'll give the wicki-hayden layout a try!
At first I thought it was just another CI tool exclusive to github.com, but the fact that you can hook up more than just the commit push events makes it interesting for orchestrating a bunch of workflows around issues and pull requests.

Also great to see that it supports both UI and code definition.

The only big missing feature in my opinion is a shared library support, because it will soon be tedious to copy/paste the same generic docker build commands across repositories.
> It’s basically a manifestation of programmer arrogance that they’re just too damn smart to encounter a software learning curve again.

It's fun to be cynical, but surely this is just yet another example of how hard it is to "just change" something for all sorts of reasons.

It's funny that you bring up hubris when the pinnacle of developer hubris is "surely it can't be too hard to {build it, change it, replace it} -- I could do it!"
IMO, by blindly follow these kind of cheatsheet, you will hard to get better with Git.

I used to remember command in certain situation and have a hard time understanding stuff like stash, rebase, cherry-pick, detach head etc...So whenever come up I have to sit google the heck out of it.

Then one day I decide to sit down and just read Git properly. They are on: https://git-scm.com/

Eventually I understand it better and now I know what I need to do in certain situation.
Remembering Paul Allen
No points were missed - the paper just showed why the points are wrong. I'd be happy to discuss them if you care to read it: there are three concrete correctness problems with CRDT (Logoot) in sections 4.2.4 - 4.2.6.

Re: the articles you cited: Molli et al.'s http://hal.inria.fr/inria-00071213/ (A) and their earlier paper: https://www.lri.fr/~mbl/ENS/CSCW/2013/papers/Imine-ECSCW03.p... (B), are unfortunately wrong about OT correctness, demonstrably so.

The formalism can obscure the underlying argument, but both A and B uses the same reasoning, which goes something like this:

1. Assumption: An OT system's transformation functions must always satisfy TP1 and TP2, independent of the OT algorithm or protocol, otherwise they are incorrect.

2. Proof: take any existing OT system, disregard the OT algorithm or protocol, just look at the OT transformation functions in isolation, and show that the functions do not satisfy TP1 and TP2.

3. Conclusion: All known OT systems are incorrect

The starting assumption of the proof is a false premise: OT's transformation functions do not always require TP2. The proof itself, of evaluating correctness on a subset of OT in isolation, then broadly generalize to OT as a whole, is a sleight of hand (and sloppy theory work). Hence, the conclusion is plainly wrong.

TP2 is only required under a very specific pre-condition, and meaning that avoiding this pre-condition means removing the need to preserve TP2 at the level of transformation functions. TP2/CP2-avoidance strategy is commonly used in many OT algorithms and protocols: GOT, JUPITER, G-WAVE/DOCS, COT, TIBOT etc., which are provably correct (see https://www.computer.org/csdl/trans/td/2016/03/07060680-abs..... Transformation functions capable of preserving TP2/CP2 for string-wise text editing (with verified correctness and without tombstones or other meta-data)are also available (see https://dl.acm.org/citation.cfm?doid=2998181.2998252)

What I also find really dubious is the verification method used in A and B: paper B starts with using a theorem prover to definitively prove that all previously known OT systems are wrong. Then the paper proposed new transformation functions that the same theorem prover showed to be definitively correct. Paper A, which came after paper B by the same authors, used another theorem prover to show again that all previously known OT functions to be wrong, definitively, including the ones that they proposed to be "definitely correct" from B. So A basically contradicts the results in B, and both were definitively "proven correct".
New in Chrome 70
This Texas Finance Professor Sifts Data for Signs of Rigged Markets
Russian Rocket Fails, and 2 Astronauts Make Safe Emergency Return
Mike Ash's article goes into more depth into how something like this is implemented in Objective-C: https://www.mikeash.com/pyblog/friday-qa-2010-07-16-zeroing-.... To put it short, references are kept in a big dictionary and zeroed out on deallocation.
Gorillas.bas

BZFlag on networked SGIs.
Throwaway on this one for obvious reasons.

Everyone makes mistakes and it is clearly a mistake to take money from repressive regimes. The #metoo movement should take a look at some of these companies.

https://en.wikipedia.org/wiki/LGBT_rights_in_Saudi_Arabia
> In a situation where there is a lot at stake, socially savvy people generally want to know the answer will be "yes" before the question is asked.

There's a gap between an overture which gets a “yes” and one which is unwelcome, within which an overture is acceptable and will not adversely impact a relationship even though it is declined; how wide this gap is varies by individual and context (it tends to be particularly narrow, and sometimes of negative width such that there are unwelcome advances that will be met with grudging acquiescence, where the recipient is on the downward side of a power imbalance) and, I suspect, is on average in our present society much narrower for women than men (becaus of, at least, general social power dynamics rather than necessarily any inherent gender feature.)

While obviously one will prefer that the answer be yes to any overture (even an implicit one), I think that—particularly with the kind of subtle, implicit, preliminary overtures that are used to gauge interest before an explicit overture is made—the thing a savvy individual will want to be certain of is that the overture will be within the permissible range irrespective of whether it will elicit a positive response.

I think a lot of the problem (other than active malice) comes from people not recognizing the effects of context and lacking empathy and thus projecting their own broader range or permissible-even-if-not-interested onto the recipient of their advances.
I drove across South Dakota and Wyoming in June. Unreal amount of bugs on the car.
It's not even a real tenet in the US. Politics and national/state/local policies here have extremely heavy religious overtones. There is absolutely no way that a publicly non-religious person would be elected to any meaningful public office.
My first iPod Nano with a scroll wheel. I could adjust the volume and scrub back/forward through a podcast without looking at the device. All it did was play music and podcasts, and it did it very well.

Now I have an iPod Touch. It's heavier than I want in my pocket for running. It has a bunch of apps besides music which I don't need, and which necessitate it having a lock screen. And ironically, because it has a "touch screen", you can't use it solely by touch.
As you may have guessed there is already an issue for that:

https://gitlab.com/gitlab-org/gitlab-ce/issues/21485
Before anyone asks, this is still a beta release that's not covered by App Engine SLA.
Battling the Scourge of ‘Embalmed Milk’ in 1880s Indiana
Two Commits That Wrecked the User Experience of Git (2017)
How would you like useful, open source tools that can be deployed once and only once (for everyone), and used freely (minus processing fees) forever without having to worry about (a) deploying an instance of it on your own environment or (b) the service going down because the owner lost interest?

Because smart contracts can do that. Pretty neat, huh?
It is the routine norm with social issues to look to pin the blame on one party. That seems to be the default mental model for any social problem.

It is usually not the best explanation and it actively causes all kinds of problems. I like to give push back against this common assumption wherever possible.
That’s a bit like saying you shouldn’t ask for a pay rise because there are starving kids in Africa.

Commercial unixes are basically dead, and for very good reasons. Good riddance.
Disclaimer: I work at Backblaze.

> Do BB publish pricing of what they paid for drives? ... a TB/$/Failure rate

Thank you, that is EXACTLY the correct way to look at the failure statistics! So many people seem to sort the list by failure rate and think no matter what the cost, the lowest failure rate wins. For Backblaze, we just feed it back into the cost calculation. For example:

If a drive fails 1% more often but is 2% cheaper in total cost of ownership, we buy that drive. Now, total cost of ownership includes the physical space rental so more dense drives can be more expensive per TByte in raw drive cost because we can make some of that back up in physical space rental. Also, most drives seem to take about the same amount of electricity unrelated to how many TBytes are contained inside, so double the drive density is like saying it takes half as much electricity over its 4 - 5 year lifespan. Electricity is one of our largest datacenter costs, so we keep an eye on that also.

But to answer your very first question, unfortunately we cannot release the price we paid for the drives due to the vendors requesting we don't disclose prices. But don't think we have some magically huge discount or anything. Most of the time we are literally paying about retail, maybe a 3% - 5% discount for buying in bulk orders of over 10,000 drives. But for reasons nobody at Backblaze can figure out, sometimes a bunch of new drives appears randomly at a really good discount price, then returns to the original price the next month. It might be some attempt along the supply chain to boost monthly or quarterly top line at the expense of profits, I don't know.
If you're just using a formula your heart rate zones could be quite far out.

For example, 220-age suggests my maximum HR is 178 and my threshold HR (85% of this) is 151, but in fact my max HR (determined empirically) is 188 and my threshold HR (based on an actual threshold test) is 162.
At some point people draw their line in the sand and would rather go without then do business with an entity that goes against ones own beliefs and morals. Unfortunate for the startups but in my opinion that is a risk you take when entering a foreign market.
I doubt this will be a popular opinion on HN, but...this is what comes of libertarianism.

What is a government other than a group of people who agree to work together toward certain goals and hold each other accountable to certain moral and ethical standards? Yet somehow, "government" has become the enemy, a thing to be done away with or reduced in scope.

When you do that, and replace government with "voted for with your dollars" corporations, suddenly corporations become the standard bearers of morals and ethics. Now, if I want to stand by my own moral code, I have to research every corporation I interact with. Can't buy those shoes, they employ slave labor. Can't hail this ride sharing service, they endorse autocratic regimes. Can't rent an office over there, they eat meat...or whatever. It's exhausting!

I'd much rather go to the polls, cast a vote for someone who represents my values, and have the government DO ITS JOB!

...but alas, that seems like the least likely thing that will happen in this situation.
Looks like they've read the old "useit" blog, which NN/g sadly "fixed".
MongDB submitted their license for approval, so obviously it matters to them. Whether you think it matters or not is irrelevant, you're just some random HN user with no bearing on what society decides open source is or isn't.
I'm not affiliated with this site, but this person sells DIY plans for similar mechanized wooden machines, mostly of clocks: http://www.lisaboyer.com/Claytonsite/Claytonsite1.htm

The celestial clock is on my bucket list to make if I ever get access to a laser cutter or CNC routing machine.
Yeah, the "based on age" makes it tough. I would love for there to be something more prescriptive. That said, I suspect just trying already puts me in a decent position.
How easy or even feasible is it to track where the money is coming from? Let's say you're a startup and a VC wants to invest in you. Can you ask for that information?
"The article is correct, you're mistaken."

No, I'm not.

"in order to bundle the Play Store and associated Google services you have to agree to MADA"

But "the Play Store and associated Google services" aren't part of Android. So you can ship Android devices without them.

"No major manufacturer, except Amazon, ships an AOSP variant without Google's Services."

Yup. Amazon shows that you can ship Android devices without the Play Store and Google services.
The nice thing about wikis is that they're editable :) thanks for pointing out that page though, I've updated it a tiny bit (and will do more if I can figure out media wiki's table syntax).

That is, assuming you meant: https://wiki.xmpp.org/web/XMPP_E2E_Security
Is this made to replace things like Travis and Jenkins? (I have very little experience with them.) The GUI looks very sleek, I'll definitely be checking this out to see how to integrate it into my SE course.
Both google.golang.org/appengine/datastore and cloud.google.com/go/datastore connect to the same data? Is there a list of incompatibilities somewhere? I remember seing some serialization differences between these two datastore libraries.
> I'm not sure what planet you live on, but the GPL and other various copy-left licenses have been on the slow decline for years

The planet that recognizes that proclaimed righteousness (what I wrote about) has nothing to do with adoption (what you wrote about). If anything it makes the righteousness stick out because it goes against what people are choosing. I rarely see GPL devs demonized for how they choose to give their code away, or blog posts and evangelists espousing anti-GPL, or the straggling person "eventually coming out and calling it poisonous", or justifications on non-GPL changes as claiming corporate harm.

I have no statement on license prevalence and it is unrelated to my comment. My statement is about justification used and being overly prideful of their work. Change and be done. One way is not necessarily better than another, and companies are not all bad, and that's not only who you are hurting with these changes, etc. But when I hear complaints about the company using up all their hard work like it's some zero-sum coffer being depleted, I don't pity them. I know the intent is guilt and I don't think it's a good look.
Uber and Lyft IPOs [120B and 15B respectively]
https://www.wsj.com/articles/uber-proposals-value-company-at-120-billion-in-a-possible-ipo-1539690343?mod=e2tw

https://www.cnbc.com/2018/10/16/lyft-hires-jp-morgan-to-lead-ipo-at-15-billion-valuation.html
BuildZoom (YC 13) is hiring for sales/ops talent
Definitely Salvatore Sanfilippo's (creator of Redis) blog: http://antirez.com
You might want to read a bit through this 4 year old thread about Tribler: https://news.ycombinator.com/item?id=8780313. Apart from the mountains of grant money and severly broken crypto ("set aside 'RSA without blinding'; this is RSA without padding.") which might or might not be fixed by now, I think the main point is that: "Tribler has a very long history of making high profile claims and never being able to follow through with actually usable software".

And it seems they're doing it again, now even making clearly false claims. See this paper, published this summer: https://arxiv.org/abs/1806.01926

They claim that this is about the "deployment" of an identity platform, but they only talk about several student projects during a blockchain course given by Pouwelse. The conclusion paragraph is really bordering on academic misconduct. They claim: "Thusly, we have created the
new Dutch digital passport solution ready for global adoption", but there isn't a shred of evidence to back this up. There is no production ready system. There is some work being done by course students here (https://github.com/Tribler/trustchain-android), but this is very far from "ready for global adoption". The documentation about ZKPs for example states "it was decided to leave zero knowledge proofs out of the application for now, until a better library comes around", while the paper claims that this is core part of the solution.

They also say that they have "presented the ground work for a Self-Sovereign Identity solution which is in production in the Netherlands for use by citizens in the latter half of 2018". They are here framing two small pilots in two Dutch municipalities to be a production ready system. Those two pilots, by the way, have yet to materialize.

(throwaway because I don't want to be ambushed about this later)
Who needs app stores anyway? Let's build progressive web apps and target all platforms.
> Unless you have a bug to report about undefined or non-deterministic behavior, then it must be something you're doing. Random functionality is not intended behavior.

You wouldn't be saying that if you ran into the behavior we have. Eventually I'll do more digging to find out root cause. But there's no way it was us.

> I seriously doubt we'll see a resurgence of anything like GWT again.

I'm thinking more along the lines of CoffeeScript. It bifurcates the landscape even further, but honestly I don't think it can really get any worse than it is now. But at least it will be building on top of sanity and not the lava layer.
From what was shown, it could definitely replace some of those use-cases.
Side note: the sans-serif font used on that landing page is Inter UI[1], an open source font that kind of looks like Apple's San Francisco font.

[1]: https://rsms.me/inter/
Git has a fair share of problems, but this command is not one of them.

`git push -u origin <branch>` requires you to to understand tree things: push, remotes, and branches. Once you know what those are the command is straightforward. Those concepts are very fundamental to any DCVS. Maybe you can do the first steps in other DCVS's without this knowledge * , but doing everything but the trivial things will require you to understand these concepts.

It's not strange that a tool solving a complicated problem for professional developers requires a bit of investment.

* But so you can in git, learning this command by rote is a valid strategy for a new git user.
I miss Umano. It was an app that collated a feed of human-read articles. It’s one of the few iPhone apps that I was willing to pay for a yearly subscription in order to unlock some premium features like offline listening.

Great UI and all of the readers were top-notch with new content every day. Haven’t found a replacement that works as well or where the voices used are as good. Sadly, Dropbox acquired them and then shut them down - really wish I knew why they wanted them in the first place. Just hope the founders got some decent $$$ from the deal for their excellent product.
Indeed. Tariff is a dirty word in American English.
Didn't know you could use ReasonML w/ GatsyJS. The app is really cute kudos!
I'm a semi frequent user here. I registered a new account for this comment thread because my username is easily tied to my identity and I mentioned in my comment there's someone we're afraid of who has threatened to harass us in the past. That person has used my web presence for harassment before and I don't want to give them more ammo.