Easy answer: it’s not. Learning isn’t copyright infringement. Never has been and hopefully never will be.
13,246 karma · joined August 19, 2007
You can reach me by emailing my first name at my last name, on the .email TLD.
Easy answer: it’s not. Learning isn’t copyright infringement. Never has been and hopefully never will be.
This is a tiny minority of people, not “most people”.
This is not even remotely true.
What do you mean?
> Facebook and Google were one of the first major online services offering an "takeout" feature in service of data portability. FB had multiple rss feeds. It's graph API was around quite early due to demand.
There was a period of time years before the Graph API launched that was all over the place. Facebook couldn't decide how they wanted their platform to work, so they cycled through a bunch of ideas like APIs, FBML, etc. before “Operation Developer Love” and the Graph API happened. Until that point, you could access a load of personal info, but the data portability everybody cared about – the social graph – was off the table because competitors could use it to bootstrap their own social graph without users having to find and re-add all their friends again. You tried to mirror that, you risked losing your account.
Yes. Please read the entire sentence before replying:
> All the early Facebook access revolved around engagement and anything even remotely related to data portability was verboten.
2010 is years after the Facebook platform was launched.
Regardless, as people in that thread pointed out at the time, what he is referring to is not data portability. If you were building on the Facebook platform at the time, you would know that apps had pretty much free reign to soak up the personal info but the main thing people cared about in terms of data portability was the ability to use the social graph outside of Facebook. Facebook hated the idea because it would allow competitors to bootstrap their own social graph without having to find and re-add all their friends, so it was the one thing that everybody knew could get you booted off the platform.
This isn’t true. All the early Facebook access revolved around engagement and anything even remotely related to data portability was verboten.
If that’s the case, then the delete links were behind authentication, but DHH assumed that meant it was okay to ignore the HTTP spec. and use GET for unsafe actions. Lo and behold, authenticated users with the GWA browser plugin installed deleted all their data.
Then, instead of learning from the mistake and fixing his bug, he tried to detect GWA and hide from it. Sure enough, that failed and users experienced data loss for a second time. He still continued to blame GWA, calling it “evil” and “scary”. You’d think he’d be smart enough to figure out that he needs to follow the HTTP spec., but he couldn’t admit to being wrong.
Follow the specs, people!
https://blog.moertel.com/posts/2005-10-25-google-web-acceler...
https://slatestarcodex.com/2013/04/12/noisy-poll-results-and...
Right, but that is not what was said, so “summarising” it in that manner is not a good faith representation of their argument.
> a direct and meaningful impact on the quality and availability of our services.
You:
> user-facing delivery is sameish
I don’t see how you can think that is a fair summary or a good-faith argument.
I’ve noticed Astra doing this a lot as well.
> This is the weirdest thing to put in a comment you could simply not have made. If your time is so valuable why are you here commenting on HN?
It’s basic intellectual honesty. If nobody believes that they came up with it independently, putting it forward as if it’s a real argument is just a form of trolling. If I don’t believe it, you don’t believe it, and even the person who posted it doesn’t claim it’s original, you’re just baiting me to respond to a position nobody holds.
Do you believe that they actually came up with it independently? If you do actually believe this, then a discussion is not a waste of time. But if you aren’t willing to claim that position, it’s pointless me arguing against it because it’s just you deliberately wasting my time on something you don’t believe.
> aphorisms have value regardless of how many times they are used.
This is a cornerstone of the point I was making. You’re literally supporting the point I was making.
Do you think that they came up with it independently? If you aren’t willing to say you believe this, you are just asking me to waste my time arguing with a phantom opinion nobody holds.
“Just do it” is an incredibly common, generic phrase, but if a new shoe manufacturer chose it as their slogan, it isn’t plausible that they came up with it independently of Nike.
No. Plenty of people – not just “piracy advocates”, whoever they are – have pointed out that copyright infringement is not theft over the years. Learning, copyright infringement, and theft are three distinct things.
Learning isn’t copyright infringement.
Learning isn’t theft.
Copyright infringement isn’t theft.
These are all different statements, and all are true.
> There is an exposure to (and a gain from) a resource that is traditionally associated with a cost.
“Gaining exposure to” isn’t theft either.
Copyright isn’t some form of “super-ownership” that gives you absolute say over what happens to all copies of the work. It is very specifically a monopoly on the production of new copies, and even that is limited in many important ways and is not absolute.
There is a form of control over information that matches what you want copyright to be though - trade secrets. If you want legal protection that allows you to control knowledge, then it needs to be a trade secret.
Because the same sentence has been repeated practically word-for-word ad nauseam all over social media for years. What do you think is plausible - that they repeated something that is damn near omnipresent in the discourse, or that they never saw any of the many, many times it has come up and independently came up with the exact same formulation? They are perfectly able to step in and claim that it was their original thought if they want to.
Learning isn’t stealing. They didn’t take our culture away from us and nobody is “buying our culture back” from them. We never lost it; it never went anywhere.
This isn’t your thought; you are merely regurgitating a sentence we have all heard many times before, practically word for word.
Presumably you think there is value in posting yet another copy of that other person’s thoughts in this discussion, despite having spent no time or effort in thinking it up yourself.
Why is that? Is it because you think there is inherent value in the sentence you transcribed, in spite of the near zero effort you spent creating it? If you think anybody here should read it, then you have undermined your own point. If you don’t think anybody should read it, then you shouldn’t post it.
It was pretty obvious even back then that they were just people who didn’t want to learn something new and they would not listen to anything pro-CSS at all. In fact, developers who insist LLMs are not useful for development remind me of them a lot.
Anyway, the CSS Zen Garden was released, and it seemed to shut everybody like that up overnight. It conclusively won the argument that CSS sites could look as good as table-based sites and could even do things the table-based sites couldn’t.
Pay attention to what you are committing. Generally this means looking at what you have staged before writing your commit log message.
Pay attention to what is in your pull request. Generally this means looking at your commits / draft pull request before you ask for code review.
If anybody other than you sees crap in your pull request that should obviously have been ignored, it means you have failed to pay attention to what you are doing three separate times.
I’ve worked with and managed plenty of people like that and those are the people I least want doing something like this. Seeing the flotsam and jetsam of .DS_Store etc. are an early warning sign they aren’t paying any attention to what they push and the sooner that gets caught and addressed the better.
As I explained earlier, what we were actually trying to do was debug the problem, and reading the error message was a necessary part of that.
It’s weird you’ve cooked up this little fantasy that the error message was getting in the way when it was the most important thing in the whole process and that was the entire point of the anecdote.
> Reflexively dismissing error message popups is reasonable behavior because they're almost always unhelpful.
Not when you’re trying to debug the problem the error message is telling you about!