HNHacker News
TopNewBestAskShowJobs

tpmoney

2,887 karma · joined October 23, 2019

submissionscomments
tpmoney··on FFmpeg to Google: Fund us or stop sending bugs
To be clear, what does relicensing to AGPL do here? Does the AGPL include licensing terms that forbid filing bug reports without also including code patches? Or does it just make ffmpeg that much less appealing to projects and cut off the steady stream of contributions that it has gotten from google since 2009? https://git.ffmpeg.org/gitweb/ffmpeg.git/search/HEAD?pg=3;s=...
tpmoney··on FFmpeg to Google: Fund us or stop sending bugs
> They see the profit being made, and they're not even getting drops of it.

Doesn't google routinely contribute to ffmpeg? Certainly there's a lot of commits from `@google.com` email addresses here: https://git.ffmpeg.org/gitweb/ffmpeg.git?a=search&h=HEAD&st=...

tpmoney··on FFmpeg to Google: Fund us or stop sending bugs
If it takes 3 seconds to fix it, then how is this some massive burden on the maintainers? The bug report pointed to the relevant lines, the maintainers are the most familiar with the code and it probably would have taken them 1.5 seconds to not only fix it, but validate the fix. It probably took more time to write up the complaint about the bugs than to implement the fix.
tpmoney··on FFmpeg to Google: Fund us or stop sending bugs
> In addition to your point, it seems obvious that disclosure policy for FOSS should be “when patch available” and not static X days.

So when the xz backdoor was discovered, you think it would have been better to sit on that quietly and try to both wrest control of upstream away from the upstream maintainers and wait until all the downstream projects had reverted the changes in their copies before making that public? Personally I'm glad that went public early. Yes there is a tradeoff between speed of public disclosure and publicity for a vulnerability, but ultimately a vulnerability is a vulnerability and people are better off knowing there's a problem than hoping that only the good guys know about it. If a Debian bug starts tee-ing all my network traffic to the CCP and the NSA, I'd rather know about it before a patch is available, at least that way I can decide to shut down my Debian boxes.

tpmoney··on FFmpeg to Google: Fund us or stop sending bugs
Where in this bug report was there any expectation for a response? They filed a private bug report and have a policy of making private reports public in 90 days whether or not they get a response. How did the OSS world go from "with enough eyes all bugs are shallow" to "filing a bug report is demanding I respond to you"?
tpmoney··on FFmpeg to Google: Fund us or stop sending bugs
ffmpeg is already LGPL / GPLv2. How does the license choice factor into this at all?
tpmoney··on FFmpeg to Google: Fund us or stop sending bugs
So to be clear, if Google doesn't include patches, you would rather they don't make bugs they find in software public so other people can fix them?

That is, you'd rather a world where Google either does know about a vulnerability and refuses to tell anyone, or just doesn't look for them at all, over a world where google looks for them and lets people know they exist, but doesn't submit their own fix for it.

Why do you want that world? Why do you want corporations to reduce the already meager amounts of work and resources they put into open source software even further?

tpmoney··on FFmpeg to Google: Fund us or stop sending bugs
So no one should file public bug reports for open source software?
tpmoney··on FFmpeg to Google: Fund us or stop sending bugs
> When you publicize a vulnerability you know someone doesn't have the capacity to fix according to the requested timeline, you are simultaneously increasing the visibility of the vulnerability and name-calling the maintainers.

So how long should all bug reporters wait before filing public bugs against open source projects? What about closed source projects? Anyone who works in software knows to ship software is to always have way more things to do than time to do it in. By this logic, we should never make bug reports public until the software maintainers (whether OSS, Apple or Microsoft) has a fix ready. Instead of "with enough eyeballs, all bugs are shallow" the new policy going forward I guess will be "with enough blindfolds, all bugs are low priority".

