You have a good point, but the problem that not knowing the table to select beforehand does seem valid.
What if the FROM clause is called SELECT and the SELECT clause is called PROJECT? (So it will read something like SELECT <table> PROJECT <columns>?)
This looks great. I have a work PC and personal PC on the same desk but cannot install anything on the work PC. Would be great to declutter my desk with this.
Unrelated - surprised JLCPCB does not have a way to share a link to a PCB so folks can buy a board without needing to upload the files themselves. Maybe I am missing it?
J, K, and L are keyboard shortcuts for "skip back 10s", "toggle pause", and "skip forward 10s". Left and right arrow keys do the same skipping. On mobile a double tap on either side of the screen again skips forward/back. A double tap with two fingers skips a chapter. Makes hopping around in a video a breeze.
>Due to the licensing of the underlying models like layoutlmv3 and nougat, this is only suitable for noncommercial usage.
Does this mean it isn't suitable if I wanted to use it in a product for sale or I cannot use it for tasks at my work?
I would like to try to use this at work to convert vendor documentation to include in our internal wiki.
If your work is commercial then you cannot use it. Think of it this way, is your work being used in a commercial business. Then it cannot be used. If you are using this for personal use or anything that is not part of a business, its ok.
How do you hide authenticating 1.3+m unique accounts? A distributed system? A mess of VPN's?
Or they don't hide it because the auth system is not checking for 1.3 million auth attemps?
> The researcher added that he discovered another issue where someone could enter a 23andme profile ID, like the ones included in the leaked data set, into their URL and see someone’s profile.
I recently had to explain to a tech lead that you can "never trust the client," because any dedicated party can just curl around your UI and send whatever HTTP request they want.
I remember when this first occurred to me from me deciding that I didn't want to click download a series of things on some website where this was the intended use. I wrote a small shell script to curl it for me, and somewhere during the process of writing the script, I realized the true "power" of this. Ever since then, GET with search queries were protected against in everything I wrote from that point forward. Luckily, that was in the late 90s, so it's been a minute.
