325 karma · joined August 19, 2013
how is value defined in this context?
if you have the time, you should make a complimentary “solution” read me page for this post.
deletion really does seem to be an unwinnable proposition, so flooding with false data is a great approach. can this be automated?
couple thoughts:
1. is this dynamic? your first time setting up the api takes a while as it's processing everything, but what about additional emails? or is every api call that slow? i suppose if it's _not_ slow, that suggests you are caching something on your side, and I wouldn't want you to store my data like that.
2. how will you convince people to give you access to _all_ their emails? maybe it makes sense for this to be a tool people can run locally (helping with the performance issue of [1] as well) and you can charge for that somehow.
3. the api schema generation tool seems like it would be flaky.
> but you can flood them with false information and they will record it and keep it forever.
how would you do this?
Unless I misunderstood the app while playing around with it and reading every word on your product page, it is not a _ drop-in replacement_ for those tools. Albeit, I didn't try creating my own url/launchers but if anything its functionalities seem like a subset of Alfred's abilities as opposed to a replacement.
..which was one of my primary hesitations considering this tool for adoption while playing with it. I already have Alfred, this doesn't replace Alfred, and I don't want yet another launcher to keep in mind. I could just sync all apps locally (Dropbox/Google Drive) and get the majority of the value proposition of Slapdash with Alfred.
hoping your job is fill that hole for you is begging to be abused. this is how tesla and other major "be a part of something bigger!" marketing allows for them to pay little
I went down the heavy customization path, and eventually came upon the profound realization that I was going the wrong way. I ditched all the extensions and went with the simple gmail[0]. No breaking changes to extensions over time. Less CPU load. Cuts out all distractions. Simple. Fast. I'm in and I'm out.
• squashed commits
• arbitrary thresholds of session durations
are they all 100% owned by you or did you drink out of the poisoned foundation (vc)?
also how do you toss up many sass so quickly? do you just have an auth and payment module you're comfortable that you reuse for every project?
This feels like alfred without namespaces and a more cluttered UI. I don't like that there are "plugins"; alfred's workflows are way more customizable and accessible. some plugins are "pro" (paid). it feels way more "closed garden"y than alfred.
maybe because of my engineering mindedness, but I personally prefer namespaces like alfred supports. this "natural language" take was a bit confusing, specially since anything could be interpreted in multiple ways (no namespace identifiers) and multiple plugins could handle it. this requires far more mental effort to use and filter the responses than alfred, and also feels significantly laggier probably due to it doing so much simultaneously (loading icon flashes often and I'm on a mbp).
I think it could work for people that don't know that alfred exists yet want a similar tool. It certainly is pretty, and besides the laggy UX, the UI seems pretty well polished.
2. how do you come up with the startup/tool ideas?
i suppose more transparency on them getting a cut, and/or decreasing the size of the cut are plausible.
this is certainly no longer the case