Pascal Held

Hallo Corybe, you are totally right. If you connect your Evernote account to any third-party tool, you will grant access to your notes. As developers could change the code in any way, every developer could change code so that note content could be accessible to him/her. Even Evernote themself could theoretical access your notes. Nevertheless, we respect your privacy and it is totally not in our sense to access your notes without your approval, otherwise we would risk our complete business model. At Filterize, there are exactly two persons at the moment, that have access to the production code base, which includes access to the database keeping your Evernote access token. That's me and one of our developers. Both of us have no interest in your notes. Also there are laws, that we have to keep your privacy, especially here in Germany. Concluding we can say that, yes you are right, there is a potential risk, but we're doing everything to keep your privacy. If you want to be totally safe you have to keep your notes locally on your machine. Best regards, Pascal

With Filterize you can also combine multiple tables of contents into one note. So you can build a dashboard with all your todos or important notes. If you have any trouble with the setup feel free to contact us. It's a pleasure for us to help you.

I think exactly the same thing about todays AI approaches. Nevertheless, we also introduced an AI component in Filterize to automate your Evernote. But It's not that black box type of AI. We use frequent pattern mining to find plausible rules, which could be applied to your database and while you are working in Evernote Filterize checks if one of the potential rules could explain your work. If so, EvA (our name for the AI) will suggest a set of rules. You can decide which rules should become active and you are free to change them later. You can read more about the process itself in our blog.

There is a discussion about building a dashboard in Evernote here: We at Filterize like the idea of a dashboard and we build a tool to create dashboards. You can create a note with different sections, like open todos, new notes or anything else you can search. Then Filterize can create a list of notes, fitting to a given search, into these section. If you are done, it could look like this: More details, on how to create such a dashboard could be find at https://fltrz.io/xZs75N3Y2S Disclaimer: I'm the CEO of Filterize. Filterize is an online cloud service that acts like your personal Evernote assistant. Tell Filterize what to do and it starts working instantly in the background for you. It simplifies repetitive tasks, avoids errors and saves time.

I think this is a great idea! Who can move it to the integrations part? Can you do it @DTLow or is it up to @msfz751 as the thread creator?

Sharing should be possible too. All links within the dashboard are normal note links, so you can navigate. If you share the dashboard note to other users, they can click and follow the links, as long as they have access to the target notes too. I also started to create dashboards with Evernotes table of content feature, but I didn't like that if I added new notes I have to take care of the table of contents manually. Yes the Filterize table of contents are based on Evernote search queries and refreshed automatically once an hour (if you are active in Evernote, during non active times, it will skip the rewriting of the note). I use IFTTT to pull data from external sources, like a daily weather notification or interesting articles into separate notes which could be combined into the dashboard.

We at Filterize like the idea of a dashboard and we build a tool to create dashboards. You can create a note with different sections, like open todos, new notes or anything else you can search. Then Filterize can create a list of notes, fitting to a given search, into these section. If you are done, it could look like this: More details, on how to create such a dashboard could be find at https://fltrz.io/xZs75N3Y2S Disclaimer: I'm the CEO of Filterize. Filterize is an online cloud service that acts like your personal Evernote assistant. Tell Filterize what to do and it starts working instantly in the background for you. It simplifies repetitive tasks, avoids errors and saves time.

There is a dedicated content type for business cards. You can search for contentClass:evernote.contact* to find all your business cards.

Thanks @DTLow for posting this. We have a newer version of the table of contents generator. An introduction could be found here: Also we have a nice article, how to combine multiple table of contents into a nice dashboard:https://fltrz.io/kzmeOCOoKS

Hey guys, we have the solution for your problem. It is possible to create recurring reminders in every cycle you want for your Evernote, but not in Evernote. Who are we and how could we help? We are Filterize! An automation service for Evernote. And one out of our automations for Evernote is a workflow, that allows you to create recurring reminders for your notes. Have look here. You will need an Filterize account to use it, but there is a 30 day's premium trial and a free Basic account, in which you can have 3 filters. You have any questions? Feel free to contact us! With us, you can automate your Evernote in many different ways. Save time and keep your Evernote 'tidy'.

