This is a list of Free Software network services and web applications which can be hosted locally. Selfhosting is the process of locally hosting and managing applications instead of renting from SaaS providers. https://reddit.com/r/selfhosted

The dots are white blood cells moving in the capillaries in front of the retina of the eye.[5] Blue light (optimal wavelength: 430 nm) is absorbed by the red blood cells that fill the capillaries. The eye and brain "edit out" the shadow lines of the capillaries, partially by dark adaptation of the photoreceptors lying beneath the capillaries. The white blood cells, which are much rarer than the red ones and do not absorb blue light, create gaps in the blood column, and these gaps appear as bright dots. The gaps are elongated because a spherical white blood cell is too wide for the capillary. Red blood cells pile up behind the white blood cell, showing up like a dark tail.[6] This behavior of the blood cells in the capillaries of the retina has been directly observed in human subjects by adaptive optics scanning laser ophthalmoscopy, a real time imaging technique for examining retinal blood flow.[7] The dots will not appear at the very centre of the visual field, because there are no blood vessels in the foveal avascular zone.

Some highlights: Most of this research is on college students who are currently in the context of institution-regulated learning. Spaced testing and information retrieval improves later retrieval even for items that people believe they have already learned. Massing (including cramming) helps, but more learning is achieved in the same amount of time by interleaving -- alternating between material. For example, the French mathematics curriculum with algebra and geometry learned in alt...

> This is literally an episode of Better Off Ted.[1] In it, the titular Ted is inadvertenly deleted from the company system when trying to correct a misspelling of his last name. Eventually, he is forced to interview for his own job as the system had already put out an ad for his replacement. I think the most striking part of it, and of the true story from the post, is the human factor - the idea that the humans involved looked to the system as an authority and followed its orders blindly.
I wonder what other examples there are of people blindly following technology - people driving into lakes because their GPS told them to, etc. Plus, as our society gets more and more dependent on these systems, we may lose out on the flexibility that human mediators and problem solvers once gave us. The human tendency to defer to authority may never be as terrifying as when that authority is held by an uncaring machine with a couple bugs.

> The episode about the black engineer who isn't detected by the motion sensors is basically straight out of HP's webcam fiasco[1](although the show takes it to the logical and hilarious extreme).

> Reminds me of Frank Herbert's ominous (fictional) prophecy:
“Once men turned their thinking over to machines in the hope that this would set them free. But that only permitted other men with machines to enslave them.”

In addition, it does nothing to mitigate even remotely significant scrape detection. Doesn't talk about request fingerprints, patterns, user agents and headers, multi region access, etc.
This is a hobbyists' guide to scraping under the radar. Fine at that scale but quite incomplete for anything remotely mature or wide reaching.

MTurk itself is not perfect and could use many improvements. Amazon has been absent from the project itself for a long time and provides minimal support and there is a lot of criticism over them changing their fee structure in a few weeks that may or may not lead to a decrease in tasks and/or pay. https://requester.mturk.com/pricing

I have been through waterfall, agile, scrum, "agile", "scrum", kanban, to-do lists. Yet, I cannot point to a single style of project management as a silver bullet. However, I have come to realize the following conditions improve the probability of success: small teams made up of scary-smart accountable people, given a well-articulated objective (not solution) and are left alone without distraction. Short of this, you almost always fall in the trap of micro-management.

