chris: “Cake is written with a lot of custom code and and a heavy dependence on third-party services. It took a small team of engineers and designers to build it and my expectation was we could raise some significant capital to sustain the team and add more for an Android app, etc. On our list of things to do was multiple images per post, private messages, good search, following people, improving the editor, feed, etc.
We attracted attention from the top-tier VCs and they circled but didn't commit to the big round because we didn't have enough growth. And that put us in the position of a chicken and egg problem we couldn't solve, even with patience.”
true that, some corner cases only appear in the wild and very hard to reproduce as we don't really know what caused them, anyways, keep us updated.. ;)
Duck.com domain name transfer hammered NamePros servers so hard that it singlehandedly uncovered a fairly obscure bug in Nginx's FastCGI caching. It's gone unnoticed for years, including during rigorous load testing.
Preliminary evidence suggests that fastcgi_cache_key doesn't handle $cookie_* variables correctly. If the cookie doesn't exist, it seems to result in a unique key every time. (The workaround was to assign the $cookie_* variable to another variable and then use that in fastcgi_cache_key.)
If anyone is curious what sort of increase in traffic you should expect from a link to your site appearing on HN, NamePros is getting about 230 additional backend requests per second--that doesn't include anything cached by Cloudflare.
this exactly describes Google policy on small fish, by neglecting their concerns, Google gets a lot of negative reputation from small startups who spread the word on forums like this, making their technical innovation largely irrelevant to their future success
why not just use the Private / incognito mode every time you want to use Facebook directly or indirectly?
That way any Facebook-owned service like logins and website comments plugin will work as expected but will not follow you around in your regular browser window!
________________________
From the extension page:
> "Clicking Facebook Share buttons on other browser tabs will load them within the Facebook Container. You should know that using these buttons passes information to Facebook about the website that you shared from."
> "Because you will be logged into Facebook only in the Container, embedded Facebook comments and Like buttons in tabs outside the Facebook Container will not work. This prevents Facebook from associating information about your activity on websites outside of Facebook to your Facebook identity.
> In addition, websites that allow you to create an account or log in using your Facebook credentials will generally not work properly. Because this extension is designed to separate Facebook use from use of other websites, this behavior is expected."
yes, why not just use the Private / incognito mode every time you want to use Facebook directly or indirectly?
That way any Facebook-owned service like logins and website comments plugin will work as expected but will not follow you around in your regular browser window!
________________________
From the extension page:
> "Clicking Facebook Share buttons on other browser tabs will load them within the Facebook Container. You should know that using these buttons passes information to Facebook about the website that you shared from."
> "Because you will be logged into Facebook only in the Container, embedded Facebook comments and Like buttons in tabs outside the Facebook Container will not work. This prevents Facebook from associating information about your activity on websites outside of Facebook to your Facebook identity.
> In addition, websites that allow you to create an account or log in using your Facebook credentials will generally not work properly. Because this extension is designed to separate Facebook use from use of other websites, this behavior is expected."
i think the potential for F# just got bigger and better with a brighter future!
this pretty much highlights the whole movement at Microsoft +Xamarin:
(and directly answers most of the questions in this thread)
Microsoft intends to make Xamarin's job a lot easier and realign its developer-oriented strategy in the same direction
Delivering on its promise to support cross-platform development, Microsoft is providing the full .NET server stack in open source, including ASP.NET, the .NET compiler, the .NET Core Runtime, Framework and Libraries, enabling developers to build with .NET across Windows, Mac or Linux. Through this implementation, Microsoft will work closely with the open source community, taking contributions for future improvements to .NET and will work through the .NET Foundation.
“A strong, open source, cross-platform CLR opens significant new options for building large server-based systems,” said Brian McCallister, chief technology officer, Groupon. “This significantly expands the choices developers have when finding the right tool to solve their problem. I’m very excited to have access to the quality virtual machine and tooling of the CLR without having to completely rework our production infrastructure in order to run it!”
____
this will be of great interest to those already using the CLR as it gives more incentive to those developers / dev shops
i Think the best analogy to this situation: Oracle (or its predecessor) published a cookbook and it tries to indemnify anyone profiting from it, like a restaurant or catering service that utilizes the same recipes compiled therein..
the cookbook in itself has copyright, but utilizing the instructions from it for your own food or business is not exactly the same as republishing the cookbook itself or redistributing it
imagine if someone could copyright the way we make grilled cheese sandwiches
We attracted attention from the top-tier VCs and they circled but didn't commit to the big round because we didn't have enough growth. And that put us in the position of a chicken and egg problem we couldn't solve, even with patience.”