twitter://post?message=hello%world
in the current Facebook app? Lots of older posts indicate fb://publish/?text=helloworld once worked, but it doesn't seem to any longer.2,120 karma · joined January 4, 2011
Github: http://github.com/yahelc
Personal: http://yahel.com/
Manger, Data Science & Engineering @ DigitalOcean.
We're hiring!
Email: yc -at- do.co
twitter://post?message=hello%world
in the current Facebook app? Lots of older posts indicate fb://publish/?text=helloworld once worked, but it doesn't seem to any longer.Mostly out of curiosity (since I'm not looking for a new job), I switched my location to San Francisco Bay Area. And like magic, the recruiters immediately returned in full force.
My point was that it doesn't need to require much complexity at all; just an HTTP request served by the domain in question that passes along the cookies that need to be served from the new domain.
This is just what third party cookies are. Cookies set from the server-side (ie, the Set-Cookie header) can set whatever domain they want -- and if that cookie happens to not match the domain of the page you're on, that's what's called a third party cookie.
Some browsers (primarily Safari IIRC), however, will automatically reject those cookies, either in all instances or depending on if you've interacted with that domain before.
Default behaviors:
HTTP->HTTP: Referrer
HTTP->HTTPS: Referrer
HTTPS->HTTPS: Referrer
HTTPS->HTTP: No Referrer :(
I've seen people bypass this by either:
1. Having a HN specific URL (sometimes just ?hn attached to the URL)
2. Just having HTTPS landing pages.
One thing that could help fix this behavior (on newer browsers) would be for HN to explicitly authorize passing the referrer using `<meta name="referrer" content="always">` or "origin"
EDIT: Filed a bug to get this implemented on HN, since Chrome and Safari support it, and Firefox support is ongoing: https://github.com/HackerNews/HN/issues/68
Here's the output for ga.js: https://gist.github.com/yahelc/00299f2e4a3c07cafa1a
Another popular one (switch "cloud" to "butt") has resulted in me finding image embeds from "buttfront.net" (and broken images) in page sources on a couple of popular websites.
Source is on Github: https://github.com/yahelc/emailguesser.com