Live data from Hacker News

Using Goatse to Stop App Theft

joshcsimmons.com

281–290 of 464 posts

Re: Using Goatse to Stop App Theft

#281
post #63

Earlier quoted context omitted.

Came here to say the same thing. Unless you're one of today's "lucky 10,000"[0] who haven't ever encountered goatse before, there's no need to verify this :D [0] - https://xkcd.com/1053/ edit: folks the xkcd lucky 10k reference was a joke, settle down

Your joke really flips the meaning of the lucky 10000. Nicely done.

This is the "Lucky Pierre" type of lucky.

If you don't know what that is, you might not want to search it.

Re: Using Goatse to Stop App Theft

#282
post #29

Very much NSFW lol https://wordlewebsite.com/sqword

it doesn't work in an incognito window (first thing I tried) but does in a regular window. @joshcsimmons it seems like sqword is reading local storage on this line: this.localStorage = n.localStorage || globalThis.localStorage, which leads to the following error: "Uncaught DOMException: Failed to read the 'localStorage' property from 'Window': Access is denied for this document." you should do it in a try/catch.

I'll note that this is a side effect of incognito blocking third party cookies, and I wouldn't bother changing it for that purpose.

But I guess it can happen on the original site if the user turns off cookies entirely.

Re: Using Goatse to Stop App Theft

#283

Just keep in mind some kids might be playing these games. So while it might be satisfying to stick it to the sites that are stealing your code, you might traumatize a child.

No one is traumatized by seeing goatse. It is a right of passage for children to become true internet denizens, in fact.

Re: Using Goatse to Stop App Theft

#284
post #94
post #63

Earlier quoted context omitted.

Came here to say the same thing. Unless you're one of today's "lucky 10,000"[0] who haven't ever encountered goatse before, there's no need to verify this :D [0] - https://xkcd.com/1053/ edit: folks the xkcd lucky 10k reference was a joke, settle down

I've managed to never see goatse so far. Not because I'm new or innocent, but because I've learned my lessons. I don't think the 10,000 really applies to this situation. It's certainly not something that everybody needs to see at some point in their lives (or so I've been lead to believe).

Anyone who was a freshmen in college circa y2k saw it about 4000 times. It was one of the first images to which I became desensitized.

Re: Using Goatse to Stop App Theft

#286
post #141

I am absolutely not a lawyer, but I wouldn't do something like this for fear of falling afoul of anti-obscenity laws. For instance, the UK has a cyberflashing law which allots a two year custodial sentence for sending a graphic image (by any means) with intent to cause distress.

And yet Goatse persists, a quarter of a century and counting...

Re: Using Goatse to Stop App Theft

#287
post #76

Earlier quoted context omitted.

After tubgirl I vowed to never click on links people said I shouldn't. I've never seen goatse because of this rule. (I have been rickrolled a lot, but that's fine.)

It's a butthole. It's not some traumatic thing.

It's a picture of "a butthole" in the same way that a picture of a shotgun wound to the gut is "a stomach."

Re: Using Goatse to Stop App Theft

#288

Earlier quoted context omitted.

Both legally and morally, intent matters far more than these technical details.

I can't answer to the law, which besides will vary - and I reject the implication that a puerile prank is immoral. But that aside, taking it on as if there was any moral dimension, moral clarity is straightforward here: The parasite has to answer for the material it shows its visitors. If a butcher delivers outdated meat to nowhere, knowing his van will be hijacked, how can he possibly be blamed when the hijackers se…

But he can. He is clearly attempting to poison someone.

Re: Using Goatse to Stop App Theft

#289

Earlier quoted context omitted.

s/removes the disclaimer/exploits a browser 0-day/

There are much less weird links you can give someone if you have 0-day. I don't think that's a problem worth worrying about for the author.

It’s a problem worth worrying about for users who maintain whitelists of domains they allow JavaScript from.

Re: Using Goatse to Stop App Theft

#290

Earlier quoted context omitted.

> simply hard-linked to the resources It's fairly surprising to see that approach from pretty large brands/companies. Some Indian ISPs are kinda notorious in that they'll just link to huge image files on third-party sites and just let their 300 million customers hammer the poor site into the ground. I guess it saves them bandwidth, but they also run a huge risk of pissing someone off and have that asset replaced by s…

The isps can pretty easily set up a cache for things that are popular. There was a time when I worked for an ISP consultancy, where Netflix would literally give ISPs a prebuilt cache server iirc for free, and that was a win win for everyone. I shouldn’t be surprised that some shitty isp thinks it’s easier to hard link, but making a cache isn’t that hard.

A couple of years ago, the main submarine link connecting my country to the internet was damaged, and internet basically slowed to a crawl for a day. Could barely open anything.

But Netflix was running at full HD with no problem. So they must have had local cache's with the ISPs.

Post reply on HN