> This topic seems to be broadly misunderstood. It is 100% verified fact by both myself and others (including university researchers) that diode strings can produce more heat (or watt-hours, BTU) from a given solar panel than a bare resistance element.

https://www.youtube.com/watch?v=42XIbHA9Dv0

That said, I don't work for Google and my conjecture is based on the hand wavy details (from engineers that do/have) posted online.

When you press the button on the USB switch to go to another PC, the software detects this and sends data commands over the monitor connection (using DDC standard) to trigger the monitors to switch inputs. You can use this same data communications standard to do things like adjust the brightness of your display. For example, I have these setup on my Mac to adjust the brightness of my two attached displays (complexity increased with multiple displays and desire for each to change at same time, simpler commands with a single display):

alias day="seq 3 | xargs -n 1 -P 3 sh -c 'ddcctl -d \$1 -b 80' sh" alias evening="seq 3 | xargs -n 1 -P 3 sh -c 'ddcctl -d \$1 -b 32' sh" alias night="seq 3 | xargs -n 1 -P 3 sh -c 'ddcctl -d \$1 -b 10' sh"

Does that make sense? As mentioned earlier, you're limited by the minimum number of inputs on the monitor(s) and/or the minimum number of computers the USB switch can be connected to. The simplicity of this system is that the display connections do not go through any switching layer and are instead directly connected to the computers (which avoids a number of compatibility issues).

I should be clear that I haven't used this yet but I'm going to try it. The Acer monitors I'm using have two HDMI ports and 1 DisplayPort so I can in practice attach 3 computers assuming I buy a USB switch which can connect to 3 or more computers.

Of course, git bisect still works with squash commits it just makes your job as the bug fixer much harder because typically squashed commits are quite large so you have to figure out what in the N lines of code introduced the defect.

For example, on a recent project I added prettier to eslint and tried eslint-plugin-prettier however it was very very slow (like multiple minutes for an eslint run). I discovered it's basically a deprecated package and the right way to use it is eslint on it's own (with ruleset for prettier so it ignores what prettier should do) and prettier on it's own. Then each command runs lightning fast and there is no slowdown. Their docs even go into this issue under Notes on this page:

https://prettier.io/docs/en/integrating-with-linters.html

No doubt tooling can be slow but looking for configuration issues or bad practices is a good place to start if things are slow.

I had an A+ experience being audited after my initial shock. They even have a secure message system where you can communicate via a website with the IRS including uploading files instead of having to mail letters back and forth. Definitely some clunkiness but overall it was solid and worked.

Not sure I'd recommend the experience but I definitely found it nothing to fear. I also found I didn't need professional assistance with being audited (I did seek it out but due to the time of year being so close to the next year's tax due date, I couldn't find someone right then so I decided to try fixing it myself).

As a contractor, I've chalked it up as yet another possible cost of doing business however it is frustrating and there seems to be very little one can do that actually results in getting paid without eating up the majority of the payment. Lawyers? See eating up the payment. Collection agencies? My experience was they were out for a quick buck but it was basically no protection from not getting paid a lesser amount (revised terms that ate into the payment). Government? See the other contractors experience -- probably will pay off but company might go bust before it happens. Going public? I think this might be the best route because at least it warns others (although typically it'll be too late).

Stepping back, I'm doing just fine and I'd be far more annoyed for those who have to work off the clock at minimum wage.

https://web.archive.org/web/20200604154641/http://blog.nucle...

I had the same problem with a Chrome extension for my side project Defero (school information system). It uses InboxSDK to integrate the Defero address book with GMail. Unfortunately, it got flagged for security review and it kept getting rejected no matter what I changed. I ended up concluding my authentication mechanism and/or my use of InboxSDK was causing problems so I'm going to try changing the authentication mechanism.

But working with the Google to try to get it fixed and finding the cryptic warnings they hide in various parts of the developer console has been extremely annoying. I don't blame you for your decision.

Anyone else using InboxSDK in a Chrome extension and didn't get killed off by this change?

My extension hooks up the address book from a SaaS project (school information system) to GMail so faculty/staff can quickly look up parent contact information or send to special group email addresses that broadcast out to part or all of the school. The people using it were very happy to have it but I could conceivably go back to a private chrome extension if that is still allowed.

https://joplinapp.org/

I like the ability to use tags too -- I've got various product/tech ideas and it's nice collecting information with it and not having to worry about the pages going away or changing.