kanevski

We still have some fit & finish things to improve upon, but it should be quite functional.

We are new to this, so don't hesitate to reach out with suggestions, we're still learning.

A pen test costs half the monthly salary of an engineer, so it’s an easy investment to rationalize on a quarterly basis.

Most people use Alfred in limited ways, and we tried to cover those hot paths. However, we are still working on covering the long tail of that feature set.

We definitely support building custom commands, but they are super limited today. We have to build the sophisticated commands ourselves. However, we will be opening up our toolkit, so if you have ideas on dev ex of building a command or how you would want to rig them up, feel free to reach out.

Feel free to shoot me an email (ivan@) if you want to brainstorm some commands and how they can work.

Today, we write the integrations ourselves.

We will eventually open up our APIs so people can build their own integrations to extend Slapdash. If you have ideas or thoughts on what would be a good dev experience, feel free to reach out.

I have my command set up to open this URL:

vscode://file/<ABSOLUTE_PATH_TO_YOUR_DIR>

The "file" above is important, first time I set it up I missed it and it didn't work correctly.

Certain products have a desktop app counterpart. For example, Notion, Trello, Figma, etc.

Slapdash is aware of those applications and when possible will opt to open things inside the desktop app vs a browser tab.

There are details throughout this post, but I will summarize our high-level approach.

* When we request permissions, we request a minimal set. For example, you can connect Drive with just meta-data access and our access will be scoped accordingly.

* Everything is encrypted. Importantly, it's also encrypted in the data store itself. If our DB was compromised, the entries would not be readable (ECIES, Secp256k1, AES256+CTR). Only exception is the reverse index.

* The operations that involve encryption / decryption of encrypted content live in an isolated layer.

* Token storage follows similar methodology

* We get a pentest and security reviews quarterly

* We also have strict company policies around IT and infrastructure access

That said, we aren't ever at a terminal point in our security story.

Our experience has been that security conscious companies simply turn off ability to connect third party applications.

That said, it's definitely confusing in its current form, so thanks for highlighting it.

The apps you suggested are definitely within reach (except for maybe Signal). We don't integrate any CMS's yet, but I think it would be quite helpful, especially for folks who tend to interface with them a lot.

If you think of Slapdash as sort of an OS, today Spaces are kind of like folders. You can build them manually, or with rules (a saved query). It's a means of organization -- which is complimentary to the problem of information retrieval. It also lets you add arbitrary things to the Slapdash graph (any URL) - which helps with making Slapdash more comprehensive outside of the apps we have coverage for.

You will certainly be able to extend existent commands. We are in the process of exposing our command-building primitives so custom commands can be as sophisticated as the ones we write.

We will improve coverage with the MSFT stack, and the use-cases you mention (launch a zoom call with a person, schedule a meeting with a person) are actually right around the corner.