anonymousisme

New Mexico was having massive flooding just a few weeks ago, but maybe not localized to Albuquerque.

Should also include the political/policy problems related to processors preventing transactions for "unpopular" product/service providers.

All of those electronic locks are garbage. Last year I bought a safe with a S&G mechanical spin-dial lock. Those are GSA approved. S&G also has electronic spin-dial locks, but they do not seem to be available as an option on consumer/commercial safes.

There are plenty of other contemporaneous sources all saying the same thing. Similar to the now dis-proven Russia-gate hoax, the DNC are the ones pushing the narrative that the leak was a Russian operation. The analysis of the time stamps on the DNC files has proven that they were not copied over a network, but copied locally.

I've done this and it makes a big difference, but I still get a lot of junk from local businesses. Either those businesses are not part of the DMA, or they are ignoring the opt-out list. I'm not sure what to do about it.

Agree. Creating corporate sovereignty for insurance companies just re-enforces government interference in a free economy. As a result of the interference, health providers have continuously raised their prices far beyond what anybody would pay in a free market. If nobody had insurance, what do you suppose would happen to health care costs? Answer: They would adjust to what the market will bear.

Ruckus is not bad, but not great either. I've got a ICX 7150-C12P that worked fine until the PoE power supply failed just a few months out of warranty. I'm glad that I did not pay them for the "license" to use the SFP ports (which every other manufacturer just enables by default).

I do like their WAPs. I've got a couple of RS510 WAPs that do a great job, but initially they had some noticeable performance problems for almost a year until fixed by a firmware update.

I had a legitimate call from my credit union last month. They were following up on a problem I had reported with their on-line bill pay system. Toward the beginning of the call, they wanted to verify that it was me and they asked me to provide them with the 2FA code they had just texted to me. I declined and told them that this is what scammers do. They agreed with me and encouraged me to call them back at the number on my ATM card.

I thought it was really unprofessional of them to operate this way.

Ten years ago I went back to school and finished my BS. All of the instructors required us to run our work through a plagiarism checker and certify that it was our original work when turned in. The plagiarism checker was part of a suite of tools that included a grammar checker, and some instructors used the grammar checker themselves when grading student work.

I always viewed the grammar checker as a crutch and only used it when required, but some students I worked with on team projects were obsessed with getting no warnings from the grammar check. There were a few ESL students that produced almost unintelligible work that had passed grammar check, and they argued with me when I tried to help them.

My best experience was when one instructor ran my work through the grammar check and then sent me the graded paper (A) which included his long critique of the changes the grammar checker had recommended.

The film packs included the (flat) battery, and the (non-rechargeable) battery always had plenty of charge left after the film pack ran out. I salvaged those batteries and used them in many electronic projects.

Heh. I used Netcom and they did not outright ban slirp, but they did have a script running that would renice (lower the priority) of user processes once they reached a certain total cpu time (two minutes). I discovered this feature shortly after they implemented it because my slirp network performance went down. Note that I am referring to cpu time and not run time. Most processes spend most of their time waiting for something, so accumulating two minutes of cpu time under slirp usually took several hours.

My solution was to write a program (I called checkcpu) that would spawn a process (slirp) and periodically check its total cpu usage. When it hit the threshold (110 seconds), it would spawn a child and suspend the parent (seamlessly passing the current run state to the child). It worked great and they either never noticed what I was doing, or they did not care. Over time, the number of suspended parent processes would rise, but it never became a problem.