skysight-inc/HackerNews huggingface dataset:
> he calls the original glass "delicate and jewel-like" but that merely describes surface texture, not how deep the colors were

Really? I interpret "delicate and jewel-like" as applied to stained glass as a comment on color and size.

It's hard for me to imagine it as a comment on a physical property like texture -- historically, jewels were valuable first for their color and then for their resistance to damage.

The color part is less true today -- we can cheaply make almost any color of glass -- but the "precious" stones are one and all a lot harder than glass is. Even when amethyst was very expensive... quartz is a lot harder than glass.

If "texture" refers to clarity, glass is a big improvement over natural jewels.
free mosquito nets would drastically get the death rate down
Some of us like to eat.
I would argue that, at the moment, economic development of former colonies is happening considerably faster than development in the former colonizers. And the evidence agrees with me. Take China, for example. Per capita income there has grown from $89 in 1960 to over $9000 today (constant 2018 dollars), a 100x increase. Over the same period, US per capita income grew from $3000 to $60,000, a 20x increase. The number of nations mired in desperate poverty drops every year, and the number of nations improving their economies rapidly grows.

The gap is closing.
The HN discussion contains links to archived versions at the very top.
When I first saw Hasura, it was AGPL licensed which makes it unusable in a lot of use cases so we passed on it. Looks like they converted it to Apache license two months ago. I suppose it is worth another look, I'm glad they made the change.
The normalized cache is the one of the main value props of Apollo Client. It optimizes reads, automatically updates queries without a refetch for some mutations, supports optimistic updates, and can also return partial data for large queries. If you don't need a cache, then you can use fetch, graphql-request, or even Apollo Link to fire off a simple GraphQL request. You also don't have to use our cache implementation (apollo-cache-inmemory) with Apollo Client. There are other implementations that make different tradeoffs.

For what it's worth, we are rearchitecting parts of the cache to support invalidation and garbage collection for Apollo Client 3.0. The only reason why we don't have it yet is because it's a tough problem to solve - one mutation could invalidate an infinite amount of queries. We're committed to solving this soon though because we know the community really wants it.
I'm surprised people are commenting on fake vs. real followers. Even if the 2M followers are real, that would not necessarily translate into selling T-shirts.

Do the T-shirts even look good? Is a T-shirt what people want? Why do I want another T-shirt when I have dozens of good-looking free ones already? These are the real questions.
We do this, but we've labeled our field very explicitly with something along the lines of "Please leave this field blank, it is for SPAM control.". We also provide a hidden error message if it is filled in to alert the user that it really should be blank.

It's also always place this field after the Submit button with the idea that a user with a screen reader would never make it that far. Bots still see it and add it to the post request since I don't think they care about the order of the form fields.
Statins have only ever been shown to help people who have had a heart attack, or were in imminent danger of one -- despite decades of effort by Big Pharma to find other benefits. (Big Pharma wants every drug they sell to be needed continuously from today until you drop dead. Statins would perfect because they are also extremely cheap to make.)

What we do know about statins is that they have terrible long-term side effects that might not put off somebody worried about dropping dead at any moment, but should give everyone else the heebie-jeebies.

They interfere with the liver's production of cholesterol, but we (like every other animal) need cholesterol to live.
I think we are potentially close to the best time to be alive.

There is a lot of work being done on reversing age related diseases, so maybe in another 30 to 100 years, we will reach escape velocity so to speak, and people will no longer die of "old age".

This assumes we don't make humans extinct through warfare.
Or, if you don't need the microwave so much as the oven part, I highly recommend the BReville Smart Oven (https://www.breville.com/us/en/products/ovens.html)
survivor bias? (just kidding)
No tears will be shed, I am sure, if Google has to pay some billions to fatten the already fat pockets of Oracle but the decision by the Federal Circuit being appealed here made a hash out of key legal foundational items that facilitate the very idea of interoperability in the computing world and therefore cries out to be corrected.

