818 karma · joined February 17, 2008
CPU time building a query is rarely the business bottleneck until you're at a huge scale - scaling up the engineering team uniformly and having business logic at abstraction level closer to the rapidly evolving Product specs is the bottleneck that ActiveRecord solves for, and does pretty well.
If you'd like something that avoids object/hidden state - check out how Elixir/Phoenix's Ecto[1] was designed - it avoids many of the shortcomings of ActiveRecord and SLQAlchemy:
If you want strong consistency for S3 consider something like JuiceFS: https://JuiceFS.io
It wraps your S3 in a strongly consistent and fast POSIX API (aka regular mountable filesystem) and its way less expensive than EFS.
53 was granted a US Trademark on the phrase 'Paper by FiftyThree' on December 2013 for trademark categories 21 23 26 36 38 and it appears international category 9 with a first-used-in-commerce claim of March 2013.
53 are obligated to enforce their mark in those categories otherwise they risk losing it. This is the same reason Facebook goes after anything with 'face or book' that even vaguely seems similar. If they don't they risk losing the Facebook mark.
The law sides with the trademark holder as long as they enforce the mark.
As many people have mentioned, 'Paper' is generic and 53 didn't get the word 'Paper' by itself. It was granted the mark 'Paper by FiftyThree'. Since Facebook's app isn't called 'Paper by Facebook' this leaves some wiggle room if FB wants to challenge the claim if it heads to court. Facebook has deep pockets and good lawyers, so perhaps they've already calculated the risk and is willing to fight in court. 53 may not be able to afford that fight (cash or distraction wise).
TL;DR: 53 is obligated to enforce their Trademark and the letter to Facebook is a manifestation of that obligation. Unfortunately their mark isn't just on the word 'paper' so it will be interesting to see if this fades away or the parties head to court.
If that doesn't come up my email is in my profile. Happy to connect you directly with their CTO.
[edit: added new ticket #]
I'm a fan of Cloudflare and would love to have my client running again. Do you guys have a network hacker on staff we could connect them directly with to get to the bottom of things?
Also, one of my clients had to turn off Cloudflare this week because of customer complaints. They weren't using Railgun, but were getting too many false errors with HTTPS enabled (https -> cloudflare -> https server). They thought it might be an odd interaction with SPDY.
For Memcache users, configure Rails.cache to use Rails' built in :memcache_store:
http://api.rubyonrails.org/classes/ActiveSupport/Cache/MemCa...
For Redis fans, try :redis_store:
https://github.com/jodosha/redis-store
This covers Rails 3 caching pretty well:
http://broadcastingadam.com/2011/05/advanced_caching_in_rail...
Note for Rails 2: If I recall correctly, in Rails 2 fragment caching/action caching still uses the filesystem even if you have a cache_store set.
What the article doesn't say is Inktomi had a dual sided business. One side was in Caching Proxies the other was licensing a search API.
Inktomi decided to focus on the caching proxy business and de-emphasized their search product, only to watch the proxy business evaporate as internet bandwidth became cheaper/better.
The focus on a shrinking market (proxies) and the lack of focus on growing market (search) killed them. Had search been a priority from the beginning things may have ended very differently with Inktomi creating their own front end.
In case you miss the old color scheme, try this Stylish theme:
http://userstyles.org/styles/64637/gmail-google-mail-classic...
Follow Jason's post to fix icons and spacing:
http://jasoncrawford.org/2012/04/how-to-cope-with-the-gmail-...
[Disclaimer: I was asked to be an early investor in Friendster and chose not to]