I've had similar arguments with telco people. If the DIGITAL part of the system is not dropping (or delaying) packets then there is no problem with the DIGITAL part of the system.

Swapping cables that are not causing dropped/delayed packets for other cables that won't drop/delay packets is useless.

And testing the digital portion is very easy.

If you think you hear a difference, it is probably your imagination or the analog portion on either end.

Its like saying "Hey, Chevrolet, you know your customers like the radio station set to 101.9, why cant you engineer your cars to respect their choice instead of forcing your nefarious 101.5 agenda."

Yeah, but this is a Mozilla car analogy we're talking about here.

In the current 2015.7 model, release, the UX team has decided that a 5-button hamburger menu on an AM dial (and only from 1100Khz to 1150KHz in 10KHz increments) is all that's needed. Users who want to access a wider range of frequencies in the AM band are free to write an extension or purchase a third-party radio head unit.

To further improve the user experience, we remind prospective extension developers that in the Aurora channel for the 2016.1 model year, the about:config setting for frequency.megavskilohertz has been removed, along with the FM antenna. The UX team has made this recommendation based on telemetry that suggests that few drivers actually listen to FM radio, especially since the 2013.6 model, in which the AM/FM toggle switch was removed because the UX team for 2012.1 felt it was cluttering the dashboard.

From their other link:

With dedicated customer support available by phone or online, and replacements and exchanges whenever Pepper is not working properly, corporate customers will be able to use Pepper with peace of mind at their businesses.

Eat your own dog food.

Staff your support division with Pepper robots. PROVE that they work.

IF the people in charge are asking for it, find and suggest a solution that can do it safely.

I'm with you so far.

If they are not willing to pay for your solution, find another, albeit less safe solution and present it with a list of assumed risks. Rinse and repeat until you have a solution they are willing to pay for with risks they are accepting, then do that.

In my experience, any "solution" that you present will be understood to do everything that they wanted.

Even if you say that they cannot have X at $Y. They will give you $Y and then demand X.

When you cannot do so, a contractor will be brought in to set up a flawed implementation that will reduce your security BUT will provide X at a price point that you said could not be done.

Which is why we see this story pop up over and over and over again.

If you swap caps with control, then in vim you can use Control-[ for escape, which is also a pretty good option. (That's what I do.)

The problem I had was I wanted to map the CapsLock key to Control, and the LeftCtrl key to Hyper. There are built-in xkb rules for doing both, but they don't work right when you try to combine them, and the documentation available for xkb is hard to understand, to say the least. I finally got it working by hacking one of the rules definitions in the system-provided definition files to do what I wanted -- I gave up trying to figure out how to do it the "right" way.

Unfortunately it's hard to get xmodmap to play nicely in cases like hotplugging keyboards or using Gnome, at least under Linux. There is a standard option for swapping caps lock and control (or escape, or several other similar options), but if you want a layout option that isn't built-in, then prepare yourself for a world of frustration.

You could also invest in a tool to remap the key next to 'A' to "Control," like God intended. You don't need to get a whole new keyboard. Write on the key with a marker if you're the kind of person that looks at key labels when you're typing.

Worth adding is that the answers to someone's "security" questions often are easily obtained with just a small bit of social engineering.

Yep. Even easier if the information ("correct" answers) are available via Google.

But also, since you're already using unique passwords ... and the crackers managed to get your password ... how did they do that and would that have also yielded your "security" answers.

Their thinking seems to be:

1. So, one username / password isn't enough.

2. A second password should be enough, but it will use the same username as in #1.

3. And that second password should be SUGGESTED to be based upon something that can be researched / socially engineered / tricked out of the person.

4. And entered using the same channel as #1.

Okay, if you cannot get two factor authentication then at least use a different email address for each bank AND ONLY FOR THAT BANK. Email addresses are free. And always use completely unique passwords. Not bankname1 and bankname2.

The same for the "security" questions. Always completely unique.

If you have to write them down, do so. Just keep the paper in a secure location. It's far less likely that someone will break into your house to look for passwords than it is that someone will crack your computer.

Robin Miller: One thing that I think my wife and I are doing right: we don't have a bank anymore, we have a credit union, a local credit union and they do use secondary authorization on everything, you have to not just know the account number and the password, but you also need to know the answers to fairly obscure questions about our past, what year teacher was your favorite in what grade, things like that. Does that help?

NO!!! It does NOT!!!

1. It does not because that information can be collected at other sites controlled by crackers. So unless you enter incorrect information (which is, in effect just another password) then it is useless.

2. It is still on your computer. So if your computer is cracked then the crackers get your username / password / favourite-dog-food / whatever.

3. Find a bank / credit union that uses real two factor authentication.

Read carefully and you'll notice the government said he'd even have to accept the consequences of speaking out and engaging in constructive protest: they decree you can dissent against their rule, and that's well and good, as long as they can punish you for your dissent--which is precisely the situation in North Korea, where you may speak out against Kim Jong-Un, and, importantly, accept the consequences of speaking out against him.

Exactly.

If the end result of civil disobedience is the exact same in the USofA as in North Korea ... then what is the difference?

The politicians demanding martyrdom would be just as comfortable working for North Korea's government as they are working for the USofA's government.

And THAT is a very big problem.

Gamergate was ignored because gamergate is not news.

My problem with it is that even if the initial event happened EXACTLY AS CLAIMED then it is still nothing.

The "story" became the reactions to that nothing event.

And then the reactions to those reactions to that nothing event.

And now we have a post mod'ed +5 Insightful for claiming that Gamergate wasn't covered.

And also, from TFA:

If he felt his actions were consistent with civil disobedience, then he should do what those who have taken issue with their own government do: Challenge it, speak out, engage in a constructive act of protest, and â" importantly â" accept the consequences of his actions.

He IS dealing with the consequences. That's why he left.

What Lisa Monaco is pushing for is martyrdom.

We are supposed to be a country of laws. We should not have officials demanding martyrdom of those who oppose their policies.

What depresses me bout software is how often we JUST DO NOT LEARN!

And not just software. Look at security as well. And so many other computer-related areas.

Software development seems to be riddled with arrogant know nothings who think they can cut corners or reinvent the wheel because doing the right way isn't "7337".

For me it's more like ... someone "learned" one way of handing it when s/he was working ALONE.

Then that person never learned that the practices need to be changed when you are part of a TEAM.

And releasing your code to the public is being part of a team.