Server-side analytics, upsell tool (script interactions on your website), and bot protection all rolled into one.
We're happy to answer questions (see profile) and we'd love to get insight into your decision process.
59 karma · joined December 13, 2018
Server-side analytics, upsell tool (script interactions on your website), and bot protection all rolled into one.
We're happy to answer questions (see profile) and we'd love to get insight into your decision process.
Shameless self-plug: if server-side analytics is too complicated for you, consider using the tool that we just launched to help with that (other functionality gets included as well): https://www.nettoolkit.com/gatekeeper/about
https://www.nettoolkit.com/geo/the-basics-of-geocoding https://www.nettoolkit.com/geo/adventures-in-address-parsing
It turns out that geocoding has been a much bigger project than we anticipated, but we offer the service very inexpensively. Let me know if you have any questions.
I agree that we have a marketing problem (letting people know about our services). However, even if we to solve that, I want to understand what it would take for someone who is aware of our services to actually convert. Hence, I appreciate your answer and hope others chime in as well.
Thanks again.
Mapbox charges ~$4 for a thousand map views, while we charge $0.10 for a thousand map views (less than a tenth of Mapbox's price). How do we convince you to switch to our services? https://www.nettoolkit.com/geo/about
Maybe -- just maybe -- people understand your point but are bringing up something else that they think is relevant.
> Yet you still doesn't give a straight answer how it is fair that Saleforce pays less tax than Square. I don't blame you. Nobody has answered that question.
I don't think people are saying that the tax situation is fair. Rather, I believe the claim is that Square's CEO is likely not exclusively focused on the unfairness of the situation when he is complaining about the tax situation, but complains about tax in general. I think abalone wouldn't be giving Jack grief (or at least much less), if Jack did not lobby for that tax earlier.
To spell this out further with an extreme example, imagine a recent college grad who's super smart and has the attention of the world. He says "It's crazy that recent college grads are saddled with student loans. Instead, we should soak the rich and heavily tax everyone making $1 million or more." People agree, and the tax is instituted. A few years pass, and after his college debt is forgiven, this recent college grad is doing really well and finds himself making $2 million a year. At this point, he says "It's crazy that higher income workers pay such a high percentage of their income relative to others -- everyone should pay the same percentage." To which people respond "but then we can't forgive student debt with the reduced tax revenue," and yet the recent college grad persists. Do you see the problem with the behavior of the recent college grad?
It might be that the grad sincerely held his conflicting positions when he proclaimed them, but it's also possible that he was always advocating for what was advantageous to himself. Given the short time period (and that the grad makes no offer of accepting his college debt back), people generally guess that he using a sense of fairness to advance his own interests.
Again, I'm not very familiar with the situation, but it seems that the current tax is not a good one, and the CEO of a payments company could have foreseen that it would not be good for his company once his sales got rolling. Why didn't Jack advocate for some other tax scheme earlier, such as one that is based on net income?
abalone's comment that "they've changed their tune. ... and they still shouldn't pay taxes" could simply be hyperbolic, depending on how charitable people are in their interpretation (e.g. "shouldn't pay [the full amount of] taxes").
I think the main thrust of abalone's comment stands: the CEO of Square pushed for a tax that many think is absurd (e.g. darawk), and now that Square has grown and the tax is unfavorable for them, Square wants to change the tax that it seems to have lobbied for (and presumably thought was fair back then) -- that makes Square seem opportunistic [and not having the community's best interest in mind when the CEO lobbied for the tax]. At least, I think that is abalone's implication.
> I think trying to come up with challenges to beat botters would be prohibitively time consuming.
I agree that is challenging, and I think this question will need to be settled empirically. Sub-questions include:
a) What is the threshold for bot operators to engineer custom CAPTCHA solutions? (e.g. for a large website, how much can a bot network make?)
b) Even if it were not possible to conclusively beat the bots, what is the threshold at which bot operators decide that they would rather make their money off of other sites instead?
For me, this is an interesting and open question. I've taken the view that as long as it's easier to come up with new types of challenges than it is to create an automated means to solve those challenges, CAPTCHAs offer some protection. If you're ok with requiring JavaScript, mouse input, and images (e.g. you don't require your site to be accessible by sight-impaired users who cannot use a mouse), I think people can come up with varied enough challenges to present a problem to bots. How long will that be the case? I don't know.
You can try out demos at https://www.nettoolkit.com/shibboleth/demo
While not open-source, the service is very affordable ($10 for 100,000 CAPTCHAs), and clients get to review user submissions to see if the CAPTCHAs are reasonable or not.
Would love to get your feedback on the service.
Only if the newspapers themselves allowed it. Newspapers could suppress public criticism that came their way through this channel if they so chose.
Shameless plug: we at NetToolKit recently launched a very affordable geocoder that includes rooftop-level geocoding for most of the US (using OpenAddresses data). You can test out the accuracy here: https://www.nettoolkit.com/geo/demo
We'd be thrilled if you would consider using our service (first 1,000 requests per day can be free).
To answer your question, we currently have multiple (redundant) servers, but not multiple data centers. If we got a strong enough commitment (contract), we would be happy to operate in multiple data centers.
We are launching an alternative CAPTCHA service and we would love your feedback. We've developed some unconventional puzzles to entertain your users, and you can also review your users' solutions to see if the challenges are too easy or too hard.
We are particularly interested in feedback in two areas: 1) if your team would consider using our services, please let us know what needs to change in order for you to actually make the switch and 2) if you have ideas on how to develop an effective CAPTCHA that is accessible to the sight-impaired (while still being generally usable), we would really like to know.
Thanks so much for stopping by!
If any of your small business clients might be interested in our new CAPTCHA service that should launch late next month, please let me know (see profile for contact information). Our pricing is projected to be $10 for 100,000 requests.
After someone clicks the "delete selected shape" button, you should probably resume the click-shape mode (with the crosshair cursor). It took we a while to figure out how to start clicking the shape and that I need to refresh the page if I want to restart.
Beyond that, I only got it to give me results when I specified a very small area; my earlier attempts encountered a "too big" error. I would guess that you are running into performance issues for larger areas, but limiting the area too much makes the demo less impressive.
You might get some more feedback if you don't require registration to test out your platform (I personally am not thrilled about creating yet another account just to try something out). A compromise would be to allow users to enter the query, and only see say, the top three results. In order to see the rest, users could be required to register. That way, people can test out the flow of the service before deciding whether to give you their email addresses.
I personally think your previous language of "bait" and such was cute. You have a pond theme, and you could commit to it further by having graphics like "fishing expedition" or a net to represent the catch. I'm not a marketer, so it's quite possible that manigandham is right. Nevertheless, I suspect that a single data point should not be enough to change your theming either way.
Hope that helps!