Jump to content


Level 1
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About markav

Profile Information

  • Subscription

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I hope EN does something like what Google does and assigns a specific unique password to an app, so even if someone got it, it wouldn't work on any other machine. Leave the 2FA to the PC and web browser. Actually using Yubikey for 2FA on the Android is a reality for LastPass now and it's pretty elegant. I just bought a Yubikey NEO which supports NFC so all that's necessary is to swipe the Yubikey across the back of the phone which opens the LastPass login screen. Enter username/password and you're in. Granted, this only works for LastPass now and only Android phones that support NFC, but it's a pretty cool solution. One other thing that LastPass has implemented recently is a "poor man's Yubikey" which uses your own flashdrive as a hardware key. Install a LastPass tool on the flashdrive called Sesame and you now have hardware 2FA. Here's an article on lifehacker that discusses the LastPass 2FA.
  2. YubiKey. Google Authenticator. Something other than username/password. Personally, I use YubiKey with LastPass on both Windows and my Android phone. It works and would be an excellent solution to this issue with EN. Google Authenticator would be nice, but falls apart if I'm running it on my Android along with EN. Assuming my EN user/password has been compromised, all one would have to do is run the Android Google Authenticator app, grab the code, and plug it into the Android EN login along with my EN user/password. Nothing gained here at all (please correct me if I'm missing something on this.)
  3. I create a lot of notes that use the same set of tags and trying to do this by memory inevitably leads to accidentally assigning the wrong tags or leaving some tags out. I've grouped my tag list using parent-tag/sub-tags, but this doesn't always fit the actual group of tags I want to assign to a note. I can press Ctrl-Alt-T to mass assign tags but this is even worse because the parent-tag/sub-tag hierarchy gets flattened making the dialog pretty much useless. Also, I don't want to create a new note from a template that already has the tags in place because most of the notes I'm trying to tag are being clipped from the web so tag assignment has to be done after the fact. What I would like to do is create a "tab template" that allows me to save a group of tags using an alias that will assign those tags to a note or group of notes in one fell swoop... a super-tag if you will :-). The next best thing would be to have an option to select a parent-tag from the tab list and have EN assign that tag and all it's sub-tags to the note. Not quite as elegant as what I really want but it would do. Thoughts please. TIA Mark
  4. Sorry if I'm posting on a topic that's already been covered. Being new to Evernote and not fluent in the terminology, I scoured around trying to find an answer and finally said ***** it... I'm just going post a new topic and suck it up if I get yelled at. 8) I've seen several posts that discuss the limitations of sub-tags when you're trying to use the same name in a different parent hierarchy. Evernote errs out indicating that this is a duplicate tag. Windows ....Appnotes Mac ....Appnotes Which generates a duplicate tag error. I could do this, but it's contrary to the way I want to organize my data: Appnotes ....Windows ....Mac I could also do something like this, but it would start getting ugly really fast with all kinds of weird tag names: Windows ....Appnotes_Win Mac ....Appnotes_Mac I would like to suggest a solution to this problem.... Give the user the option to make a new sub-tag unique in the hierarchy (or not.) In other words, internally, Evernote could represent a unique hierarchy by concatenating the nested tag names something like this: Given: Parent1 ....SubTagLevel1 ........SubTagLevel2 Parent2 ....SubTagLevel1 ........SubTagLevel2 Evernote could create a unique ID internally (the user doesn't have to see the implementation) by combining the branch tag-names resulting in something like this: The first branch would be assigned the ID: Parent1-SubTagLevel1-SubTagLevel2 And the second branch would be assigned the ID: Parent2-SubTagLevel1-SubTagLevel2 In essence, these ID's could be thought of as the tag names for each branch, and since those tag names are unique there is no issue with duplicates. Problem solved. This should be a global option to accommodate users who could care less and want to continue to use the current data model, as well as an option on a tag-by-tag basis. Hope this makes some sense. TIA Mark
  • Create New...