And of course, if you have a GPU, recurrent neural networks (or other deep learning architectures) are the endgame for the remaining 10% of problems (a good example is SpaCy's DL implementation: https://spacy.io/). Or use those libraries to incorporate fasttext for text encoding, which has worked well in my use cases.

"Wow a little googling on this subject led me to sshuttle, which I've never heard of before but looks awesome"
sshuttle is indeed awesome - a viable VPN that requires nothing on the endpoint but a functioning ssh login (and python on the remote host).
So any host, anywhere, with no configuration (and no permission required by the operators) that you can ssh into ... is now a VPN endpoint for you.
Sibling comments in this thread are pointing out that ssh has this functionality already and that is true, but some configuration and maintenance (and understanding) is required. Not so with sshuttle.
ALSO:
We (rsync.net) sponsored the reworking of the ipfw target for sshuttle so that it now works properly on FreeBSD with the --dns option, etc. We also sponsored proper UDP tunneling for sshuttle on FreeBSD but I am not sure those patches are in a -release version of FreeBSD yet ...
You need to use FreeBSD 11.0 (not 11.1) and you need to:
git clone https://github.com/sshuttle/sshuttle.git
cd sshuttle ; git checkout c746d6f7db3efbad6caddea76bdf916c46cf5c6e
... and that will get you a working sshuttle on FreeBSD with --dns support.

Ryan Dahl, the creator of Node.js:
"That said, I think Node is not the best system to build a massive server web. I would use Go for that. And honestly, that’s the reason why I left Node. It was the realization that: oh, actually, this is not the best server-side system ever."
Full interview: https://www.mappingthejourney.com/single-post/2017/08/31/epi...

Cool! I could see why this would work well for teams and collaboration. Here's my hugo+aws pipeline for my personal blog.
Do editing, with hugo in server mode so I can WYSIWYG edit my pages. Then run a bash script:
#!/bin/bash

Instead of having an "observer" process that updates a table with the LSN you can just ask Postgres directly: The `pg_stat_replication` view has the last LSN replayed on each replica available: https://www.postgresql.org/docs/10/static/monitoring-stats.h...
Also, instead of updating the `users` table with the LSN of the commit - which creates extra write load - why not store it in the session cookie, then you can route based on that.
Another option is to enable synchronous replication for transactions that need to be visible on all replicas: https://www.postgresql.org/docs/10/static/warm-standby.html#...
Since this can be enabled/disabled for each transaction it's really powerful.

Why don't more companies resize images client-side first using <canvas> and then save the server some work by only asking it to verify the result (by resizing to the same size and) removing metadata?
This results in much faster transfer (10x less bandwidth used often for mobile uploads) and reduces server load by "farming" out the work to the clients.
https://developer.mozilla.org/en-US/docs/Web/API/CanvasRende...

Prophet is a procedure for forecasting time series data. It is based on an additive model where non-linear trends are fit with yearly and weekly seasonality, plus holidays. It works best with daily periodicity data with at least one year of historical data. Prophet is robust to missing data, shifts in the trend, and large outliers.

For reddit, all the content was submitted by Steve and Alexis at first, then they got a couple of friends to start submitting.
To make submitting for themselves easier, Steve made a special submit page that would also create an account at the same time, and then make the submission from that account.
After a while they noticed people they didn't know were submitting, and then PG mentioned them in an essay and things started taking off.
They knew they had something the first day they didn't have to submit anything.

If you're interested in a quad loaded with open source software right out of the box, take a look at the Sky Viper v2450 GPS. It runs about $150.
It runs full ardupilot code, has a ublox gps chip, a taoglas gps antenna, and the video board and transmitter software is open source.
It runs a tiny webserver that allows you to configure any of the ardupilot variables, and is compatible with most of the ardupilot ground control software.
http://sky-viper.com/product/info/V2450GPS-sdhttp://ardupilot.org/https://github.com/SkyRocketToys

1) start with pronunciation and spelling (Gabe created pronunciation trainers for most languages) 2) Learn some basic verbs (I need, I want, may I, to go, to take, etc) 3) Building up a large list of nouns 4) Start using iTalki with a partner very soon into your journey and keep track of what you dont know.

“If you were nineteen and starting out again, would you go to film school?
The best education in film is to make one. I would advise any neophyte director to try to make a film by himself”
I give same advice to aspiring developers.

There is an insider story about how these methodologies comes about. So there are few groups of people whose sole job is to do consulting on failed/late/over budget projects. Mind you, they don't write code but rather they observe how things are going and then prescribe process/management improvements (McKinsey style). Once in a while, these folks bump in to terrible projects and whatever they prescribed sometime works like a charm. In that case, they take that prescription on road and advertise the hell out in conferences, magazines, blog posts. Unlike regular developers, they have all the time in the world to do these activities. They write books and give interviews and by the media power of distributing information suddenly they pop out as process gods who knows how to fix any project. Eventually the new things starts to fad, people realize what works in project X didn't worked in Y, speaker engagements starts drying out and then these folks need new thing to repeat the cycle.
The obvious problem is that these folks prescribing the development process are not active developers. They are not even part of any real project over any long duration. They are in job of inventing and selling processes and handing out management advice as consultants. Whatever they prescribe, might have worked only in specific context and for specific symptoms, usually with huge dose of luck. Next time when you see new process fad, look up the history of originator of this process, what company he is part of, how much code has he written, how he makes money. You will know what I'm talking about.

