There are some great opinions posted so let me add some data from uspto.gov (use 'trademark search' from the menu) and a touch of what I understand of Trademark law after filing a few myself:
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.
And while I can appreciate their caution, changes in regulation are how new markets are made and the early movers become the winners. Fundersclub has the opportunity to be a first mover here, and instead they're ceding the opportunity. The hubris in the blog is amusing: You can only 'carry a big stick' when you're big. 7 digits is at least two orders of magnitude away from earning that level of cockiness.
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.
Just got off the phone with my client: They had an email exchange last week that was inconclusive. Then filed a support ticket this week when they had to turn Cloudflare off (business plan) and didn't hear anything back. I just had them re-file the ticket since it looks like Cloudflare had some support ticket issues.
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?
Did this happen yesterday? Did the client happen to be in Tokyo? We had a temporary issue in our Tokyo data center (related to our rollout of SPDY) that would have caused the symptoms you describe. It's fixed now and there's a check in place to confirm that SSL is answering properly before a server starts receiving traffic.
As a small addendum, I strongly recommend dalli (https://github.com/mperham/dalli) over the default memcached library. It is written by the former maintainer of the memcached gem, is smaller in size, up to 20% faster, and most importantly to me, is actively maintained.
Inktomi killed Inktomi long before Google helped put the nail in the coffin.
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.
Indeed. Inktomi also tried to position themselves as an arms supplier to the CDN business. It didn't help that the CDN business basically disappeared from 2001-2004, and that CDNs, to this day, rarely buy software.
I was going to mention this. It seemed like the management at Inktomi let it fall once the engineers started using Google search engines. Their response is a likely bellweather of the attitude of the time.
I can't fault Google for experimenting, but the 'all or nothing' approach they took to the rollout was an example of false choice. The classic coloring could have been offered as a theme to lessen the impact of the UX changes.
In case you miss the old color scheme, try this Stylish theme: