Other links on Twitter have the same #<user_id> schema.
From the FAQ:
> How do referrals rewards work? We offer rewards for referring new paid Founding Members. Every Founding Member is provided with a unique referral link that we use to track people who have signed up through referrals.
When you purchase a Grid Founding Membership, well give you a unique referral URL to share with your friends. For every person who purchases a Grid Founding Membership using your referral URL youll receive $32 of the proceeds refunded toward your order, until your Founding Membership has been paid for. That means if you get three friends to purchase, youll get your membership free.
Any recommendations for passing referral ids in a fully stealth fashion between domains, e.g., by reading the referrer attribute of the GET request? A django app?
People comping to mysite.com/refID could bypass the referral program and re-visit the base url mysite.com. I'm fine with this, but it's not cool from refID's point of view. The main problem is the person visiting via the referral link might wonder whether the refID really recommends mysite.com wholeheartedly, or out to make a buck.
As people started complaining that their links didn't work - which in fact, they did all along - we decided to leave it in the URL from now on. Such is life ;)
Screenshot: http://d.pr/i/PQcW
Also the font they are serving from AWS throws a failed to load error.
Gif: http://d.pr/i/14DRl
I'm on chrome too, and the only outrageous thing I see is the rectangles that line the middle of the page, which don't seem to serve any real purpose...
Overall, I think "make img into useful background for a full-width div" is a useful feature but I won't pay $8/mo for it.
I think this is also a great idea especially because we use AI for way to less nowadays compared to what we actually should have learned about AI the last 50 years.
It also spends most of the time showing the actual product instead of just Adam doing 'funny' things.
Looks nice in firefox (doesn't work in chrome)
* Store the normalized content of our users to per-site repos in Jekyll-like Markdown + Front Matter documents
* Store the actual pages our engine designs
This means users have full access to their content on both levels.