qhoxie

14 ms·

91.
by qhoxie 13y ago
If I understand what you're suggesting correctly, we already do this. Any analytics we expose in the dashboard are also being leveraged internally as signals for search relevance. Effectively, any search interaction can be used to im
92.
by qhoxie 13y ago
Glad to hear it. As Luke noted, we've been using d3 more and more, particularly for this release. We've all been really please with its flexibility.
93.
Swiftype Adds Live Analytics And Other Features For Marketers(techcrunch.com)
19 points by qhoxie 13y ago|6 comments
94.
by qhoxie 13y ago
As we gradually migrate data from MongoDB to MySQL, this code has been hugely helpful. It is making the transition as smooth and efficient as possible. I hope others can get some value out of the gem as well.
95.
Swiftype is a Static Showdown sponsor(swiftype.com)
3 points by qhoxie 13y ago|1 comments
96.
Swiftype is hiring software engineers(swiftype.com)
1 points by qhoxie 13y ago
97.
Swiftype is hiring software engineers(swiftype.com)
1 points by qhoxie 13y ago
98.
Swiftype is hiring software engineers(swiftype.com)
1 points by qhoxie 13y ago
99.
Swiftype is hiring software engineers(swiftype.com)
1 points by qhoxie 13y ago
100.
by qhoxie 13y ago
This is definitely true. We frequently talk about the real challenge in all of this being exposing the power that is under the hood while still keeping people productive and not letting them shoot themselves in the foot (while changing res
101.
Swiftype is hiring for engineering, sales, and support(swiftype.com)
1 points by qhoxie 13y ago
102.
Swiftype is hiring engineers to help fix site search
1 points by qhoxie 13y ago
103.
by qhoxie 13y ago
Both – interaction with the search results and general site usage data are important factors.
104.
by qhoxie 13y ago
There are many factors that make high quality search difficult, but as an example, take relevance that evolves over time. Static text-based rankings are a fine start, but improving search relevance continuously based on usage takes a lot o
105.
Site Search Should Be Sexy: How Swiftype Raised $1.7M(forbes.com)
67 points by qhoxie 13y ago|17 comments
106.
by qhoxie 13y ago
We still allow this. You are just more limited in how frequently you can do an on-demand crawl with the free plan versus a paid plan. You can also ping our API to update a specific URL immediately, which is really helpful is cases like thi
107.
Marketing with Asana: The Tools We Use(blog.asana.com)
12 points by qhoxie 13y ago|1 comments
108.
by qhoxie 13y ago
I think that "double the price per bandwidth" figure is way off – where did you get that? imgix pricing looks to be about a 30% premium over the US CloudFront pricing, and much less than that internationally (imgix doesn't appear to distin
109.
by qhoxie 13y ago
I don't think littleutils does much more than optimize images, which is pretty different from: http://www.imgix.com/docs/urlapi Resizing or optimizing images, in isolation, is not a hard problem. I've solved subsets of this problem a han
110.
by qhoxie 14y ago
Mike McCandless gives a good overview here: http://blog.mikemccandless.com/2012/07/lucene-400-alpha-at-l... He has some other posts on there that do a deeper dive as well.
111.
by qhoxie 14y ago
I think Cloud Code is a good example of why this is not the case. The more flexibility and customization they allow in the platform, the fewer long tail features they need to implement because people will be able to do it themselves.
112.
Swiftype (YC W12) is hiring full-stack engineers to build better search software
1 points by qhoxie 14y ago
113.
Swiftype (YC W12) is hiring full-stack engineers to build better search software
1 points by qhoxie 14y ago
114.
by qhoxie 14y ago
http://downscout.com/twitter.com if anyone wants to track it.
115.
by qhoxie 14y ago
Definitely. Swiftype currently supports geo-based searching/filtering, but it appears we haven't pushed out the docs for it yet. They will be up soon!
116.
by qhoxie 14y ago
Had a couple of hiccups due to load spikes in engine creation. Working on a fix to prevent this in the future.
117.
by qhoxie 14y ago
We do support multiple domains and even diverse types of sources (crawl and API in a single engine). Unfortunately we don't have it exposed in the interface just yet! We will get that turned on in the next day or so.
118.
by qhoxie 14y ago
Spot on. This is one of the real advantages to leverage in a site search system. We have only scratched the surface of what's possible, but there is a lot more to this coming soon. Also, not sure if you caught this on the site yet, but we
119.
by qhoxie 14y ago
Both of those are great suggestions. We'll likely make those changes soon. Thanks for the thoughts!
120.
by qhoxie 14y ago
Yes and yes. We do a fair amount of post-processing on the pages to handle things like boilerplate text pruning. Hopefully, it should catch what you mentioned. That said, we have bulk modification tools in the works.

More ›