One thing I like about this post is the story of how the feature came to be: Someone who understood redis very well, thinking about the problem over literally years, eventually resulting in a more targetted and goal-driven thinking, and even that "specification remained just a specification for months, at the point that after some time I rewrote it almost from scratch in order to upgrade it with many hints that I accumulated talking with people about this upcoming addition to Redis."
I've been thinking about this sort of thing for a while, wanting to maybe call it "slow code" (like "slow food"). This is how actual quality software that will stand the test of time gets designed and made, _slowly_, _carefully_, _intentionally_, with thought and discussion and feedback and reconsideration. And always based on understanding the domain and the existing software you are building upon. Not jumping from problem to a PR to a merge. (And _usually_ by one person, sometimes a couple/several working together, _rarely_ by committee).

- is one of the most overlooked methods of creativity
- It is physically (re-)enacting what you are brainstorming about
- Example: the following designer treated the act of selling ice-cream as a public performance for the customer and acted it out

* Classic Brainstorming has been shown to lead to:

less diverse ideas
less original ideas
a lower quantity of ideas
… compared to letting people ideate alone and pool their ideas later.

* BAD: “What new features can we put in our camera?”

- Listing features does not consider the whole product
- Question treats camera as a fixed concept that we just add things to
- Answers must fit current concept of a camera
- Leads to incremental improvements (which can still be innovative at times)

* GOOD: “Make a better device that allows people to capture and share memories!”

- First-principle question about what a camera is used for
- Lets you think of things that have the quality of a camera, but don’t have to be a camera
- Not forced into add-on thinking, but still allowed!

* Safe bets are by definition not innovative

* communication is important!

“Teams with higher average I.Q.s didn’t score much higher on our collective intelligence tasks than did teams with lower average I.Q.s. Nor did teams with more extroverted people, or teams whose members reported feeling more motivated to contribute to their group’s success. Instead, the smartest teams were distinguished by three characteristics.”

1. “First, their members contributed more equally to the team’s discussions, rather than letting one or two people dominate the group.”

2. “Second, their members scored higher on a test called “Reading the Mind in the Eyes,” which measures how well people can read complex emotional states from images of faces with only the eyes visible.”

3. “Finally, teams with more women outperformed teams with more men. [...] This last effect, however, was partly explained by the fact that women, on average, were better at “mindreading” than men.”

4. “[The most important factors were the same online:] members who communicated a lot, participated equally and possessed good emotion-reading skills.”

I LOVE PyTorch for experimenting with dynamic deep neural nets (DNNs) -- that is, DNNs that can have different graphs for different input samples. I find it much, MUCH easier to create and tinker with dynamic DNNs using PyTorch than, say, TensorFlow Fold. PyTorch is great for R&D experimentation.
For example, here's how easy it is to construct a fully-connected neural net with a dynamically random number of recurrent hidden layers in PyTorch. Yes, it's a silly example, but it shows how easy it is to construct dynamic DNNs with PyTorch:
import random
import torch

def forward(self, x, max_recurrences=3):
hidden_relu = self.input_layer(x).clamp(min=0)
for r in range(random.randint(0, max_recurrences)):
hidden_relu = self.hidden_layer(hidden_relu).clamp(min=0)
y_pred = self.output_layer(hidden_relu)
return y_pred
It would be a hassle to do something like this with other frameworks like TensorFlow or Theano, which require you to specify the computational graph (including conditionals, if any) before you can run the graph.
PyTorch's define-the-graph-by-running-it approach is sooo nice for quick-n'-dirty experimentation with dynamic graphs.
You can even create and tinker with dynamic graphs interactively on a Python REPL :-)

I love seeing this, and not just because I love PyTorch[1].
It's also because I believe it's in everyone's best interest to have more than one widely used framework controlled by a single company (TensorFlow).
Also, I think fast.ai's approach to teaching deep learning is the right one for the vast majority of developers: start with practical, immediately useful know-how instead of theoretical underpinnings. People who want to delve deeper, say, so they can develop innovative architectures, can always do so at their own pace after taking fast.ai's course. There are a ton of other online resources for learning subjects like linear algebra, multivariate calculus, statistics, probabilistic graphical models, etc.
[1] Here's why I love PyTorch: https://news.ycombinator.com/item?id=14947076

