skysight-inc/HackerNews huggingface dataset:
I am really not up on copyright law, but I see this as analogous to someone writing a book. Say I wrote a book and titled all of my chapters the same as another book, the book was given a different title and the chapters themselves where very different on the inside but naturally my table of contents looks exactly the same, would this be considered infringe in the publishing world (I don't know)?

Also based on that:

If it would why would API's be different?

If not how was it applied differently here?

What if in the above scenario, I added some extra chapters so the TOC has all the chapters the other book had, but the TOC is not a 1 for 1?

If my analogy is wrong, what am I not seeing?

I know as someone who writes software, API's not being copyrightable is preferable, but I would like to understand how the law sees it when dealing with real physicals works and understand if the law is applied the same when it moves to less concrete works.
You are correct that it's not on the axis, but West Virginia is very much tied to DC.

A number of federal agencies have offices there, including the FBI. I believe it's the central fingerprint data facility.

There are tens of thousands of people who work in DC, but live in West Virginia because it has fewer taxes than Maryland or Virginia.
well, there was a time here in Brazil when MSN was very popular (@hotmail.com), all my friends used it as the default messenger.

Later came Facebook and people created their account using the @hotmail.com and starting to left MSN, since facebook had a messenger. One day I received an email from Microsoft saying that they were disabling MSN (I'm telling this from memory, forgive me if I'm saying anything super wrong).

Fast forward to me being in college and studying a little bit of pentest. As I recall I was trying to see how much information a could gather from a person by their facebook page (as a non friend). If you try to login using their ID (or username) you could find pieces of cellphone number and emails. So I tried this with a profile from some girl I had a crush back in the day and discovered that shed used MSN as email.

Eventually I tried to log in her email on MSN and found out it has been disabled for a while. So I tried to recreate the email account with me as the owner and for my surprise it worked. I then went back to facebook and recover "my" password. With the email and password, facebook didn't let me login because of my location. But I knew where this girl lives, so I found a proxy server [1] and bam, I was in.

Not going to lie, I did look at some of her messages and pictures, but felt very bad after and decided to tell facebook and microsoft about it. This was facebook's response [2]. After a day or two of getting no answers from both companies (before I got the answer from facebook), I told the story to about 2 or 3 tech reporters. They told me they wrote to microsoft asking for a comment, but never got any answer. A week later I tried to recreate another "dead" account on hotmail and I couldn't. Don't remember exactly what they did, but I just couldn't create the email, so I figure they has fixed it.

1 - http://free-proxy.cz/en/proxylist/country/BR/all/ping/all
2 - https://imgur.com/a/kFMlO6d
You're right. It's hard to publish data with semantic markup and understand the schemas (or even the benefit of using them). Nobody is writing FOAF or any other RDF/OWL by hand.

In order to bootstrap the process, authorship tools need to produce semantic markup automatically on the behalf of users. Unfortunately the content silos do not want to do that. They're happy to keep the data to themselves and run Snowflake / big data queries on them all day long. They just don't want you doing the same. It's no benefit to them if your friend or interest graph escapes their hold.

This is a difficult chicken and egg problem.

A good angle of attack might be for the distributed web folks to take an interest. ActivityPub, Mastodon, and Matrix/Riot/(whatever they rebranded to) would be beneficiaries of schema ingestion. The more they can mark up the data they produce, the more useful it becomes. A tooling ecosystem can grow around semantic data.

Technically open standard APIs in a distributed web are already semantic, it may just be that their schemas don't map well to queryable triple stores. But that's just a transformation away. RDF is just a format for expressing your ontology in an open and compatible way others can reference and build upon.
Yea, easy to sharpen steels are like AUS-8 and 8CR and other cheap Chinese steels.

Kershaw's lower end line are often full of really cheap Chinese steels. Same with CRKT.

I've taken a "buy good knives" stance. My favorite is definitely not cheap, but it gets a ton of carry time. I'd also hate myself if I lost it lol

But if you're the type to carry a knife, a good knife goes a long way and getting a knife steel on it that can last is also a good way to go. Modern super steels are insane.
This article really overstates the case by focusing on copyrightability while leaving fair use for a tag at the end.

Winning on fair use is not a disaster for Google. Google winning on fair use on procedural grounds, if the Court uses that as an excuse not to even answer the copyrightability question (the narrowest possible grounds for a Google victory), does not, contrary to the article's claim that "a Google win on a narrow procedural question would create a lot of legal uncertainty in the software industry", create any new legal uncertainty for the industry.
A rich internet application (RIA) framework--any of Adobe AIR, Silverlight, JavaFX. But they competed and none gained enough traction to become dominant. This happens over and over with universal toolkits. The current one is html+js web app/electron. Not my fave in terms of developer ergonomics or resource efficiency.
If the FBI thinks someone is making a nuclear bomb, they should have much better evidence than Google searches. Nuclear weapons are fascinating, and I'm sure that there are plenty of people all over the country (myself included) who have dug into how they work even though they aren't going to build one.
The sort of garbage we ended up doing prior to SPAs justify SPAs.

Writing a server to dynamically create a HTML page that also includes first pass content as well as potentially dynamic javascript to make the page interactive in "later passes" is just an ugly mix of client side execution and server side execution in one spot.

The application just feels a lot more consistent when the client is just pulling data instead of being thrown away and recreated in the middle of a request made by a browser for a particular URL that is just one of a very long series of requests.
Read the article.

The case was bad for Google because their lawyer was bad.

The case would be bad for software everywhere, because API copyright. (in future)

You're mixing both and asking why it would be bad for Google
Staying in this analogy, aren't APIs more like pictures or verbal descriptions of the facade of the building?

An API spec will not (necessarily) provide you with any internal implementation detail. Architectural diagrams/design specifications very likely will do.
Because no demographic has been demonstrated to have a 99.99% survival rate?
It would have been more effective if you left it at that. I'm trying very hard to bow out of HN discussions on COVID, you were making a good point in a bad way and it would be a waste to see it lost. Thank you for the correction.
Yes, space debris is a problem and we are likely not doing enough to keep up with the growth of the space industry. But I dislike the rhetoric of "People are not really worrying about this..."

This was really true in the early arenas of space and we can still see the effects of that today. But every person that launches a satellite now in order to get a communications license for their satellite from the FCC or the ITU has to prove that their satellite will de-orbit within 25 years. With the start of the mega-constellations there have been discussions about tightening this rule [0]. Chief among the people who want to tighten the rule is the US DoD. When you invest a whole lot of money in putting something up in to space you want to make sure it is going to survive. So there are significant number of people working on tighter restrictions for future satellites launched in to space.

From the side of removing debris from space, there are multiple people working on technologies to remove debris from space [1]. Part of the problem here is the economics of it do not currently add up. However, considering the investment in the prevention of creating more debris the economics of this might come around soon. The other problem is the actual technology of removing debris without creating more debris. To catch a piece of debris you essentially have to maneuver a satellite "rendezvous" with the debris. Otherwise the relative velocities might turn an instance of "catching debris" in to "debris collision". Maneuvering between objects takes fuel which means more mass launched and more money to remove something smaller.

[0] https://breakingdefense.com/2020/04/fcc-reconsiders-tighteni...

[1] https://www.nanalyze.com/2019/06/space-debris-removal/
Are these the beginning signs of an addiction to fake internet points?

Probably.

I wonder if karma was hidden from us if it would do something to curb this compulsiveness. Seeing instant feedback, a number going up or down is very stimulating compared to nothing, or even a very broad "over 0/under 0" status as a middle ground.
Show HN: KN95 Mask Price Dataset
I thought that until I got to Google's closing remarks. They said that 1) the Federal Circuit didn't really do a de novo review like they said they did, and therefore that their overturning the jury didn't have the excuse that Oracle said it did, and 2) that Oracle was factually incorrect in several statements it made in the hearing. If those claims are accurate, Google is likely to at least win on fair use.
The Republican government is only a recent phenomenon. This is the state that had a Rockefeller for governor in the 90's.
Rust doesn't prevent memory leaks.

However, it may help in this specific case.

In your example you are iterating over `m_requests_to_process`. As you are using `auto` instead of `auto &` it automatically clones the elements of a vector. In Rust, it's not possible to clone an element by accident. Objects are moved by default (think `std::move`) and if you want to clone instead you need explicitly use `.clone()`.

If `do_stuff` function takes ownership of a request (as in, if it takes `Request` parameter and not `&mut Request` parameter) than the problem will be pointed by Rust, and so the compiler wouldn't allow you write code like this forcing programmer to write code that removes elements from the list to take ownership of them. For example:

for req in mem::take(&mut self.requests_to_process) {
do_stuff(req);
}

`mem::take` (https://doc.rust-lang.org/std/mem/fn.take.html) replaces an object behind a mutable reference with a default value for a given type (empty vector in case of vectors) and gives you an ownership over vector.
> It does not use vacuum:

IIRC, the proposed pressure was less than 1 kPa. That would be less than the pressure at the Karman Line, the boundary of space.
Good point. I've gotten hit by this in monorepos but I probably just tried to merge instead of rebase. Both are crazy painful on large source bases.

It still takes forever!

I should replace that with 'most commits in history are irrelevant to you, so you have to dig smarter to understand what's been going on with your components'
Waymo is opening its fully driverless service to the general public in Phoenix
"Beginning today, October 8, we’re excited to open up our fully driverless offering to Waymo One riders. Members of the public service can now take friends and family along on their rides and share their experience with the world. We’ll start with those who are already a part of Waymo One and, over the next several weeks, welcome more people directly into the service through our app (available on Google Play and the App Store). In the near term, 100% of our rides will be fully driverless."

I am pleasantly surprised.
A New Factory in France Will Mass-Produce Bugs as Food
I think you might be underestimating the comfort and convenience of train travel.

> That’s almost 6 hours on the train compared to a 2 hour flight.

A 2 hour flight also has you getting to the airport early-ish (~1h), going through check-in and/or security (0.75-2.0h, 1.5h average in my experience), waiting for luggage upon arrival and navigating the airport (~0.5h), getting to center city from the airport (~1h). So in addition to 2 hours in the air, there's an additional cost of 1h+1.5h+0.5h+1h=4h, so that's 6 hours in total, and that's best case scenario.

I'd choose train travel over plane travel always, provided the trip is not more than a couple thousand kilometers and it's an express. Trains are spacious (in comparison), and you don't experience intense pressure changes, or the bad air conditioning that you have in planes. Air travel tires me out for the rest of the day; after train travel I find myself energetic enough to do things the same day.
Wasn't there a new edition of the book coming soon?
Racial Bias in Tech Has Developed the “New Jim Code”
Always use a monorepo.

There is zero difference between using repos to organize things or using folders to organize things, except for the fact that updated dependencies across repos require extra steps to update if they change. More repos = more annoyance.

Use folders to organize things because common sense.

Additionally, don't use classes to organize your code, use combinators.

Folders and combinators will solve basically imo 95 percent of all organizational problems related to design.

Things like micoservices, multiple repos, and Gof design patterns only serve to make the organizational problem worse.
The vast, vast majority of the 600k (methodology is questionable) cameras in London are private indoor CCTV cameras that don't monitor public areas.

TFA appears to be about government-operated cameras in public areas.

Comparing those two figures is apples to oranges.

That's not to say London doesn't have significant government operated camera installations. Most are road cameras used to optimise traffic light patterns, but there is also the "Ring of Steel" in the City of London which, at ~650, is probably the largest integrated surveillance camera installation in London.
Ok, beyond close friends who work at the top of a few of these fields telling me it’s not even a question, let’s try a quick google:

https://www.scimagojr.com/countryrank.php

https://www.natureindex.com/news-blog/top-ten-countries-rese...

https://www.nature.com/articles/d41586-020-01231-w

You are the one that’s confident in something you clearly don’t know and ignoring hard numbers.
Assange had first started to insinuate a connection to Seth Rich in 2016. He has had plenty of opportunities since then to share any supporting evidence, but he hasn't. That isn't due to any free speech issue.

Also Assange was still communicating with and receiving DNC documents from his source after Seth Rich was already dead. Seth Rich wasn't Assange's source.

https://www.nytimes.com/2019/04/20/us/mueller-report-seth-ri...
Where Gaming Begins | AMD Ryzen™ Desktop Processors
I've had -3 karma for about 6 years now. Kind of proud of it. My only comment was trying to be helpful with a link but it got downvoted a bit.
"Meritocracy was meant as a satire" is brought up as a rebuttal frequently but it's somehow never accompanied by an explanation of how the negatives Young brings up are relevant to the topic at hand. Based on a cursory search, a summary of Young's point in his satire seems to be that meritocracy had the undesirable consequences of demeaning/devaluing those who scored poorly on measures of merit and also triggering a societal arms race as people did whatever they could to improve their own and their children's measured merit, neither of which is salient to this discussion. He doesn't seem to say that meritocracy itself was ineffective. (Somebody please correct me if I am in error here.)

It's also worth noting that the same Wikipedia article that the parent poster points to says that the concept of meritocracy predates Young's coining of the word by centuries and also details its history of successful application by many societies in various eras.
I wonder how the defaults would be chosen on such a platform - especially for visitors that have no profile.
It seems like CNET has an angle here. Since when is complying with a warrant "giving away information" as they put it.
I actually tried to adopt Dart v1 line at a startup buying into the WebComponents (too) early. The weekly updates broke compatibility so much and often that it had to be abandoned. Just as well as it didn't survive or perhaps because.
Code is a repeatable (executable) list of instructions that can describe a process. Perform the instructions, execute the process.

Processes--and a good example is business processes like SOPs, etc.--have inputs and outputs.

An API is a name for that process, plus a description of the required inputs.

Can you copyright a name and a description of inputs for a process?
A "free speech" platform is not enough of a value proposition for mainstream users to migrate. The only people who will be incentivized to move will be toxic/fringe/controversial people and their followings. If you want to make a community for those people, go ahead. See gab.com, voat.com, 4chan.org, parler.com etc... All these places are similar to reddit/facebook/twitter but without censorship. However, the whole point of a "free-speech" platform is to encourage an open exchange of ideas. If you only serve one side of the political spectrum, what ideas are you exchanging? It's just an echo chamber.

My point is that a real competitor to reddit will be highly dependent on some technical innovation that convinces a "normal users" to migrate. Our only hope is that this new platform will be wiser in terms of censorship policies. No normal person is going to waste their time signing up, actively post, check, and sink their time into a platform who's whole pitch is "a twitter/reddit clone with less users, but you can say racial slurs".
Every single PC has had a button cell for the RTC. This is nothing as new as Fukushima.
Setting up Node the right way on Linux
BMWs have taken a big leap forward in reliability since the E36 and E46.
OP here.

I've started gathering data on KN95 mask prices after seeing the same KN95 products from AliExpress being sold for 10x prices on European marketplaces.
My goal with this project is to raise awareness about alternative marketplaces and fight price gouging.
The data is available on Github [1] and it will be hopefully useful for others as well.

Of course, one can be never certain which products actually qualify as KN95 masks, but my position is that, I'd rather be wearing a mask that has the required layers for a KN95 mask, than a surgical mask, even if it may not fulfill the filtration criteria, because of the better fit.

[1] https://github.com/abiro/mask-price-data
If a monorepo is generating multiple binaries, there’s no reason it can’t use separate compilation units. In many languages, separate compilation units give you that arm’s length separation you need, without introducing the problem of making breaking changes that you can’t reasonably detect prior to commit, because the code is used in some obscure module you don’t even have checked out.

For that reason, monorepos favor the new programmer, which makes it easier to ramp your team size.
It's a tradeoff. Yes, you can only remove something if all callsites are gone, need to take care of breaking changes etc, but on the other hand you have clear insight into that and individual components can't as easily drag behind and require you to keep old versions around/maybe even backport fixes/...

And ideally a monorepo workflow gives you the tools to a) find all callsites, b) run tests to ensure your changes won't break anything, c) apply changes in lockstep. Those tools are an engineering effort, but the equivalents for a large multi-repo setup are too.
Show HN: A free security focused QR Code reader – Dhiway SEQR
And in the amici briefs (though they're not called expert witnesses there)
Google, Twitter, and Facebook have open sourced their solutions to this. Bazel, Pants, and Buck. Each have some rough edges but I'm currently migrating a bunch of stuff to Bazel and the workflow and tooling for it is pretty amazing.
It's all good ;)
Show HN: I built a site to compare Presidential Candidates speeches side-by-side
Only if you're a low-effort and obvious troll, which unfortunately there seem to be plenty of.

However, smart trolls (of which HN also has plenty) learn to adapt to the local culture. HN will often permit trolling as long as it's civil, and the mods won't ban an account that posts frequent troll comments if it also sometimes posts high quality comments.
A vpn at best just increases the costs for multi-country collaboration, but doesn't prevent it. This is the federal government, not some local municipality.

Even your favorite swiss bunker vpn can be subpoena’d or tapped extrajudicially and you would never know