skysight-inc/HackerNews huggingface dataset:
Right, so the fact that this is the person complaining implies that it's not about fear at all, and is likely a far more legitimate concern.
I apologies if I just do not understand how the GH PR system works. I see approved/reviewed troll PRs. Maybe randoms can review/approve PRs? I assumed they had to be devs to approve PRs.
Did the same on the recommendation of a local merchant who sells soap and sundries while picking up some goods couldn't be happier.
So? Most of the developed world have legal systems that does believe in intellectual property. The fact that a few people "don't believe in intellectual property" because they want to torrent movies/games is mostly irrelevant when it comes to the software engineering profession.
Well this is some ideological drivel. The first area in the reports defines an increase in government size as a decrease in freedom.

I suppose my local metropolitan area would be considerably more free if we didn't have mass transit that allowed for a dense urban area and the economic activity that comes with. Perhaps we should disband the legal system that enforces contracts so that when a business hires another, they can anticipate actually getting what was agreed to.

Edit: It gets even more logically inconsistent as you go further into the report. They point out that they ranked China as 116 out of 165 jurisdictions and then two paragraphs later have this title

> Nations that are economically free out-perform
non-free nations in indicators of well-being
Because we helped make the weapon and have helpfully provided our fingerprints so that if someone else uses it we look guilty. If someone else releases something that looks like this variant the world now has a casus belli against us. (that is, those that don't already for our role in the original virus).
They had the famous pin drop commercials!
> Following this line of thought, do you think that all code from all software should be open source and publicly available

Let's help shape this thought: Copyright should be abolished entirely. It is one of many monetization schemes and its negative effects greatly outweigh its positives.

We know people won't stop writing software in the absence of copyright. We know they won't stop writing books, singing songs, etc. Copyright is not the primary motivator for either science or art.

Will we need new monetization structures? Of course. But generally speaking we already have them where it matters.

End copyright entirely.
If you take a function from a repository (or a sentence from a book), it is the unlicensed use of copyrighted material. Everything in the repository is covered by the license, functions, files… everything.

Whether or not it is infringement depends on if the use can be considered fair use. This is a more nuanced question and is not always clear.

In this case (Copilot) the real question is how transformative the AI training is. Given how verbatim some of the outputs are makes the argument less clear.
You're absolutely right.

Copilot and Dall-E (and so on) are all bad in the same way.

Many of us agree with you.
I’ve narrowed it down to the east coast of the US.
How exactly did you think "Any system less powerful than PA is trivially incomplete." conveyed any of this? You seem to be claiming two almost opposite things about PA.
I've been using email for the last few years, and just this month my bank made a change so that you MUST use a phone call or SMS. NO getting around it. Can't even use something like an authentication app... so I MUST have a SIM with an actual number.
We’ve had one heck of a decade.
> Working overseas without approval is usually a friable offense.

IOW, the chances of remaining employed will crumble.
Did they include "ladies nights" in their analysis?
This depends on the law in jurisdiction. For example... https://codelibrary.amlegal.com/codes/pompanobeach/latest/po...

> In all spaces marked for city administered public parking within the city, all vehicles shall be parked with the front end of the vehicle facing into the space provided for parking. It shall be unlawful for any person to back any vehicle into such parking space. No person shall stand or park a vehicle other than at the angle to the curb or into the roadway other than as indicated by signs or markings.

I recall this being the case in Palo Alto for city lots at one time and I believe that San Francisco city lots are similarly ordinanced.

Unless you know the city, it's safest to park "the standard way". No one wants to get a ticket in an out of state city.

Furthermore, there is some "unless you do have a backup camera, the backing into a spot between two cars is more difficult than going in forwards and then using the lot space upon leaving to properly orient."

Lastly, if you are to make use of the trunk of the car, most parking lots are set up to allow easier access when not backed in.
It says why in the linked post. People aren't doing open source for free; they do it for the community. But Copilot is there to extract value from it, giving nothing back, not even credit.
I don't think many people here would object if Copilot was trained on all the publicly available source code from before 1930.
you're making a big assumption here, that Microsoft did not learn from their mistakes.

I posit that they have indeed learned from their mistakes.

1) They train Copilot with repos hosted on github.com. 2) Users who upload code to github.com grant GitHub an explicit license[0] granting GitHub the right to show that code to others. 3) GitHub do not specify which technologies or techniques they may use to show this code to others, meaning they may use any technique they like.

