Perhaps it was one of these audits?
3,559 karma · joined June 26, 2013
If you are a human and you wish to contact me, the sha1 hash of my email address is 9aae0f6d01421dde3d5085fa1a24adff6c9e344f. I look forward to hearing from you soon.
Hi'); DROP TABLE emails;--
<script>alert('Hi!')</script>
Perhaps it was one of these audits?
json jcof jcof/json
plain 244975 87083 0.355
gzip -6 35829 33152 0.925
gzip -9 34384 32875 0.956
xz -9 27864 28696 1.030
And I imagine this is close to ideal for jcof. So unless that last few % really matters, gzipped JSON is probably much better in the general case.In my case I did some tests, and the additional power usage of the dehumidifier is way more than offset by the power savings I realize by running the air conditioner less frequently. This only works because the dehumidifier enables me to be comfortable at a higher indoor temperature.
Because it's less humid, I can maintain a higher indoor temperature and still be comfortable, meaning the air conditioner needs to run less.
Do I use net less energy? In my case, yes, but your mileage may vary depending on your equipment, insulation, etc.
On especially hot days, I will raise the setpoint higher, and use a small fan to circulate air around where I am spending time, which is very effective when humidity is not too high.
So maybe if you have relevant experience and can show it, apply anyways?
$ dig +noall +answer A news.ycombinator.com
news.ycombinator.com. 0 IN A 50.112.136.166
$ nslookup 50.112.136.166
166.136.112.50.in-addr.arpa name = ec2-50-112-136-166.us-west-2.compute.amazonaws.com.This seems like a nicely clever way to trip up non-targeted scrapers which might attempt to OCR any images they encounter, but which will ignore what looks like random gibberish codepoints. It doesn't eliminate the ability to index this data but I can see how it might greatly reduce it.
Obviously you could still convert these PDFs to an image and OCR them, but that's not the thing being defended against here.
You add the long lived IAM user API key/secret to it and it stores it in a password protected storage (MacOS keychain or similar).
Then you invoke aws-vault with an IAM role and command, and it will handle obtaining short-lived credentials scoped to that role (including TOTP 2-factor code auth), and then run the command with those temporary credentials as env vars.
With the right AWS permissions on your user, it can also automatically rotate the IAM user API keys for you.
I don't know why they would include it if they don't have plans on continuing the show in some form in the future. It's not like there was any shortage of content in the mainline story to cover.
I've also experienced the AWS console being less than stellar at fault-tolerance when acting within very restrictive, targeted IAM roles. The only solution would be an overly broad permissions grant which is not always viable. Or well, if you spend enough money you can try to beg your TAM to get it fixed, but in the meantime between "now and never", your solution would still be pushing empty commits.
To carve out minimal permissions, you have to start with nothing and repeatedly attempt to do the action in AWS console, and check CloudTrail to see what got denied. Increase role permissions, lather, rinse, repeat until it works and pray they don't update the console and break you again.
It's possible that either this process is too tedious to be worth doing, or produces a policy more complicated than they wish to use, or requires a policy that is more permissive than they wish to use.
And yes the rockets had shape charges in each stage which can be activated to destroy the rocket in a controlled fashion. If you have a rocket gone haywire, it's better to jettison the crew capsule to safety and do a controlled demolition, to prevent the rocket from flying out of control and crashing into structures or people on the ground.
This is also why rocket launch sites tend to be coastal locations with ocean to the east - there's a lot less valuable stuff under their flight path.
"LinkFinder is a python script written to discover endpoints and their parameters in JavaScript files. This way penetration testers and bug hunters are able to gather new, hidden endpoints on the websites they are testing."
The short description from the page itself is:
"We generate money by serving Google text advertisments on a network of hidden Websites. With this money we automatically buy Google shares. We buy Google via their own advertisment! Google eats itself - but in the end "we" own it!"
But yes they have successfully run a smear campaign to make you think that a greedy woman went after millions of dollars for an injury that she alone caused, which is a wildly inaccurate summation of the situation.
If you want to uphold a commitment to backwards compatibility, you simply cannot extend your language in a way that might possibly change the behavior of valid-but-nonsensical code in the wild.
This pushes menu and status bars up into the bezel area at the top of your laptop's lid, leaving more room in the primary 16x10 display area for apps and things.
It's free real estate, why not have menus go up there?
The short answer is that the headline is rubbish. A law originally covering only fish was amended by the legislature to expand what it covered by redefining the meaning of "fish" in the rest of the statute, which is simpler than amending each mention of "fish" to a big long list.
One of the categories in that list was "invertebrates", and this court ruling simply found that non-aquatic invertebrates are included, and therefore bees are included.
But it gets more clicks to say "bees are now legally fish in california"
As I understand it: The short answer is the legislature changed the statutory definition on more than one occasion where it can be shown they were aware of the broader interpretation of that clause being in use and took no action to narrow it. This, according to the decision, establishes legislative intent for the broad interpretation, which supersedes ejusdem generis.
[1] https://www.courts.ca.gov/opinions/documents/C093542.PDF
"""In 1969, the Legislature amended section 45 via Senate Bill No. 858 (1969 Reg. Sess.) (Senate Bill 858) to add invertebrates and amphibia to the definition of fish. (Stats. 1969, ch. 689, § 1.) Section 45 has been amended only once since 1969 -- in 2015 (effective January 1, 2016), when the Legislature made nonsubstantive stylistic changes, modifying the definition to read “ ‘[f]ish’ means a wild fish, mollusk, crustacean, invertebrate, amphibian, or part, spawn, or ovum of any of those animals.” """
[1] https://www.courts.ca.gov/opinions/documents/C093542.PDF
- Were the prompts shown the ones fed to DALL-E 2 or were there more complex details described in the prompt?
- Were these the first images generated for the prompt, or did the author generate many images and cherry-pick the best example, and if so from how many?