API keys are most successful when they're issued for server-side use; when used client-side the usual pattern that I see is for individual clients to request their own API key?
In this case, it would need to be distributed to myriad users who legitimately need to ask for the lists and then could be scraped by the "attacker", but at least then they'd have to be knowingly malicious vs. accidentally malicious.
In the case of interstate commerce (and catalog ordering, crossing the border to buy if you live nearby, etc) they have the concept of "use tax" where you must pay the equivalent of sales tax on goods you bought to use in your home state without paying state income tax. You are expected to pay use tax on goods you purchase on the internet tax-free at income tax filing time, and (a vanishingly small number of, I'm sure) honest people have been reporting their purchases and paying tax on goods purchased on the internet. Retroactively taking sales tax from those retailers would double-dip.
Glancing at the supreme court case, I'm not sure that observations that police officers can do from a public place have a good application to this area.
I think the public expectation part was specifically whether thermal imaging was too invasive and not an observation that the general public would make from the street.
I think light switches are an absolutely fantastic UI. You can look at them to determine state, you an interact with them without unlocking a device and when they're placed well you can just "wave your hand" and lights come on.
However, when the light switches aren't well placed it is nice to add a layer of software abstraction between the switch and the light to be able to rearrange existing switches in your home without having to pull new wiring. So you can essentially just keep what you are already doing but make the existing, mature UI even more suited to your needs even if you're skeptical of all of the rest of it.
Referred from your reply to my comment[0]; Algorithms can be backdoored due to having a novel technique to defeat them that you have not disclosed and has not otherwise been discovered yet. We are constantly adopting and discarding encryption algorithms that have not withstood the test of time.
If someone has gotten a jump on research and found a novel attack against their math, but the math looks good enough to convince others to use, that is an enormous advantage.
Running an algorithm chosen by an attacker with extensive resources is foolhardy, because you can never be certain that your resources are sufficient to detect a trap carefully hidden by their resources. We have a history of the NSA performing attacks and standards subversion. Why accept their potential trojan horse when you can have algorithms designed by those without that checkered past, keep up the same amount of scrutiny for potential trojan horses, and have decreased odds of a backdoor being present if the provider is more trustworthy?
It seems that taking motivations into account could lead you into a false sense of security, but that if you keep up the same amount of security and distrust known bad actors that you increase it.
HP's consumer line isn't/wasn't great (I've had scant experience with it over the years), but their business products are generally great to take apart and repair. The EliteBook series in particular, e.g. the 8460s are built like tanks and are great to pick up off-lease.
+1 to OneNote. The Notebook/Section/Page paradigm is super intuitive and convenient. You can create/copy hyperlinks to different notebooks/sections/pages/paragraphs, so it's easy to make a master notebook with shortcuts for navigation.
(un)fortunately I'm standardized on OneNote 2007, vs. the later versions, but keyboard shortcuts for it in 2007 on Win7 are fantastic. Win+Shift+N to bring up OneNote with the last page open, Win+N for a new unfiled note, and various "tags" and searches. Many Win key shortcuts have changed in Win 10 and later versions of OneNote.
I use checkbox tags for Ctrl-1 (you can assign Ctrl-# to particular tags), so you can easily make a checklist by just typing an item and then hitting Ctrl-1 to make a "todo". You can mark it as done by hitting Ctrl-1 again on the same line. You can also insert timestamps with Alt-Shift-F so you can note when you completed something or similar. Win+S brings up a screen snipping tool for quick documentation on a topic as you go.
Tree-style tab and middle clicking means that you can have a hierarchical record of your browsing when researching. Middle click three to five tabs from a search, middle click from each tab when reading through on the first article for any interesting subarticles, then when you get to the bottom you have a visual record of your path to that point.
To make things even better, when you're done with that research point you just kill the parent level tab and the children all go away too.
Tens of tabs is pretty typical in my workday and improves my productivity vs. fewer tabs and forgetting how I got to a tangent.
I can't say as I've paid much attention and I'm sure the majority of ice cream is made from artificial vanilla, but:
Vanilla beans appear to be about $6-7 each retail and $4-5 wholesale according to these random websites, despite there apparently being a bean shortage currently:
What are the alternatives once an event occurs and Google/Microsoft/Redhat/?? claim it was an accident outside of their control (possibly due to negligence)? Yes, outside experts will be investigating to the best of their ability and there will be a statement about what measures have been put in place to mitigate the issue in the future. But what else would happen?
A signed malicious update would be a Big Deal(tm), but the entity would also be able to survive it by claiming it was negligence. I don't believe negligence has not been significantly penalized in the marketplace, aside from perhaps CAs where damage can be limited (prevent new certs from being seen as valid, plenty of other options for sites). There's no such option available for penalizing Microsoft, and their lock-in is significant enough to limit nuclear options for doing so.
"We've revoked the signing key that was hacked by blah blah we have the utmost regard for security and adhered to best practices" and everyone would probably gloss over it for one instance.
RequestPolicy Continued in FireFox, and perhaps other plugins that control/restrict cross-site requests, asks for permission before redirecting to superdodgysite.com and safeandwonderfulsite.com. It's not a feasible solution for the masses, but I really like the control over browsing that it gives.
> There is no biological drive to own a gun, just a socially constructed one.
I'm not going to argue that a gun is the only or even necessarily an appreciable way to advance this in most individuals, but for many people it likely does work into this biological need:
https://en.wikipedia.org/wiki/Maslow%27s_hierarchy_of_needs#...
Perhaps I am cynical, but what's the profit motive for Google? They're much more financially motivated to be complicit and find vulnerable people to advertise to, if not create vulnerability, assuming that there won't be backlash against them in particular.
I think you could make your point without saying that "Most women can't handle adversity", which seems to be a dubious claim arising from extrapolation from your particular situation.
Assuming that your partners were fair-weather partners and that there aren't more layers to the situation, would you really want a partner around who wouldn't support you at your darkest? It seems coming clean has two incentives: you gain the support of someone close to you or you lose the facade of someone who doesn't seem care for you in particular (if I understood your situation correctly).
I looked at the two linked pieces of documentation, and to my naive eyes they look like they perform the same task:
PHP: "Bound parameters minimize bandwidth to the server as you need send only the parameters each time, and not the whole query", meaning that the statement is prepared server-side and parameters are sent separately.
Postgres: "A prepared statement is a server-side object that can be used to optimize performance. When the PREPARE statement is executed, the specified statement is parsed, analyzed, and rewritten. When an EXECUTE command is subsequently issued, the prepared statement is planned and executed.... Prepared statements only last for the duration of the current database session. When the session ends, the prepared statement is forgotten, so it must be recreated before being used again."
Is there a difference between the two, and could you elaborate?