Microsoft have learned. And they have covered their collective asses. Users who host code on github.com agreed to these terms.

Users who don't like their code showing up in Copilot should not be hosting their code on GitHub, because they agreed to have their code delivered to others when they signed up.

[0]: https://docs.github.com/en/site-policy/github-terms/github-t...
What hurts me the most is when I was told "it's not that simple" because I wanted a container enabled machine to put a container on that sits behind the public web server which forward requests to it (reverse proxy).

What I was told is that it doesn't scale and k8's is simpler because how does it talk to the database otherwise? Oddly enough, I'm not sure this person has ever _just_ worked with containers without k8's and so it all falls into a black box.

Which is odd, but all of this is to take roughly 100 servers and get them into the cloud.

At some point I have to wonder if it's even possible for many of these same people to work in a way that's simple.
> I would hope the answer is yes

Why? What does holding a pyrotechnician's license have to do with opening a bank account? Can you get a driver's license automatically as well when you are a pyrotechnician? The reason that bank accounts need proper identification is not something that I can comment on with authority, but whatever the reasoning is, it has nothing to do with whether you can carry and operate a firearm responsibly. The two have nothing to do with each other.
It doesn't matter what you believe. It matters what the judge and jury say when this goes to trial, and it will go to trial because Microsoft has a lot of money.
> This app requires a login info from a flight attendants to scrape their schedules.

So? If the flight attendants have provided their credentials to the scraping software, they have essentially authorized the software to scrape the data on their accounts. It's just a custom user agent running locally and the airline company has no business blocking anything.
Absolutely those are horrifically bad.

Now imagine humans can't even go within a few hundred meters to clean anything up, and we have no robots that can either.

Also imagine that humans can't live within 500km ever again.

Nuclear is clearly the best option, right up until the point it's the worst possible thing for humans and planet earth, which seems to happen about every 30 years or so. As I said, we've been lucky with it so far.
Perhaps, as the parent commenter suggested, we need a Universal Safety Net, then, instead of a strict UBI.
Microsoft got done because they were threatening vendors with punitive action if they didn't bundle Windows and IE by default.

Which is to say: Microsoft was taking specific action which wasn't a natural consequence of their software, but was being actively enforced to keep out competition. Vendors didn't organically discover consumers weren't interested in getting a PC without Windows and IE, they were prevented from even offering the option lest they be completely denied the ability to offer that at all.
So if it's fine to copy the pseudocode implementation of a non public use codebase, then you couldn't possibly object to recreating a codebase into a different language then, right?
While that certainly covers some code on GitHub, much of the code on there is just mirrored from other locations by non-owners: you can find copies of the Linux kernel and SQLite on GitHub, for instance. The users who upload those to GitHub have the right to do so (legally) but do not have any rights that they could grant to GitHub.
Unless the image generators routinely generate specific works produced by you (or other artists) then it’s not a directly comparable situation to Copilot.
>Copi­lot intro­duces what we might call a more self­ish inter­face to open-source soft­ware: just give me what I want! With Copi­lot, open-source users never have to know who made their soft­ware. They never have to inter­act with a com­mu­nity. They never have to con­tribute.

>Mean­while, we open-source authors have to watch as our work is stashed in a big code library in the sky called Copi­lot. The user feed­back & con­tri­bu­tions we were get­ting? Soon, all gone.

I don't see how you square the above complaint with this:

> First, the objec­tion here is not to AI-assisted cod­ing tools gen­er­ally, but to Microsoft’s spe­cific choices with Copi­lot. We can eas­ily imag­ine a ver­sion of Copi­lot that’s friend­lier to open-source devel­op­ers—for instance, where par­tic­i­pa­tion is vol­un­tary, or where coders are paid to con­tribute to the train­ing cor­pus.

Is an AI that was trained on opt-in or paid-for training data any less damaging? How would these choices have alleviated the problems described above?
It's the same reason someone thinks putting an entire OS behind the "doIt" function simplified everything.
I wrote it myself and it came out looking very similar. What do I do?
Why not describe the world space in integers? Where 1 is the Planck length of the simulation?

Is there a “lossy compression” benefit to describing space with floats?
>Virtual desktops with AWS via disposable credit card is pretty good, imho.

there's zero chance that you can create an AWS account with disposable credit cards, presumably for fraud/spam related reasons. Even many VPS providers will reject prepaid cards for the same reason.
Meanwhile ... for those of us back in reality ...

There is a reason for the legions of jokes about "deadlines and the wooshing sound they make as they go by".
We went to an amusement park this summer and they no longer give out paper maps of the park. We had to squint at the online map on the tiny screens of our phones.

It was a shame because I would have liked to give out maps to the kids so they could navigate/orient themselves.

A few days afterward, I actually went to the trouble of printing nice legal-sized color versions of the map at Staples to give to the kids as mementos. Sure enough, they loved looking at and discussing those maps just like I did as a kid.

Next time we go I'm printing maps ahead of time so we can have them while we're there.
I think it's a gray area in the license. Much of the code was intended to be used freely and commercially by others, but not for AI training. It follows the license to the letter, but not the intent.

I expect we'll see new licenses appear making it clear whether or not the content can be used for training.
> vanadium is 6x as abundant

By mass. But a vanadium atom is more than 7x more massive than a lithium atom. So lithium is actually slightly more abundant by atomic % of the crust.
You could just re-sell it to someone else. Replacing something that works fine doesn't mean you have to throw it in the trash. Plus, a newer A/C probably has better efficiency anyway.
> Ignorance is bliss. Contaminated soils abound across the industrialized world, it's just that most people have no idea.

Absolutely right. And most of the industrial contaminates are a lot harder to detect than radiation. Even utterly minuscule amounts of radioactive isotopes are almost trivial to detect.
But fair use, as I understand it, is only about outputs, not inputs. (Licenses can apply to inputs.) A copyright violation occurs when one produces a work that infringes copyright. In this case, Google made digital copies of the books and showed snippets of the books to website visitors. Fair use refers to cases where producing that work is nevertheless legal.

The only analogy I can see is that copying the code internally to use in CoPilot training could be a violation of copyright (like how backing up your own MP3s is a violation of copyright?), but the licenses on these public repositories probably already allow that...
Yep, you need quite a bit of background knowledge, imho. And it's poor writing--just "notes to self".

If you have time look at the charts in the linked paper, "Empirically grounded technology forecasts and the energy transition"[1]. The "experts"--the International Energy Agency IEA, the National Renewable Energy Laboratories NREL, etc.--are getting things badly wrong, because of the limitations of their modelling software.

1. https://www.cell.com/joule/fulltext/S2542-4351(22)00410-X
This was posted yesterday in a tweet by "TheFrackingGuy"

Oh no, what happens when the wind stops blowing!

Furnaces would stop working because the blower fans that circulate the warm air are powered by electricity. Water pipes would freeze, and hundreds, if not thousands, of people would die from carbon monoxide poisoning when they attempt to keep warm by bringing charcoal grills inside or sitting in running cars in their garages, as occurred in
Texas during the blackouts of 2021

Big difference between Texas and Minnesota. Up North they plan for bitterly cold winters, including what to do if there isn't enough wind. Texas, on the other hand, sees a cold snap as a natural disaster.