My comment at the time the decision was rendered: "This ruling will do what its [the Federal Circuit's] prior expansive reading of patent law did: it will set up a legal standard that invites lawyers and litigants to engage in endless second-guessing over copyright and fair use in areas of connectivity and inter-operability in the computing world and this in turn, as a standing invitation to litigate, cannot be good for future development." (See https://news.ycombinator.com/item?id=16691774 for fuller analysis)

The Supreme Court quite often fails to take up discretionary appeals even if the issues loom large for a particular industry or even if an important case was wrongly decided. Sometimes it does so to resolve conflicting rulings among lower federal courts on an important issue; other times, because a case raises important issues of public policy. Don't know if this case will fit the criteria (it didn't on its first cycle of appeal - see my comment here: https://news.ycombinator.com/item?id=9801251#9802457; also, https://news.ycombinator.com/item?id=4050490#4051761).

I have long been an advocate for solid protection of IP rights but the Federal Circuit here has almost fetishized the idea of copyright protection to the point where it has, in the API and fair use areas, become a caricature of itself. Strong correction is needed on the legal merits of the case.

Let us hope that the high level of interest in the tech community, as revealed by the number and quality of amicus briefs filed, will prompt the Supreme Court to intervene and bring soundness and clarity to an important area of law that affects the tech world in profound ways.
Maybe. Maybe not. They are pretty darn difficult. I’ve seen a few that are fairly straightforward to break. For the good ones, you’d need some quality CV tech and if what you have is that good then you’re probably better off using it for something other than breaking captchas in order to post comment spam for penis pills or whatever they are peddling these days.
I don't. I actually support recent calls for developing a means to give vasectomies (high percentage of which are reversible) to all newborn males. Therefore, having a child is the choice of both the male and female counterparts of a couple. I'd be stunned if more women didn't support this measure...
Ruby legacy code: Using the right AWS SDK version
I was transferred from a poorer middle school and my HS admin prevented me from going into the accelerated classes. I had a bad time in university and have not been able to return.

It hurts me every day. I hope it will get better, but I do not see it happening in this life.
It's clear from your comment you've not actually used the thing you are criticizing.

Nothing about the spec necessitates duplicating your DB schema.

In terms of the data models, you only need to spec out models based on what you want returned.

It's perfectly fine to have limited data models for only what's being requested in a specific use case.
Because it's transformative:

>The Transformative Factor: The Purpose and Character of Your Use

>In a 1994 case, the Supreme Court emphasized this first factor as being an important indicator of fair use. At issue is whether the material has been used to help create something new or merely copied verbatim into another work.

https://fairuse.stanford.edu/overview/fair-use/four-factors/

IMHO simply re-implementing an API is not creating something new. It's just redoing something that has already been done. A translation layer from one API to another is a new thing separate from the original API.
That's just moronic, I would even go as far that GraphQL is something only backend dev could love, the only benefits frontend dev gain using GraphQL is not having to wait on backend dev to change some random endpoint response. From a backend dev perspective GraphQL completely removes that chunk of work, solves the issue of over-fetching/under-fetching, and more importantly allows you to map your REST APIs into a single interface (and break your monolith into microservices transparently).

If you're API is a todo list CRUD, then yes, you prob don't need GraphQL.
The accepted NNT for antihypertensives is around 1 in 100 depending on the exact metric you use (http://www.thennt.com/nnt/anti-hypertensives-to-prevent-deat...).
See also: critical thinking
In the end all writing or speech is about communicating an idea.

My opinion is these people have learned it doesn't matter. If an idea can be conveyed in smsesque and still get the point across while being quicker to write, then why not?

I have a feeling power/authority/expert status matters here because the listeners will power through unclear communication just to gleam a glimpse of the underlying idea from this idol.
Having coded for Android and JavaME, I can say that JavaME would have never worked right in the smartphone space. It's whole process lifetime architecture is wrong for smartphones. It basically only works with one app running that gets killed on quit otherwise you kill your battery as if your phone doesn't go to sleep.
Those who put more time and effort into improving their craft get the choices and good jobs.

Are you willing to put in the effort to gain the opportunities?
I wholeheartedly agree with this comment... and find the way it's articulated refreshing. God forbid we say we hate something without someone being outraged. +1 to 98% hating Microsoft... but also kudos for VSCode and TypeScript.
I actually think it's a bit more complicated than that. For a large company trying to fill a ton of openings, I think where you went to college is actually an even more important filtering criteria (ie an Ivy League degree is almost an automatic pass from resume to phone screen), but the list of colleges that get a near automatic pass is larger.
I have happily used DO for small things, like hosting a Ghost blog, or running an Algo VPN, but I am a little surprised to see people doing bigger infrastructure with them - not that they deserve to lose everything for making that choice, but it seems like it would have been clearly riskier than AWS/GC/Azure?
In fact, the law is intended to protect your business from competition, when that competition is repackaging and reselling your original work. That's the entire point of intellectual property law.
Now that truly qualifies as a concise ELI5. Well done. :-)
Nice scaling numbers. Can you use Hasura without Kubernetes or Docker?
> And the same is true of immigrants and outsourcing.

You are right but from certain perspective immigrants and outshoreing (as available economic resource not as human beings of course) are a sort of Dutch disease. Instead for innovation and increased productivity companies reach for imported labor and outsourcing which will hurt the economy in the long run.
When you're "addicted" it is hard to get perspective.

Not sure about your situation or feasibility, but banning the activity for 30 days might clear the fog. There are blogs about journalists giving up Twitter temporarily for example.

Another angle might be explaining the difference between a creator and consumer.
I love your didactic tone, esp. when combined with HN's inability to handle a fundamental social problem:

"Class-- I don't care whether it's Jenny, Tommy, or that group of adult strangers who freely enter and leave our classroom. One way or another your bickering is going to stop!"
It's worth writing something in an ML or Haskell sometime. Functional programming is great, and it makes my code in things like JavaScript much more robust.
If google’s lawyers cannot explain the issues on a way that high intelligent lay people under stand it, then they aren’t doing their job.

Most issue at the Supreme Court are highly detailed in some other area of expertise: medicine, economics, foreign policy, agriculture, the environment.

And the court with the most experience in tech, the Fed. Cir. decided in a way that most here don’t like.
"I will gladly pay my proportion of what's necessary to keep the service running in order to avoid the "you're not the customer, you're the product" mentality."

Since both are complementary and independent revenue streams, why do you assume that you paying cash for something does not mean you will be monetized in other ways as well?
this is awesome. I ended up paying like $99 USD just to have a custom domain pointed to it.

When I asked if I could switch the domain they said "that will be another $99 USD please"

...I don't even know why I am writing on medium
FWIW (this is merely a single example): my current company (which includes two ex googlers among the five founders) specifically uses no google infrastructure (no gmail, no google docs, no cloud, photos, hangout etc).

Actually I exaggerate: three of us use google search.

Edit: Someone asked why but their comment was downvoted dead so I am amending my comment.

There were three reasons; privacy, features, and dependability.

The privacy one is well discussed elsewhere. Apart from paranoia (won't get into that), there are UX issues. For example on the shared google docs for our local Boy Scout troop I've seen patient's files accidentally shared by physicians, internal corporate documents from some Fortune 50 companies and the like. Clearly nobody shared those on purpose!

For features: we certainly don't want to build a dependency on chrome (the new IE). One of the team had to move a google acquisition from AWS to gcp and swore never to use the latter again. Gmail doesn't follow standards (e.g. IMAP, adding AMP to mail)...the reasons go on. many products simply aren't best in class (e.g. zoom works much better for us than hangouts); others are (google docs / sheets may not be best-in-features but seem to have the best simultaneous editing, better than Apple or Nextcloud/Collabra when the network is flakey)

For dependability: one is of course products and features getting randomly cancelled. The other is cases where one account gets cancelled and it wipes out all connected features. These stories are scary; some have appeared on HN.

All in all it's not worth the risks.
A Grimoire of Functions
It's 'similar to [the] JVM' in that the word 'stack' pops up when either is described. In most substantial ways, they are quite dissimilar.
Knowing what we now know, it would be surprising if that weren't the case. What's the likelihood of no bacteria figuring out that trick?

Given the selection pressures involved, we might even expect most gut bacteria to do that.
Legally dubious as you can't prove wether someone has read an email or not. Official correspondence has to occur through verifiable means (ex: having them login to a portal, certified mail) in order to handle the approval in order to stand up to a challenge in court.

I'm not a legal professional, and my advice shouldn't be taken as rule. Please consult an attorney.
After 10 years it will probably need more than just fuel. And doing maintenance in orbit, especially way out in the L2 point is easier said than done. Probably easier to build a new satellite with even more capability to replace it, except of course that the JWT is famously behind schedule and over budget and a more sophisticated replacement probably won't be any easier to build.
The state of Reality considers getting entrapped into hiring an underage prostitute to not be sexual assault, and insinuations about it being dangerous to leave him alone with women are vile trash.
It has more to do with nobody getting paid to teach you about systems engineering. Some search engine keywords to get you started are "distributed systems fault tolerance".
I've recently seen something similar when Paul Rigby launched his crowdfunding campaign for "Don't Do That, Donald" https://unbound.com/books/dont-do-that-donald/. With tens of thousands of followers, many teaser images posted over more than a year, an apparently well designed products, and a widely talked about subject, I thought he would hit his funding levels trivially, but it seems to be surprisingly slow going.
LOL

Oh..wait..
ESA in Europe has decent salaries and you don't pay income taxes from them
So it DOES matter, after all. Screw up enough at job and your ability to eat goes away.
The other replies are correct, but there are also subtler problems that title insurance can cover. One example I remember reading about was an old surveying error that resulted in an inlaw unit encroaching 6 inches on a neighbor's property. If such a problem is discovered, the insurance company might negotiate with the neighbor to purchase a perpetual easement or, failing that, pay to have the inlaw unit either moved or altered to correct the problem.
No - it's just a very polite/formal way of singing a letter to royalty/gentry. Like "Yours sincerely" turned up to 11.
Hadoop pioneer MapR faces an uncertain future
So here we have an enormous article assailing dark mode, which at the veerrry end remarks:

"There will also be some excellent niche uses for Dark Mode. Let’s say you’re a musician who uses a MacBook Pro as part of your performance on a darkened stage. Even though the MacBook Pro will be harder and slower to use in Dark Mode, those downsides are likely worthwhile to avoid a bright glowing white light illuminating your face. Similarly, if you read at night on your iPhone while someone else is sleeping next to you, it’s only kind to switch to light-on-dark—whether in an ebook app or in iOS 13 if it does gain Dark Mode—to reduce the chance your insomnia will wake up your bed partner."

Er...
Controlling how the issue is framed has a larger impact than who wins. Whether APIs are copyrightable is beside the point and no matter who wins, we all lose:

If Google/Oracle can copyright APIs, then they are free to use their market positions to block competition because the very ability to inter-operate with other programs would be infringement, and their monopoly forces everyone to acknowledge their presence.

If Google/Oracle cannot copyright APIS, then they're free to use their market positions to snuff out upstarts by copying / re-implementing their programs.

Whether some method signatures are the same is just evidence suggesting copyright infringement, not infringement itself. I can write a song with some of the same words as another song. That doesn't answer the question of whether that's copyright infringement.
I don't understand why people are use the same browser for browsing and development.

I use Chrome for development. It has lots of helpful extensions, like the React and Redux devtools, extensions for cookie editing, screen measuring, JSON formatting and so on. I often need to forcibly restart tabs (or the entire browser) due to misbehaving devtools, so it's great having a dedicated browser for it. Same goes for cookies and local storage state. It's completely separate.

I use Safari as a browser. I has the basic extensions (adblocker, etc.) that I need personally. Its development tools are terrible, but that's okay — I only use them in the very rare case where a rendering/JS problem only shows in Safari.
Fulltext: https://www.gwern.net/docs/genetics/editing/2019-lovett.pdf
A table of contents, stripped of editing, is generally not copyrightable as is. It falls under mere listings of ingredients or contents exemptions.
No, I don't. Which only supports the copyrightability of the BIOS API, and the illegality of BIOS clones (and hence, early PC clones).
As an engineer and now an author of a technical book I definitely agree with this. I have seen many places where they have a talented engineering team that cannot communicate what they have created etc. to everybody else. The worse anti-pattern is when they hire technical writers with no knowledge of the domain (or dev skills) to create documentation on how to use API's targeted at developers... The end documentation from that effort, unsurprisingly, is often borderline incomprehensible.
I only recently started using Medium. I do like the audience aspect of it, but I also want my own personal website to mirror all of my content on Medium. As they don't have an API I'm actually working on something to periodically scrape my own Medium account and copy all the posts to my personal website so they can be seen at either place.

Although technically not that different from this project my objective would be not to switch over, but rather still use Medium's editor, but just have content mirrored.
The problem with this strategy is that IP Address/Domains/Hashes that are publicly available for free are typically dated and are rarely useful for catching anything other than mass scanning / ssh brute forcing or for doing retroactive searching and analysis.

You're also assuming that the linux server is the initial attack vector.

It is not uncommon for an org to be breached, and for the adversary to pivot to an admin box, and for the adversary to then gain control of a server using the admins legitimate credentials. All the while dropping persistence mechanisms along the way. Secure configurations and setups are always recommended and the above information is great advice. BUT it is also dated advice.

If you're not actively monitoring these servers and the activity on these servers they will eventually be popped. Logging all process/CLI activity is an awesome way to get started on monitoring, but if you're going that route, deploying Wazuh or an EDR tool can only add extra value by allowing you to create alerts off of specific values.
That company might've just been lowballing you. I'm much closer to your current salary at my job and I'm not management or a particularly senior developer. If that was a job direct from the government, they might've put you on the GS scale, which sucks (although you don't need as much in retirement savings if you have a pension that pays 40% of your salary)
I don't know much good on average wars do. For every good person fighting a tyrant, there's a good person fighting for the tyrant.
Slightly off topic, but one medicine that really does work is Accutane (Isotretinoin) for cystic acne, and I'm super grateful for it. If you still have acne, I highly recommend trying it.

I came across it on reddit a while back and it's basically solved my acne problem. You get a super dry face and chapped lips, but there are lots of products to help mitigate that.

The Accutane subreddit is full of tips and before/after photos - https://www.reddit.com/r/Accutane/
Uh, yeah. You are correct.

Sorry. I forgot which of the ex-DEC design groups got bought when. It's been a while.
wasn't there an experiment that used laser interferometry to calculate the precise distances between a constellation of three satellites? I assume something like that could work?
Or Oracle when they implemented SQL?
The key word being "if".

It sounds like he's just curious what people want Cloudflare to do for the GitHub audience instead of making a full Github replacement.
I think writing doesn't get anywhere near the attention ot should be getting.I've met and I work with some really great people but boy oh boy they struggle to write.I'm not talking about producing the next bestseller but simply communicating simple ideas. I read what some of them write I think: wtf...if you were only able to write better you could be reaching the sky.. Technical capabilities+ ability to communicate well in writing is a killer skill and can literally elevate people to a whole new level..