Great news, filterize is official in productive status now. Thanks to all of the testers. We found and fixed a couple of bugs. Also some new feature like complete logical expressions for the conditions are possible now. Next, we will focus on business accounts. At the moment only standard "Free", "Plus", and "Premium" accounts are handled. If you are interested in being a beta tester for your business account, please contact me. You can configure most of the available actions, e.g. specify your tag or something like this. At the moment filterize is complete event driven on note create or update events. So there is nothing like a "cron job" yet, to processes your notes every night. But such a feature is on the feature request list, and will be available at some time. I think you can setup such a process with reminder times (the final followup date), which can be set by filterize, and a saved search for "reminder tomorrow" for example.

Yes you are totally right. The user have to trust in the software as it could have bugs (which could damage the users content). That's why I'm looking for courageous beta testers ;-) (BTW: I use and test it with my live account). Also evernote recommends to start testing new addons with a test account.

Yes it would be possible to create a native app where all this filter process runs locally. So only connection from the users pc to evernote is needed. But there are some drawbacks in this situation: Evernote can notify webservices, but not local applications. That means that changes are not processed immediately. But you can sync every 15 minutes, so changes will be processed after this 15 minutes. You have to run the application all the time, because the processing can only be done if the app is running. It is hard to synchronize the filters between different devises. So you have to decide which device should do the processing. If you run it in parallel on your smartphone and your pc you could get conflicts. And if you run it on one device (e.g. your pc) you could not configure filters on other devices (your smartphone) What do you mean with automatically? If you provide a machine which runs all the time, and you trust this machine that nobody else can access it (e.g. hackers via internet) then yes, it is possible. Yes in the case I would sell a native app, which no server requirement I would sell it for a one time fee. But probably with higher costs. Here some arguments why I would do it so: There are different costs for the developer: Development costs: This is payment for the time the developer needs to create a first releaseable state of the software Maintenance costs: You are interested in support, bugfixes, and maybe new features Current costs: In the case of a webservice for the server infrastructure (so you don't have to run a pc all the time which costs energy) In case of a one-time payment native app: The developer has the development costs and the maintenance costs for a certain time (e.g. I provide one year free updates) To calculate the app price you have to devide these costs by the number of potential users The number of potential users is the critical point. If you underestimate it (which yields into higher earnings) the developer is happy, earns money and is motivated to build new features and give free updates. If the numer is overestimated the developer loses money, he is frustrated and stops maintain the software as you mention in your first post in point 1 In case of a subscription modes: The developer has all kind of costs, especially the current costs require a continuous cash flow. So If you want to run the filters for 20 years, I have to provide the server for 20 years. regular cash flow is possible with different concepts: regular payment: Requires subscriptions and services that stop working if somebody does not pay. high one time costs: This is hard, because the developer has to provide the service even only one person has payed for a lifetime service. On the other hand at ony point in time every potential user has buyed the software, so no further sells are done finance the service by ads: That is hard for this kind of service. Ads could be places on the website itself, which is not used frequently if the filters are set up. Another idea would be let the webservice put ads into your evernote account, but I think user would kill me, if I add ads to there notes are create extra ad notes. What happens if the developer miscalculated the prices? If there are not enough users which are willing to pay for the service and the costs are higher than the current costs the developer could close the service after the current payment period. This is annoying, but the user payes only for the service he get. (With one time payment you will lose money if the service closes as you have payed for lifetime service) Thank you. All questions are welcome.

I thought about the questions @Panzerkampfwagen asked. And I have some answers and some points to discuss. 1. Lets Talk about security: I see the point. It's hard for users to trust third parties, espacially if the most private notes are in there evernote account. Thinks I can offer to the clients: Encrypt all connection between evernote, the user and my service, so nobody else can steal the access token, which can be used to access the users data Avoid storing personal data and account content on my server as much as possible. (currently I store only meta data about tags and notebooks and the title of the note for logging for the user, but at least I have to store the access token, which will give access to all data if lost) Give a detailed description about this on the website Promise not to abuse the users access token and the users trust Provide legal information about my person (which are available in the Legal Notice) Things somebody could request, but are still not realizable Do not store/process any user content --> No service will be available or at least every information has to be fetched from evernote every time the user interacts, which is against the evernote api usage guidelines. Also at least the access token has to be stored. Encrypt everything on the server. Yes this is possible, but to process the notes the server has to know the decrypted access token to process the notes. So the server must be able to decrypt the encrypted stuff, which means that the encryption key must be stored. And if you store the encrypted data and the key it effectively not encrypted As you mentioned, with a local client and not an implementation as webservice it would be possible to use firewalls so the user can be sure, that there is only communication between the user and evernote, and hopefully the access token is not leaked. The drawback of such a solution would be, that the user have to run a native app on its computer to process all node changes. Do you have other ideas how to handle these security issues? Why do you trust IFTTT, when they collect access token to almost every personal webservice? So if IFTTT gets hacked the intruder could access almost every service you use? (I did not ask this question, because I didn't trust IFTTT, but rather there is also a huge security issue) Native app vs. webservices Yes IFTTT provides native apps for different platforms, which has started some years after the service itself started. The main idea on the webserive is, that (similar to IFTTT) you configure your filters online and they work in the background so you don't have to think about them. If there is enough interest on the service I will whink about create also native apps, so user can change there setup offline and sync it to the server if the connection is available again. The other kind of native app would be, putting the full service into a native app. But then the user has to setup a server for his own or at least needs an application running that will do the filter process locally. To build a webservice doing this was a design decision I made. But if there is much more interest in such a local version, I will create such an application, too. About payment and monetarization Yes monetarization is a huge question. In my oppinion the interest of the developer on an app is directly correlated to its profit. So if the developer does not earn money with application he is less interested in giving support and create new version. That is why the service is not for free. (BTW I working on a limited free version) This is really a good point. I see a lot of aspects here: Native app vs webservice: From my point of view, a webservice gives you continuous service. So if its offers a one time payment you should get a lifetime service. Otherwise users upset if the service goes down. Also the service provider has continuous costs, which could be a problem if all interested user use the service, then the service provider has no cash flow. On the other side, with a regular payment the user agrees e.g. for paying one year, while the provider agrees to run the service for one year. If at any point of time the provider shuts down the service (after all paying periods) the user loses no money. So I decide for a regular payment. If I would offer a full native client, which does all the processing locally, I would also offer the one time payment. day-to-day value vs. sporadic use of the website: The question here is, where is the main value of the service. I see the website itself (or a future native app for configuration) as a required tool, but not as the main value. In my point of view the value is in the background. The service will run continuous in the background. Whenever you create a note, which will trigger a filter, this filter will process the note. So if you create notes on a daily base you get value on a daily base. I think this is similar to IFTTT. You will not use the app or the website everyday to create a new receipt, but it will proceess events on any webserive on any time, so it will provide value on a day-to-day base. This is another reason, why I offer the service with a subscription model. One time users vs. regular users: If somebody just want to organize there account on a one time base, he can purchase the cheap 1 month paket. With this he can create a lot of filters and run them on the current notes, and after this month he either finished his work, or he will continue use for new note. In this case he can start a subscription. So there is a one time option for one time usage. I hope these answers would give insight to some of my thought. I'm looking forward for further discussions on these points. BTW. is there a possibility to add a poll inside of a thread in this forum? Or do I have to start a new one?

Thank you @Panzerkampfwagen for this meaningful questions. I will work on them and give response in this thread and on the filterize website.