I'm surprised they don't repeat Trump's claim that windmills give you cancer
It can be if you fail to give attribution. Plagiarism isn't just unethical, unprofessional and immoral (not to mention evidence that the plagiarist is an uncreative dullard). It's illegal. How many words or sentences it takes to trigger a complaint is mostly governed by what it takes to prove a violation. The more material copied, the easier that can be. In this situation providing attribution (tooltip when you mouse over the code?) would probably satisfy 9/10 of potential complaints. But big companies usually won't make that kind of minimal effort without being hit upside the metaphorical head with a piece of metaphorical lumber (like with an actual lawsuit).
First you have to see that the tutorial uses Lean basically as a blackbox. All that is needed is that you can express proofs in it, that applying lean to proofs yields lean theorems, that proofs are enumerable, and that Lean is powerful enough to express the collatz conjecture and the halting problem. So you can replace Lean by any other such blackbox B, for example B = (first-order logic + ZFC), and the argument in the tutorial goes the same way. Therefore type theory or not is not an issue here.

What IS an issue is that to fully explain what "express the collatz conjecture in B" means, you need model theory. You are right, type theory often doesn't come with model theoretic semantics, but it can be done in a natural way even for type theories.

The paper you are referencing is on sci-hub, by the way: http://sci-hub.wf/10.1017/S1079898600010568
Is your code public?
> GitHub Copi-lot inves-ti-ga-tion

lol rarely see such aggressive use of soft hyphens in page titles
Electron star - seems oddly specific, though maybe not spelling it same way you do.
> It's not an oversimplification; it's the cruel reality of Canada outside of the major urban centres, where relatively tiny companies can flourish before either listing themselves on a foreign exchange, being purchased, or failing.

Sure, if you exclude the vast majority of the country, there's really not a lot there. ;--)

Seriously, by the kind estimates of statscan, outside the major population centers you have just over six and a half million people (and that's after the big bump from COVID-19 migration). I think those six and a half million are about as financially independent as you could reasonable expect from an economy that is expressly outside of even local financial & trade centers.

> Where I live, the local Forestry company has been barricading public access roads and using rentacops to drive people off Crown Land; and it's tolerated and allowed, because forestry companies are given great leeway to act above the law.

Very much unlike, say the US, where large corporations are routinely reigned in by government oversight? ;-)
There are publicly published datasets, updated regularly, and you can stream all the events happening on Github (which is how secret leaks happen) so you can stay abreast of new repositories.

https://www.gharchive.org/
http://ghtorrent.org/

also available on GCP as a dataset, provided by Github itself: https://console.cloud.google.com/marketplace/details/github/...
I'll admit it took me longer to connect the dots on this one but when I was tinkering with an image generator and it gave me a clear istockphoto watermark, I knew something was amiss.
One of the canonical examples of software reverse engineering is Phoenix Technologies producing a compatible BIOS for IBM PC. They did exactly what OP described - had one person look at (public but copyrighted) IBM source and produce an extremely detailed design document, then another team went and wrote a new BIOS from scratch following that document. The issue at hand was copyright, not patents.
As Canada has shown, that is no answer.
You are right.

But the OP doesn't state anything to the contrary.

You are what-abouting a completely sound, thoughtful, and helpful article about one small piece of the privacy puzzle.
>No longer do we need to pay 20,000 hours to learn one thing to the exclusion of all others we would like to try. Now we'll be able to clearly articulate ourselves with art, music, poetry. We'll become powerful beings of thought and expression.

I'm a 20000 hours person. Knowing what I know about what I do, it's real sad to see someone misunderstand what goes into creativity this egregiously. Prompt engineering is such an unbelievably watered down "version" of making a painting. It's like writing a page, or even a folder! of bullet points and handing it to a ghostwriter, then telling them "put the end result between Shakespeare and Poe".

