Jump to content

They Call Me Broose

Level 2
  • Posts

    82
  • Joined

  • Last visited

  • Days Won

    1

They Call Me Broose last won the day on August 11 2018

They Call Me Broose had the most liked content!

1 Follower

About They Call Me Broose

Recent Profile Visitors

2,670 profile views

They Call Me Broose's Achievements

45

Reputation

  1. Worse case, instead of being blocked from sign-in on the EN Legacy client, I'd like to have continued access, even if sync doesn't work. I'd maintain storage and backup of my own data. It would drastically change the way I work with EN on multiple machines, but I'd do it, because the 6.x client is still the fastest and most efficient for my workflows. I've understood for a long time that Legacy is going away, and appreciate that it's been around as long as it has, but don't lock us out of its use altogether by requiring the sign-in to open and access the content. Or do to confirm a subscription, but at least make it an option to continue using the client, even without sync.
  2. Oh. nah. Full disclosure - the quote sounded like something I said - or just thought - and about halfway through writing I realized that wasn't my quote, but I thought the response still valid. sorry dude, lol
  3. Exactly. Legacy's super fast and efficient. Good info above. I was wondering whether anyone's found anything comparable. I've seen a few posts here and there over the years as others have commented on the various major hiccups we've experienced. I made a list, but haven't explored anything else in earnest yet. It's obvious now we're approaching the cutoff. It's not a surprise, I've seen all the notifications and chose not to make the jump. My reasons were proven valid in my exploration of v10 today. They should announce a hard cutoff date, though. I'll add Notion to the list to check out. I don't want to leave EN, but v10's too big a sidestep/backstep to ignore now. I think those like myself who become involved in these impassioned discussions here are hoping that someone sees there are enough of us saying, "Woah, no, wrong!" Likely to make any difference? No. I'm not saying to take anything away from you v10ers who like it, but client/server's not that hard. I don't know how it all works, but client/server/local database/sync changes shouldn't be that complicated. I don't even need updates. Is an updated Evernote desktop client any less susceptible to compromise? Have there been any documented cases of compromise through a Legacy client? or has it all been weak credentials, social engineering, or lack of multifactor?
  4. Here are the links to working Legacy versions for anyone here who still needs to stay on Legacy for now: EN 7.14.1 for macOS -- https://cdn1.evernote.com/mac-smd/public/EvernoteLegacy_RELEASE_7.14.1_458325.zip EN 6.25.3 for Windows - https://cdn1.evernote.com/win6/public/Evernote_6.25.3.9348.exe @s2sailor - you mentioned V10 for macOS in one of your posts above, and how it's closest to Legacy. I'd like to check that out. I have a note where I captured a process for figuring out EN download URLs if one has the full version info, however, I've not been able to successfully determine a download path for a v10, let alone figure out which version of it is most stable and still closest to Legacy. Would you happen to have any info here? Right now I'm using the 7.14.1.
  5. I know you did, but I had the same thought and offered my take. I didn't realize you were having a private conversation with @jpservices My apologies.
  6. I asked questions not addressed in an auto responder disguised in the voice of a real support staff person - remember them and how friendly and helpful they were? The wording of that response effectively said, "We've responded to you re: your request for support, and this issue is closed. But write back if you need to." Who said anything about relying on support to consult on feature use case? I don't need "thrills" - I need my organization tool to work the way EN ran it for years and years and years. Resistant to change? You bet, when one of my best tools is being [bad word].
  7. Albert - awesome, you rock. 6.25.3 still works on Windows. Just downloaded and tested it on a Win11 machine that 6.25.1 failed to complete a sign-in after the sign-out test. Further, confirmed that 6.25.3 still works after a sign-out and sign-in. I enabled multi-factor authentication on my account a while back. Everyone using Evernote should. I need to find a 6.x solution for macOS... If I can't, I'll have to run a VMware Fusion VM in Unity for Evernote access in a Windows VM. I'm really going to miss the EN 6.x macOS client. It had some really cool functionality in it, like keyboard shortcuts for custom colors and a bunch of other Apple-y environment benefits.
  8. I've just spent the past hour testing V10.x on a spare Macbook. It's *****. A marked degeneration of a once great platform and client. What do I find? Aside from removed functionality I'm finding so far, poor layout structure, cludgy performance, and multiple steps now required for what used to be a toolbar item, I happen across a pretty significant data handling issue. I view a note and it updates the modified date? That's a problem. And you wonder why people hang on to legacy? This is why. Who cares what the fremiums think. I mean that with whatever respect due, but, I mean, seriously, what effect do they have on EN's success? What right do they have to expect anything other than what EN develops if they are not at least contributing by subscribing to the service? "surely objectively false?" great phrase. Impossible for any of us to prove, of course. What I was referring to with that statement was based on what I saw in the community in a previous uprising back in 2018 over some business with a forced version upgrade to a version that was crashing constantly and had become unworkable. I can be sure at this point, but it sure seemed like most of those contributing were long-active community members, and yes, I'm presuming, subscribers. Their impassioned and insightful contributions would have been a bit much for a casual user. I'm mad. I'm frustrated. I've sung EN's praises to everyone over the years. I love EN. But this development is wrong. It's not even efficient. By the way, the new features touted, like Calendar and Tasks? I'm supposed to update my "Premium" account to a "Personal" one. Huh? Keyboard shortcuts >> I have to pay to create additional ones? What? EN 10 is a pos. Barely more than a browser instance passed off as a desktop client.
  9. Finally forced to update from legacy versions, and testing out v10.x on a Macbook this afternoon. I was just spending a little time poking around and testing things out. Immediately I find a few practical usability features missing, and then encounter this rather significant data management one. Opening a note is not editing a note. And people wonder why users stick with legacy...
  10. Wondering whether this may have something to do with a Windows security setting patch. My issue on the Win10 machine may have begun after completing Windows patching. I was working on a bunch of machines and tasks this week, and don't recall order of ops/observation. I'm going to check a few other things to see if I can figure out when it began, and whether I had any system changes. I just logged onto a Win11 machine I haven't used in a while. EN 6.25.1 is working there. I haven't tested sign out and back in yet, though.
  11. This is the first response message I received. Exciting new features: "Improved performance and reliability". It worked fine the way it was. Web, btw, has always sucked, and isn't any better, I see. These other features I couldn't care less about. I have a calendar. I have the ability to share notebooks to work with others if I want. "Enhanced" collaboration should be part of a business suite of tools/options. I make my own checklists for tasks, and while I don't bother with them, I have/had? "reminders". I don't use any of this stuff. Everyone's doing this. I can't be the only one on the planet who thinks that products or services reach a pinnacle, and no longer require "further development". Just leave it alone. All the good stuff gets wrecked or discontinued. The abysmal UIs of streaming devices is another one of these things that's gone 7 miles down the wrong road.
  12. I noticed the same, re: #1. I just sent in a support request to see if I could get some more information, especially since the failure is inconsistent. I did receive a quick response, however, it was form-letter-y, tone unlike earlier EN support I'm used to in the very few times I've actually had need for assistance over the years. I, also, do not like bad surprises, like having my long-term workflow/organization tool disrupted. I was directed to update to the latest version(s) to resolve the issue. I have reasons for not doing so. I've responded politely requesting specific information on what's going on. I'd like to know what's not working or no longer supported. (IT minds wanna know.) Can you provide any detail on the Legacy EN you're running that is syncing? Oddly, I still have one instance running on a deeply rooted legacy machine, and it works on that one, but not in a newer OS.
  13. That's weird, my 6.25.1.9091 still works on one of my Windows machines, however, all logins were forcibly signed out yesterday it seemed, including the aforementioned. My Windows laptop would not sync at all yesterday, and I thought it may have been a temporary outage, but yeah, also wondered whether they'd cut the cord on me. Then noticed that the home machine was signed out when I got home last night. I'm here posting because my EN 6.9.2 running on an older Macbook was also signed out when I came into it this morning. Still poking around to see what's up. If there've been any announcements, I've not easily found them in initial searches, admittedly loose attempts.
  14. Yeah, I know we're all users, here, sure. I've been around a while. Was just wondering whether anyone had any specific info instead of generalization. How do you guys keep up with goings-on? The blog? Like this issue being the result of an outage last week, which support documented on the blog back on 10/5. I wasn't aware of the blog for announcements - looks like a good resource.
×
×
  • Create New...