tpmoney··on FFmpeg to Google: Fund us or stop sending bugs
Since when are bug reports blackmail? If some retro game enthusiast discovered this bug and made a blog post about it that went to the front page of HN, is that blackmail? If someone running a fuzzer found this bug and dumped a public bug report into github is that blackmail? What if google made this report privately, but didn't say anything about when they would make it public and then just went public at some arbitrary time in the future? How is "heads up, here's a bug we found, here's the reproduction steps for it, we'll file a public bug report on it soon" blackmail?
tpmoney··on FFmpeg to Google: Fund us or stop sending bugs
But how are those companies supposed to know they need to do anything unless someone finds and publicly reports the issue in the first place? Surely we're not advocating for a world where every vendor downstream of the ffmpeg project independently discovers and patches security vulnerabilities without ever reporting the issues upstream right?
tpmoney··on FFmpeg to Google: Fund us or stop sending bugs
Great, so Google is actively spending money on making open source projects better and more secure. And for some reason everyone is now mad at them for it because they didn't also spend additional money making patches themselves. We can absolutely wish and ask that they spend some money and resources on making those patches, but this whole thing feels like the message most corporations are going to take is "don't do anything to contribute to open source projects at all, because if you don't do it just right, they're going to drag you through the mud for it" rather than "submit more patches"
tpmoney··on FFmpeg to Google: Fund us or stop sending bugs
How is having a disclosure policy so that you balance the tradeoffs between informing people and leaving a bug unreported "holding" anything over the heads of the maintainers? They could just file public bug reports from the beginning. There's no requirement that they file non-public reports first, and certainly not everyone who does file a bug report is going to do so privately. If this is such a minuscule bug, then whether it's public or not doesn't matter. And if it's not a minuscule bug, then certainly giving some private period, but then also making a public disclosure is the only responsible thing to do.
tpmoney··on FFmpeg to Google: Fund us or stop sending bugs
What's "strictly legal or required" of Google here is absolutely nothing. They didn't have to do any auditing or bug hunting. They certainly didn't have to validate or create a proper bug report, and there's no requirement whatsoever that they tell anyone about it at all. They could have found the bug, found it was being actively exploited, made their own internal patch and sat quietly by while other people remained vulnerable. All of that is well within what is "strictly legal or required".

Google did more than what is "strictly legal or required", and what they did was submit a good and valid bug report. But for some reason we're mad because they didn't do even more. Why? The world is objectively a better place for having this bug report, at least now people know there's something to address.

tpmoney··on FFmpeg to Google: Fund us or stop sending bugs
But if no bug report is filed, then only google gets the ability to "be responsible for their own security", everyone else either has to independently discover and then patch the bug themselves, or wait until upstream discovers the bug.

In no reasonable reading of the situation can I see how anything Google has done here has made things worse:

1) Before hand, the bug existed, but was either known by no one, or known only by people exploiting it. The maintainers weren't actively looking at or for this particular bug and so it may have continue to go undiscovered for another 20 years.

2) Then Google was the only one that knew about it (modulo exploiters) and were the only people that could take any steps to protect themselves. The maintainers still don't know so everyone else would remain unprotected until they discover it independently.

3) Now everyone knows about the issue, and are now informed to take whatever actions they deem appropriate to protect themselves. The maintainers know and can choose (or not) to patch the issue, remove the codec or any number of other steps including deciding it's too low priority in their list of todos and advising concerned people to disable/compile it out if they are worried.

#3 is objectively the better situation for everyone except people who would exploit the issue. Would it be even better if Google made a patch and submitted that too? Sure it would. But that doesn't make what they have done worthless or harmful. And more than that, there's nothing that says they can't or won't do that. Submitting a bug report and submitting a fix don't need to happen at the same time.

It's hard enough convincing corporations to spend any resources at all on contributing to upstream. Dragging them through the mud for not submitting patches in addition to any bug reports they file is in my estimation less likely to get you more patches, and more likely to just get you less resources spent on looking for bugs in the first place.

tpmoney··on FFmpeg to Google: Fund us or stop sending bugs
On the other hand, if the bug doesn't get filed, it doesn't get fixed. Sure Google could spend some resources on fixing it themselves, but even if they did would we not likely see a complaint about google flooding the maintainers with PR requests for obscure 30 year old codec bugs? And isn't a PR even more of a demand on the maintainer's time because now there's actual code that needs to be reviewed, tests that need to be run and another person waiting for a response on the other end?