For Basecamp 3, we’ve replaced Objective-C with Swift, UIWebView with WKWebView and added Turbolinks, with even more native code, and a deeper integration between native and web.

For us, it means using Xcode + Swift, and conforming to all the platforms conventions regarding navigation/presentation. The building blocks of our app are composed of UINavigationController, UITabViewController, UISplitViewController, UIViewController, etc. Within those containers, we have many screens where the content is built using UITableView or UICollectionView, we have even more where that role is filled by a WKWebView.

he primary code here is a local JavaScript file (written in TypeScript) embedded in the app and injected into the web view using WKUserScript. This provides native code an API for communicating with the web view without needing to directly query the DOM or do complex JS. Using a WKScriptMessageHandler, we can respond to messages sent from the web view through the bridge.

buy a Wizard X220 off banggood.com.
It's the best value for money starter racing quad you can get. I bought it for my first drone and it's just as capable as anything you can build for twice the money.
reply

Zahreddine 26 minutes ago [-]

Start off with the $15 cheapies like the E10 and solder a small TX03 camera onto it followed by Lizard95 and similar sized drones and then onto larger 180-250 size drones like the Wizard x220s.
For the goggles I'd recommend the Eachine VRD2 if you're cheap or Aomway Commander if you want low profiles.
All can be found on banggood.

"Maybe the good life is not about trying to achieve some sort of illusory balance. Instead, maybe it’s about pursuing your interests fully, but with enough internal self-awareness to regularly evaluate what you’re not pursuing as a result — and make changes if necessary. Living in this manner..."

