You do get a feel for where the important parts of the error actually are

Yes, after decades of scanning large pages of text - code, errors, logs, search results, etc - a programmers ability to apply pattern recognition to screens of letters can be truly remarkable.

Ah yes. Life before Agile was wonderful.

Care to elaborate?

Closed as a duplicate

Yeah and it won’t tell you that it hasn’t seen this pattern before. It will just make things up out of the blue which seem like they might be correct.

Stay away from ChatGPT for bleeding edge things.

What OS do you run? Are you planning on sharing this app with others? Should it be a web app?

Happy to help!

In my 30 years of experience, it is usually the devs.

I’m well aware how async works in the single threaded js environment. All code blocks the main thread! Calling await on an async operation yields back.

You’re right, async is commonly mixed up with multi-threaded. And in fact in many languages the two things work hand in hand. I’m very aware of how it works in JavaScript.

We are agreeing. Don’t need more info.

Yes I’m simplifying a LOT, but in the context of background web calls, that was what callbacks became so important for. XMLHttpRequest in IE 5 sparked the Ajax movement and adventures in nested callbacks.

Prior to that, the browser had window.setTimeout and its callback for delays and animation and such - but that’s it.

The main purpose of all this async callback stuff was originally, and arguably still is (in the browser), for allowing the ui event loop to run while network requests are made.

NodeJS didn’t come into the picture for almost 10 years or so.

It can lock up a UI doing cpu bound work. Making a web request, no. Preventing the ui thread from waiting on native IO is what async was created for.

Symlink a git tag?

It’s domestic as well. Red vs Blue is just a distraction and you can’t point this out because nearly everyone is divided along those lines to the point of ignoring getting fucked up the ass.

Onboarding new users securely is in the forefront of most minds in my industry because the current standard is a 12 word phrase written on paper, which most users throw in a cloud solution or screenshot.

The stakes are even higher in crypto where you’re protecting, without recourse, large sums of value. Passkeys are a critically needed solution for my industry. But they need coupled with a social or offline storage recovery mechanism.

I agree 100%. As mentioned, I rarely share my approach and I’ll be deleting that comment in a bit. It works well for me.

No hacker is attempting to decode the password algorithm because they don’t know of its existence on my logins, and they have thousands of better ways to go - as you said.

I’m of the mindset that locally stored keys and/or social solutions are better than throwing all passwords in a single place.

All passwords for large amounts of people in a single place is begging for a break-in.

I spend a lot of time studying solutions in this space as I’m a long time crypto solutions dev. Lots of ideas and discussions to be had.

I’m not disagreeing with you, just having a dialogue.

One doesn’t have to remember dozens. Just a basic algorithm for deriving it from the name of the site. Complex enough that it’s not obvious looking at a couple passwords but easy to remember.

This method works for me. I understand its dangers (can still correlate. Dozen passwords and figure out the algo). But it’s my current approach. I hate even discussing it since obscurity helps.

I use a different password for every site tho. Using same pw for every site, that’s another extreme entirely.

But does their advantage in security overcome the fact that they’re a much larger target?

It’s similar to how money under a pillow could be safer than money in the bank; depending on who you are.

Interesting. I never really realized how it was more my path changing than the entire industry.

Isn’t all hosting containerized at this point? Is hosted, language specific servers still a thing?

I’ve been out of the market for a while now and just run everything as containers on aws and gcp