"Given enough eyeballs, every bug is shallow" right? Well, Google just contributed some eyeballs, and now a bug has been made shallow. So what's the actual problem here? If some retro game enthusiast had filed the same but report would that be "abusing" the maintainer's time? I would think not, but then we're saying that a bug report can be "abusive" simply by the virtue of who submits it. And I'm really not sure "don't assign employees to research bugs in your open source dependencies and if you do certainly don't submit bug reports on what you find because that's abusive" is the message we want to be sending to corporations that are using these projects.

tpmoney··on FFmpeg to Google: Fund us or stop sending bugs
I get that the ffmpeg people have limited time and resources, I get that it would be nice if Google (or literally anyone else) patched this themselves and submitted that upstream. But "everyone else down stream of us should compile out our security hole" is a terrible way to go about things. If this is so obscure of a bug that there's no real risk, then there's no need for anyone to worry that the bug has been reported and will be publicized. On the other hand, if it's so dangerous that everyone should be rebuilding ffmpeg from source and compiling it out, then it really needs to be fixed in the up stream.

Edit: And also, how is anyone supposed to know they should compile the codec our unless someone makes a bug report and makes it public in the first place?

tpmoney··on Drilling down on Uncle Sam's proposed TP-Link ban
“Core performance” only matters relative to what the company is selling you though. For example let’s say a company sells 2 tiers of switch. One does 10G and the other 1G. For whatever reason when they start selling these, it’s cheapest for them to sell the same internal hardware, but with the internals underclocked in software. Some hardware hackers discover this and start unlocking the 10G capabilities of the 1G units. Later down the road, the company finds a cheaper implementation of hardware for the 1G that still can do 1G but even if up-clocked can now only do 2.5 at best. That’s a change to “core performance” but it’s also not fraud. They didn’t advertise or sell you a “switch that starts at 1G but can be unlocked for 10G”, they sold you a “switch that can do 1G”. As long as that’s what they’re still selling you, everything else is ancillary.
tpmoney··on Contributing to open-source should be required, like jury duty
On the other hand, there’s a good argument to be made that if you think the judiciary can be captured for political ends, a trial and verdict by your peers at least gives you the opportunity to get a fair(er) shot. And in many (most?) US jurisdictions you can waive your right to a jury trial and ask for a bench trial instead.
tpmoney··on Drilling down on Uncle Sam's proposed TP-Link ban
It’s only fraud if they sold you or marketed to you on those specs. But at least for things like reflashing your router, short of a few explicit opener vendors (like glinet) and Linksys AFTER releasing the WRTGL version, router manufacturers aren’t usually advertising on how much ram or flash memory space they have, any more than car manufacturers are advertising how much flash memory is in their ECUs. It’s not an intended or marketed purpose, so they’re not going to be changing model numbers just because they made an internal update.
tpmoney··on AI is Dunning-Kruger as a service
We’ve been down this road before. Wikipedia was going to be the knowledge apocalypse. How were you going to be able to trust what you read when anyone can edit it if you don’t already know the truth.

And we learned the limits. Broadly verifiable, non-controversial items are reasonably reliable (or at least no worse than classic encyclopedias). And highly technical or controversial items may have some useful information but you should definitely follow up with the source material. And you probably shouldn’t substitute Wikipedia for seeing a doctor either.

We’ll learn the same boundaries with AI. It will be fine to use for learning in some contexts and awful for learning in others. Maybe we should spend some energy on teaching people how to identify those contexts instead of trying to put the genie back in the bottle.

tpmoney··on AI is Dunning-Kruger as a service
But you can expect to learn in both cases. Just like you often learn from your own failures. Learning doesn’t require that you’re given the right answer, just that it’s possible for you to obtain the right answer
tpmoney··on IKEA launches new smart home range with 21 Matter-compatible products
> Neither Matter nor Matter-over-Thread require Internet access.

The protocols themselves might not but as a warning to people looking for “matter” as an indicator they can have local only control, apparently the matter spec doesn’t require local only setup. I bought Honeywell’s new matter thermostat and in order to get the QR code and keys you need to register it to a matter controller, you first have to download their app and connect the thermostat to their cloud, so that you can get the keys from the app. So the matter capabilities are still useless