- I suspect you could fit this into a pair of dedicated server s from somewhere like OVH or Hetzner for <$150/month (two servers to provision for peak load, which I'm assuming is ~3x as high as the troughs).

- This is some budget thinking, but 20 $5 instances, 10 from Vultr and 10 from Linode in 4 different locations and 2 load balancing servers for tops $30 with DDOS protection etc. to send the requests to proper servers would easily handle this and scale without the problem. Would that work? We would be left with $130 easy to scale, huge bandwidth and computing power network.

- Lambda itself is already ~300% more expensive than EC2, but in comparison API Gateway is indeed much much more than Lambda for processing the requests.

- I'm a huge fan of Lambda, but these prices really need to go down. If anyone thinks API Gateway is cheap, just do the math, this is a trivial amount of traffic for even the smallest of EC2 instances.
Head over to http://serverlesscalc.com/ and enable the "HTTP Requests" radio.

Let’s structure the optimizations I told you about.
A read goroutine with a buffer inside is expensive. Solution: netpoll (epoll, kqueue); reuse the buffers.
A write goroutine with a buffer inside is expensive. Solution: start the goroutine when necessary; reuse the buffers.
With a storm of connections, netpoll won’t work. Solution: reuse the goroutines with the limit on their number.
net/http is not the fastest way to handle Upgrade to WebSocket. Solution: use the zero-copy upgrade on bare TCP connection.
That is what the server code could look like:

Automate as much as possible. Payments ? Slap a stripe checkout form (unless you happen to be in a country where Stripe is still not supported) or Paypal for others.
Onboarding: Make it as easy and smooth as possible for clients to get started after signinup. Show them exactly where and how to start.
Documentation & FAQ: Create tons of it. If a client has a question, thy should be able to resolve it through your documentation for the most part. Don't let little simple questions to come to you EVERY time.
Setup a Support Ticket system and only answer via emails/support ticket for questions that cannot be resolved via your documentation. If a client is not aware of documentation, point them to it before answering the same question again and again.
Get a decent smartphone and answer the tickets/email through that. You could even do it sitting at your desk or during lunch break
If you absolutely need to schedule phone calls, schedule them during lunch break and find a relatively quiet place where you can talk. If not quiet enough, tell the client that you are travelling and they may hear background noise. As long as it is not a screeching train, clients won't mind specially if you already told them.
Hustle. Do whatever it takes to get the first few clients except illegal activity of course. You may have to cross a few lines at work (lying about lunch plans etc) but I personally think those are reasonable to do.

I also like people who get things done. If you’ve been working on your startup for two years and have nothing to show, that’s a pretty bad sign. I’ve discovered that most people are really good at finding obstacles. I don’t fund these people.

>Paul : The biggest one is made-up ideas. The best startups come from personal experience. It was something you or someone you know needed. Occasionally, I’ll ask a company, “Why do you think is a good idea?” And they’ll say, “Oh, I read an article in TechCrunch.” You have to understand it at a deep level. It can’t just be something you read.

Hint to the uninformed: don't look up "bitmap" and wonder why anyone would index them. Look up "bitmap index" instead. This will save you many clicks in the github project as well as in your favorite search engine. It's about databases, not pixels.
reply

Have used several browser fingerprinting services and have tried a few of the techniques myself, they're incredibly useful for fraud prevention when said fingerprint is reported against a central database alongside with the fraud that happened to _you_. The next time said fingerprint shows up at an eCommerce site, they'll be blocked off from purchasing or at least flagged for additional verification.
They're also just useful for super targeted ads.
shrug

There are a whole BUNCH of other ways available. In practice, no single thing is even close to 100% accurate, but once you have enough distinct indicators you can fingerprint to a pretty high level of accuracy (for many advertisers 80% accuracy is enough, and it's probably not worth spending lots of effort to go above 90%). Clock skew, for example, is slightly different on each device, but on a given device doesn't change that quickly. Mouse/finger movement patterns, TLS negotiation timings, etc, etc. There are even technologies able to track users across different devices, but it's been too long since I worked in this area to be able to speak confidently about the methods used to implement that.

Our process? Simple. We focused on three key things:
Do we trust them?
Dan and Rich have a sterling reputation in the design community, and we have tons of mutual friends. We knew that if they made a statement about the business, we could rely on it.
Are the numbers roughly right?
Instead of spending months digging into accounting minutiae, we focused on the macro picture. We looked at bank statements and credit card transactions to quickly verify that the business was doing roughly the revenue and profit stated in their financials. It was, even if it there were a couple inaccuracies here and there. The important thing was that the business was performing roughly as they said it was.
Are there any big risks?
Had they signed any crazy contracts? Did they owe anybody money? Had anyone incubated an illegal cock-fighting ring within the company? (No. No. And no.)
Can we explain the business and investment case on a napkin?
Is this a no brainer? Can we see our money back in a reasonable amount of time? Is this a simple business? Can we grow it? The answer to all of the above was a resounding yes.

Advice from my physics professor: make a detailed plan and then discard the plan and do what you feel.
This doesn't mean the plan was unnecessary...rather the plan carves out the neural pathways in your mind. The feeling part is important too since if I am so rigid then I am going to be crushed by the randomness of life.

NaCl (pronounced "salt") is a new easy-to-use high-speed software library for network communication, encryption, decryption, signatures, etc. NaCl's goal is to provide all of the core operations needed to build higher-level cryptographic tools.
Of course, other libraries already exist for these core operations. NaCl advances the state of the art by improving security, by improving usability, and by improving speed.

Points to consider:
- Influencers are key in social networks. They dont necessarily have to be famous or have a huge following. Some people are natural social butterflies. Leverage them.
- Having a marketing plan is more important than having a website. It is what you will execute over time in order to drive traffic. A plan does not need to be overly complex. It maybe simple and updated as progress is made.
- The initial rush will go quickly. Leaving you with a rather monotonous amount amount of work. Its boring. Dont chase the high. Learn to plow through the lows.
Best of luck to this team. Seems promising.
reply

What's been most crucial in helping you to succeed?
For me, SEO. I'll admit SEO won't apply for all types of companies, but it's probably responsible for most startups' successes. Unless you have no competitors, or you spread exclusively through some other channel like word-of-mouth or the App Store, then SEO is your main way of being discovered.
A litmus test is to ask yourself if you have more than 2 competitors. If you do, then it's a pretty good sign you should be focusing on SEO, as some absurdly high percentage of people go with the first result on Google by default. This doesn't just mean optimizing your website for search engines. It means gaining publicity so that Google recognizes that you should have the most mind-share and puts you at the top of results.
What's your advice for hackers setting out to be their own boss?
The most important thing for Instapainting was just doing it, and in the fastest and most testable way possible. And, as time and sales progressed, a big help was being able to engineer and automate the systems so that I had more free time to dedicate to new features and new sales strategies.
My advice to others is: Your idea doesn't have to have hundreds of thousands or millions in funding to be realized. If it does, then it's probably the wrong idea to be pursuing if you don't already have that kind of money. Your idea doesn't even have to take months or years to implement. It can be as straightforward as some simple proposition attached to a payment form. If you don't have a simple proposition to make, go seek out a non-technical revenue-generating business and help them out with their tech strategy.

I think it took about 5-6 months for me to realize that the business was primarily sustained from SEO traffic. At that point I started to focus heavily on SEO, and I the reaped the full benefits of that approach in my second year of business when I climbed to #1 spots for the top search terms. I didn't have much experience in SEO beforehand, but I leveraged my experience on Hacker News to push out content marketing pieces that were crucial to SEO. For example:

For example:
I built a robot in 2 weeks that could autonomously replicate artist paintings in black and white and, later, in color.
I launched the very first free-to-use online demo of the algorithm in A Neural Algorithm of Artistic Style, I believe 3-4 days after the paper was released.
I released an article detailing some of the things I saw when touring artists and art factories in China, which was read by Ev Williams, re-published on Backchannel, and totaled over 71k views.
When the 2048 game came out, I quickly hacked up a 2 player version and placed it under the Instapainting.com domain for SEO purposes.
Being lazy, I milked the robot I'd made earlier and hooked it up to Twitch.tv, where people could control it to collaboratively paint.

".. the measure of a healthy organization is probably the degree to which negative thoughts are allowed. In places where great work is being done, the attitude always seems to be critical and sarcastic, not "positive" and "supportive". The people I know who do great work think that they suck, but that everyone else sucks even more." ­­-- Paul Graham

I've found Linguee very useful for English -> French translation.
I think it draws heavily from the huge corpus of professionally translated EU regulations and documents.
reply

bbotond 1 hour ago [-]

Agreed, it has been extremely useful to me too for translating various Hungarian technical terms into English. Naming classes and database tables is much easier this way because most often the right term cannot be found in even the most detailed technical dictionaries but Linguee somehow just knows it. And it also shows the context so you can be very confident in your choice.

1. Gather beta tester feedback to confirm that site works.
2. Ask beta testers if they would like to be quoted in press release
3. Ask beta testers if they would announce the site to their network
4. Set up social media accounts related to site.
5. Gather media email addresses (reviewers, bloggers, news sites, etc..)
6. Email media a press release notifying the app has launched
(If a tree falls in the forest and nobody is there to hear it, does it make a sound?)
reply

This is probably the soundest advice and agree wholeheartedly; the market appears to be saturated with inexperienced developers. This means, at somepoint (probably about now actually) there will be a very real need for good/great rails/ruby devs to come in and sort out all this mess. Not everyone will be able to dump and rewrite their projects; some will need tidying and new features added. You could make a killing there is your disciplined (think of Y2K and all the old experienced cobol devs coming out the framework to fix stuff)

The closest I can get to a single "secret" is aggressively delegating. What I mean by this is delegating before you feel comfortable delegating. The only way I know of to get everything done that I want to get done is to set the vision for something, do some initial implementation work, and find people who share the vision to help as early as possible. The primary reason I end up working on so many things is that things are way more connected than you might expect, and the full picture of something like Ember involves both day-to-day work on Ember and advocacy around a whole host of related technologies. I'm very grateful for the number of groups that have welcomed my participation.
I got involved in Rust largely because it was the shortest path to a low-overhead, non-crashy agent for Skylight, even counting the work we had to do to keep up with ongoing development over the past year. When getting involved in a technology so early, I tend to get really invested, and try to find holes that I know how to fill and fill them. That's what happened with Cargo and a whole bunch of other areas in Rust.

The award winning SimpleLink Bluetooth® Smart SensorTag, based on TI's CC2541 Wireless MCU,is designed to shorten the design time for Bluetooth app development from months to hours. With a SensorTag App and no required hardware or software expertise, the kit removes the barriers to entry for smartphone app developers who want to take advantage of the growing number of Bluetooth Smart-enabled smartphones and tablets. The over-the-air download feature provides the ability to update the SensorTag firmware from a central device like a smartphone, tablet or PC. This simplifies the upgrade process and enables customers to develop new innovative features to existing Bluetooth Smart equipment to satisfy consumers' endless needs.

One of the most widely recognized predictors of fraud is the number of digits in an email address. The more numbers, the more likely that it’s fraud. Why? Because fraudsters are boring (and lazy). They use computer programs to sequentially generate email addresses so they don’t have to think of new ones. Emails such as “foo1234@test.com” or “foo1234568@testing.com” are highly suspicious. However, detecting fraud using email address alone can be really difficult. The only way to really get good at detecting fraud is to look at hundreds of signals, sometimes in the thousands (that’s where machine learning can help).

There's a million apps out there and media outlets are not going to talk about all of them, so the way we got that press was by making writing an article about us more valuable to them: we gave them something to give their readers. This was a $0.99 app (these were the days before it was clear that charging money up front for apps is not a viable strategy). We scheduled a weekend giveaway about a week out, emailed media about it, and they got to offer their readers more than just pointing out an app they might like, they got to give them a deal on it.
So, in my limited experience, a good way to get traction is through some combination the media (they have the eyeballs) and a deal (people love deals). And the best way to get the media to talk about you is to make talking about you more valuable to them.
reply

Alex-Galapagos 23 hours ago | link

bww, how did you get there initially? What app was it?
reply

daiidgo 1 hour ago | link

Several of the comments suggest a social leader board; I think that's a great idea. If you don't want to support Game Center on iOS, maybe a Facebook leader board. You could also set up your score board using Amazon's simpleDB. They support Facebook, Google, and Amazon logins. There's a basic article on that here: http://aws.amazon.com/articles/SDKs/iOS/8829919029640036 Amazon's dynamoDB does more than that, but I can't seem to find the article on high score integration through dynamoDB. Hope it helps, and good luck!

Pinterest is social bookmarking and is (obviously) incredibly popular. Delicious pushed "tags" as its killer feature. But if it had dumped putting tags front and center, and instead focused on beautiful photos of the items bookmarked, maybe it would have taken off more.

Exposing yourself to the direct, harsh feedback of the market is key. I've noticed that bad founders will do just about anything to avoid this. Instead of selling, which is hard, they spend their time going to conferences and meetups, trying to do PR, talking to biz dev people about partnerships, etc. It all sounds like work, but mainly serves to insulate them from the harsh reality that nobody wants their product.

As if often the case with stackoverflow answers, all of them are wrong in different ways. You should only kill -9 when every other signal the program is likely to respond to has not worked. kill -9 is likely to leave program in a state that requires manual intervention, especially if that program is a database.
If you're a developer, before you kill -9 a program send SIGTERM (ie kill without args or kill -15). If the program does not respond, run gdb -p <pid> and then "thread apply all bt" before killing it. At the very least, you should get a good idea of why it was not responding to other signals.

They should really list headphones by models instead of brands. Pretty much every brand there has both entry level headphones and top of the line headphones.
Still to this day, I recommend Sennheiser HD 25-II's. These things are indestructible. Plus they sound pretty good as well. When you watch any sporting event on TV or any big DJ, the majority of the time they will be using these bad boys.
I've had mine for well over 4 years now, not really looked after them very well, but they are still going strong. Every part is replaceable too.
Best of all, they are still cheaper than a pair of Beats by Dre.

As an ad company, my last company had a ridiculous fanout of metrics for every request. Every ad serve API request (of which we got thousands per second) would fan out to over 150 metrics EACH. So for 1000 requests per second we'd have to modify 150,000 metrics. Raw SQL updates of course fall down with this (even if we tone back their durability). Instead, we opted for accumulated for 10 to 60 seconds in bloomd and hlld and statsite, then aggregating and doing a single bulk SQL update. Worked incredibly well.
We used it in combination with bloomd: https://github.com/armon/bloomd Bloomd is another super high performance data structure server, but this time for bloom filters.
You can read the READMEs to learn why they're better for their specific tasks. Both have been running in production for 2+ years. If you're not going to be using the data structures that much then Redis is a good choice. We personally used these servers alongside Redis for k/v.

In 2011, the organizational psychologist Matthew Davis reviewed more than a hundred studies about office environments. He found that, though open offices often fostered a symbolic sense of organizational mission, making employees feel like part of a more laid-back, innovative enterprise, they were damaging to the workers’ attention spans, productivity, creative thinking, and satisfaction. Compared with standard offices, employees experienced more uncontrolled interactions, higher levels of stress, and lower levels of concentration and motivation. When David Craig surveyed some thirty-eight thousand workers, he found that interruptions by colleagues were detrimental to productivity, and that the more senior the employee, the worse she fared.