That's not unleashing your creative voice. Unleashing your voice and acquiring technical skills in a chosen field are the same. If you endlessly mixed all the prior classical works, it doesn't matter how you weight them, it won't spit out Mozart. You're stuck in the gamut of the model, between the maxima points of each artist.

It's an incredible tool to generate stuff quickly, and to some extent it will help artists whose work depends on quantity over quality.
yep. people forget this (including me)
Based on some quick testing MERGE does not appear to cause id gaps, though that does make me wonder if it's able to do so by providing less strict guarantees than ON CONFLICT.
I just don't understand this at all. I publish my code as open source when I can because I want others to find it useful, either by using the software that I wrote or by reusing the code. If I didn't want that, I wouldn't publish the code. But I do want it, so I'm glad there's a way for people to access it more easily.

I understand the argument from an artist's perspective much more, since they don't really have the option to publish their work in a way that any AI or any other artist can't copy off of.
And all of it has been destroyed bottom trawling
Dang. Literally none of those things exist where I live in the US. In fact, there's a food truck that comes through every once in awhile that is still cash-only.
This is doubly annoying as a tourist or immigrant: no, I don't have a local phone number, I don't have a bank account here, and I don't want to install $APP that is ubiquitous in your country but controlled by $Evilcorp.

Examples from several different countries: getting around without rideshare/taxi hailing apps, 'self check-in' gyms, Covid-related QR codes to get into restaurants, stores that only take mobile payments, restaurants where the menu is only available by QR code.
At some point I might have somewhat agreed with you but not so much lately.

I've been using a lot of swift lately and it's one of the most expressive (and impressive) language of late.

I've been blown away by its terseness which leads to incredible functionality (SwiftUI is basically a DSL[1]) and robustness of the type system.

When it compiles, it will most likely not crash, unless I specifically said "doing!yolo-dumb!stuff!here".

I'll come out and say it, Swift might be the most advanced high-level language in terms of power vs. UX.

I'll also say that its compile messages, half the time, are like academia vomit thrown at the face of the developer -> that needs to improve.

[1] (which agreeably leaks a bit)
Sorry, this is a touchy topic since everybody likes to shit on so-called wine snobs.

With respect to food pairings, thankfully this is easy enough for you to try out yourself. Get some spicy Thai food and try it (blind) with a German Riesling versus a CA Cabernet, see if you prefer one over the other. By the way, you will probably be able to tell the difference between those two wines blind.

I think most writing about wine is probably pretty useless, but when it comes to pairing food and wine there are some useful heuristics. Just like you probably wouldn’t like mustard on your ice cream, you probably wouldn’t like a big CA cab with spicy Thai food.
Firepower - by Paul Lockhart. A history of military advances, of guns, big and small, mainly in the West, mainly after 1300. Very impressive overall, but for me the most eye-opening was the arms-race preceding WW1. Nothing in the Cold War arms race came close to that.

The Rules of the Game - by Andrew Gordon. This is a 50 year history of the battle of Jutland. Meaning, one of the most thorough accounts of the battle of Jutland, plus a very detailed history of the 50 years preceding it, and the military/cultural background that led to the events at Jutland unfolding the way they did. A little innocent spoiler: after reading this book, you'll come to appreciate (like me) that one of the most consequential events in the world history (at least of the last two centuries) was the collision of HMS Victoria with HMS Camperdown two decades before the start of WW1. What a tragedy. There's a good chance that if that collision did not happen, then WW1 would not have happened, because Great Britain would have still been un-challengeble on the seas.

Freedom's Forge - by Arthur Herman. How America mobilized itself on the economic front. Unleashing the US industrial production juggernaut seems like preordained in hindsight, but it was anything but that. This book is a page turner. Once you start it, you know that you'll finish it.
Is there an AI system for those dot woodcut prints ie WSJ?
When I said

> I now think you should either expose only a string message your user can just show their end user or an error that's much more specific so they can write code that intelligently responds to it.

a boxed trait object is the main way to implement an error that merely conveys a string message.