tpmoney··on FBI tries to unmask owner of archive.is
My pie in the sky pitch is the US Government (and others) should solve this, the legality and the compensation problems in a single swoop. Make submission of your work to a federal model data set a requirement for obtaining copyright protection. License the data set (and heck maybe even charge for making custom models) for nominal fees to anyone who want it, with indemnification against copyright lawsuits for works deriving from the licensed model. Pay copyright owners a limited time royalty from these licensing fees. Everyone wins and we can stop needing a billion bots scraping a billion sites billion times a day.
tpmoney··on AI and Copyright: Expanding copyright hurts everyone
That's certainly an argument often made about counterfeit goods, and it can certainly be true in cases (and counterfeiting has other problems, namely confusing the origin of a specific good when that matters to the consumer), but it's also not a universal truth either. Were it a universal truth, that would imply generally that open source can't work because anyone can make and distribute copies of the open material, but also it implies that Windows and macOS should not exist because of all the innumerable Linux clones.

Also instructive would be the IBM BIOS clone, it is perhaps true that the "IBM Compatibles" killed the market that existed for IBM machines at that moment in time, but it's also true that it opened whole new markets, both to the clone makers and the ancillary businesses, but also arguably IBM themselves.

3d printing and Arduino are probably other examples where "counterfeits" might have shrunk the market for the originals (Prusa is notably reducing how open their designs are, and Arduino themselves are not the healthiest, modulo being owned by Qualcom now), but the market for Aruduino projects and ancillary supplies and certainly the market for 3d printers is massively healthy, and arguably both are healthier than if Arduino or Prusa (or really Reprap) were the single and sole providers of their products.

And I think art has an even stronger bulwark in that a lot of the value of a given "art" comes not from the art itself, but from the artist. It's very possible many famous artist's works were actually made by their apprentices, but until someone proves that, the art will continue to have value as an original work of the artist. But art is also a dime a dozen (or less). The internet is full of free or dirt cheap art and today you can go on fiver or mechanical turk and commission any number of artworks for probably less than your day's wages. But no one is buying tickets to your Fiver concert. No one buys $1k per plate dinners at Deviant Art gallery showings. But they will pay many thousands of dollars for a piece of artwork that might destroy itself because the person who produced that artwork is named Banksy.

tpmoney··on AI and Copyright: Expanding copyright hurts everyone
> But that's the issue, isn't it? Someone has bought a legitimate copy and put it on Napster with the intention of providing copies to people when it's fair use.

To the best of my understanding of the law, making whole copies of a work for other people to then make fair use of is generally not considered fair use. There are some narrow cases where it has been; the two that come to mind are a case (whose name escapes me) that found reproducing an entire editorial for commentary and discussion on a discussion forum was fair use and a handful of cases regarding whether a print shop is liable for copyright infringements if a customer orders a copy made of a work.

Likewise the person downloading it can't be making fair use of the work unless they already have a copy of the work they have legally obtained. This was a key point of the Anthropic case, the use of legally purchased or acquired books was fair use, the use of the copies obtained only via piracy were not. I don't recall if Alsup addressed it specifically in his ruling, and to the best of my knowledge otherwise no rulings have ever been made on the legality of "I own a legal copy of this work, and I am acquiring a copy made from someone else's legal copy for fair use purposes" (this is often the theory behind why downloading ROMs if you own the game already could be legal).

> How is it unlike borrowing a book from the library and quoting an excerpt from it in your criticism?

Libraries have been something publishers have hated for a long long while. They routinely try to extort massive amounts of money out of them (see separate pricing for "library" copies of media, maximum lending count limits on "library" ebooks etc). One of the reasons is that a library as you point out sort of puts a big dent in the "fair use derives from ownership / first sale doctrine" idea. Again, to the best of my knowledge, cases involving using library copies just tend to get their own set of rules, and are also probably just fewer and farther between because it's unlikely you can convince a library to let you just scan all of their books regardless of the legality of you doing so.

As for the partnership thing, my point was mostly that any legal entity that can jointly own property would have to be the owner of a work for people within that entity to distribute copies between each other, and that once a person leaves the legal entity they could no longer keep or obtain copies of works owned by the entity.

tpmoney··on Optimism associated with exceptional longevity (2019)
They said "controlling for demographics", which seems to imply pretty strongly that income is a controlled for variable if it's part of the "demographics" model. To get a better answer, you'd probably have to dig for the raw data
tpmoney··on Optimism associated with exceptional longevity (2019)
> For NAS, the demographics model includes baseline age, being white, being married, education, family income, and father’s occupation.

Not wealth specifically, but income is probably as good of a controlling factor.

tpmoney··on AI and Copyright: Expanding copyright hurts everyone
OpenAI's hypocrisy on this matter is precisely why hackers should be taking this as the best opportunity we've had in decades to scale back the massive expansions that Disney et al have managed to place on copyright. But instead of taking advantage of the fact that for once someone with funding and money can go toe to toe with the big publishers and that in doing so they will be hoist on their own petard, a lot of hackers appear to be circling the wagons and suddenly finding that they think this whole "IP" thing is good actually and maybe we should make copyright even stronger.

Surely making copyright even stronger (and even expanding it to cover style as some have argued in response to the Ghibli style stuff) will have no unintended consequences going forward into a future where more and more technology is locked down by major manufacturers with a strong incentive to use and abuse IP law to prevent competition and open alternatives... right?

tpmoney··on AI and Copyright: Expanding copyright hurts everyone
My argument is better framed that this:

> "stealing the work of every single artist, living and dead, for the sole purpose of making a profit"

is begging the question. The phrase "stealing" inherently presumes a crime has been committed when that is the very thing up for debate. The note that this is "for the sole purpose of making a profit" asks the reader to infer that one can not make a profit and also engage in fair use, and yet that is clearly not true. And that puts aside entirely that you're not referencing a "specific case" here, but generalizing to all forms of AI training.

We can start by examining the "stealing" phrasing, noting that up until fairly recently it was an axiom in a lot of "hacker" places that "copying is not theft". It feels somewhat contradictory to me to find that now that it's our work that's being copied, suddenly a lot of hackers are very keen on calling it theft.

We can note that a lot of our careers rest on the idea that copying is not prima facie a crime or theft. Certainly IBM wanted it to be so, and yet their BIOS was cloned and many of our careers were kickstarted (or at least kicked into high gear) by the consequences of that. Or how about the fact that despite what Apple would really like to be true, you can't stop people from copying your really cool idea from looking at it and making something similar. They couldn't win that battle against Microsoft, and they couldn't win it against Google or Samsung either.

We can talk about the fact that there is a lot of disagreement that the dead should have any IP rights at all. Notably again many "hacker" spaces were quite vocal about how the various "lifetime+" IP laws were actually detrimental to creativity and society. Until recently it was the Walt Disney corporation in their pursuit of making a profit that was one of the largest advocates for copyrights to be extended long after the creator was dead and gone.

We could also talk (again) about how many forms of fair use are pursued for "the sole purpose of making a profit". See the previous references to the IBM BIOS and the copying of Apple's GUIs. But there is also parody music like Weird Al, or Campbell v. Acuff-Rose Music. We can look also to the previously mentioned Connectix Virtual Game Station and other emulators or to the Oracle V. Google lawsuits. We can look at how TiVo's entire business model was to enable millions of people to create copies of copyrighted material every day, automatically. Or Kelly v. Arriba Soft (which is basically why you can do an image search today) and Suntrust Bank v. Houghton Mifflin (also relevant for the discussion re "the dead").

And again, most related to AI would be Authors Guild v. Google for the ingestion of thousands of copyrighted materials to in the pursuit of profit and creating the Google Scholar application. And application which I again note produces partial, but 100% faithful copies of that original work for the user and does so intentionally, something AI system actively try to avoid.

Which is why I started by asking you to walk the tech stack. If you think the law needs to be updated or you disagree with the current rulings on this matter, I can certainly understand that. So where do you propose drawing the line? What are the specific items that you feel distinguish training an AI from the various other fair use cases that have come before. Why is Google Scholar scanning in thousands of copyrighted materials with the express purpose of both making those materials searchable and displaying copies of that material ok, but an AI scanning in books with the express purpose of creating new material not ok? Why is Android, Windows, Gnome, KDE and other GUIs so very clearly copying the style (if not the works) of Apple ok, but Stable Diffusion producing new art works copying styles not?

← PreviousPage 12 of 34Next →