The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Yea thats the right way of doing it. This was more along the lines of something that only needs to be `as-secure-as` your email account. Perhaps the website is a serverless architecture and it uses your email address as your username and for communications, but beyond that it careth not.
Like I said, it was an idea but I haven't found a use-case for it just yet.
In a recent ground-up rebuild of an application, I had a related argument with the project lead/client. I tried insisting that we should include no forced rules, but instead provide a strength meter based on the zxcvbn library.
My argument: a users password is a users password and who are we to define what is a "correct" password? Instead, we should warn against perceived password strength and accept what the user provides.
Final decision? A password must be at least 7 characters long and contain at least one letter and one number. *sigh* "pass123" is considered a "very strong" password.
I never could understand why the Kerberos authentication service didn't catch on. It has a a true beauty in its protocol design. Second only to encryption algorithms it must be the most thoroughly analyzed protocol in the entire networking world, and no serious flaws have been found. A truly high quality open source code implementation is offered.
Kerberos is ready for use, and has been for about thirty years. When it was new and being talked about, in the late 80s and early 90s, some academics took pride in pointing out limitations (such as how to forward authentication and authorization to a backend server in a reliable way) - but evem though there were proposed alternative solutions to handle such issues, that's not what we are using today. We use extremely primitive solutions, with numerous weaknesses that would have been cured by adopting Kerberos.
The market forces didn't want Kerberos. They wanted poorer solutions, and got it.
Watched a great 4th July firework show last night. Also spotted a number of large drones appearing to cover the event. I thought the first I saw was a dirigible but it was either too small or too high. Then I spotted several more so it was either an alien invasion or drones. I'm going with drones.
This is irresponsible of the owners. While it is harder to knock any aircraft, large or small, out of the sky than most people think, sooner or later it is going to happen. The rotors spin realy fast and any contacht with another object destroys them and most multicopters can't compensate the loss of one rotor, especially when it has only lost one blade and starts to wobble.
Larger multicopters can easily weigh up to 10 pounds, the heaviest single parts are the batteries. My (traditional) helicopter weighs about 8 pounds, half of which goes to the two flight batteries with about two pounds each. You don't want it to fall on your head without warning and you also don't want any contact with the main rotor. It can kill, which unfortunately already has happened when the owner lost control over the model.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
Back in the good old days, when I worked in C++ I would use the class view in Visual Studio as my primary means of navigation. When I switched to .NET, I stopped using it and switched to solution explorer which seems to be the norm amongst the .NET crowd.
These days, I tend to use Resharper to get where I want to go quickly, but let's not muddy the point with that.
Thing is, I don't know why I switched (it might be the presence of annoying namespaces), and I still think in classes rather than files - don't we all? Today, I'm going to go back to the old ways to see how I get on.
Do people still use class view or know the cause of its demise in popularity?
Probably because the best practice in .net is one class per file and to use folders for your namespaces so in a way the solution view kinda is the class view, but you get all the other stuff as well that aren't classes.
Though I dare say most VB.net solutions probably warrant the class view more
*or is it Button17 I'm after*