Hacker Newsnew | past | comments | ask | show | jobs | submit | mallin's commentslogin

> Cloud Shell is available throughout our documentation set on Chrome desktop browsers (version 74 or higher).

Is there really a reason this couldn't be made to work on Firefox? Or could they just not be bothered?


https://cloud.google.com/shell/docs/limitations#browser_supp...

Possibly related to the 3p cookies limitation described in the docs? Cloud Shell itself has wide ranging browser support.


Which is funny because Chrome is dropping 3p cookies soon as well.


You mean the ICO?


For anyone wanting to read more about this, here are some articles and data from the Climate System Analysis Group at the University of Cape Town.

This article explains the severity of the drought, and calculates that the return interval for a two-year drought of this severity is 1150 years (!), which mostly absolves the City of blame for not anticipating it: http://www.csag.uct.ac.za/2017/08/28/how-severe-is-this-drou...

Here, you can see an interactive plot of rainfall in Cape Town. Highlight 2017, 2016 and 2015 to see the reason for the current crisis: http://www.csag.uct.ac.za/current-seasons-rainfall-in-cape-t...

Addressing the scaremongering by the City around "the new normal": http://www.csag.uct.ac.za/2017/11/01/is-cape-towns-drought-t...

Describing the difficulty of forecasting this drought: https://theconversation.com/why-cape-towns-drought-was-so-ha...


> calculates that the return interval for a two-year drought of this severity is 1150 years (!)

This is however calculated based on historical weather data from 1920s onwards. With climate change ongoing and increasing, we can't rely on historical weather patterns staying accurate for future predictions. Old every 100 or 1000-year droughts can become every 10-year droughts.


In practical engineering (on circuit diagrams, bills of materials, etc), you almost never see the "Ω" symbol. "K" is used for kΩ, "M" for MΩ, and "R" for Ω (as in 330R is a 330Ω resistor).

It's nothing to do with programming language design.


Well, there is http://www.ohwr.org/


no, when I said viable, I meant, buy on Amazon. cheap.


Probably because, for all that we complain endlessly about the evils of capitalism, if someone isn't making enough money off of it, there is no motivation to make it available.


"I have a standard agreement that all my clients sign. If you aren't willing to sign it, here are some other freelancers I can recommend."


That can be tricky. Venture funded companies that are totally legit and run by competent people sometimes don't want to use a vendor's form. That's not really a red flag...


Great point, noted for next time for SURE!


I would first read the agreement they want you to sign though. If it's not bad and you can live with it, it's sometimes worse it to compromise. Some of the bigger clients cannot be flexible on contracts.

Of course, one important thing is too decide how money you're willing to risk. If you're not willing to risk more than two week's worth of work, then bill them weekly so that you can act quickly in case they decide to stiff you.


It looks like all URLs in plain text on the page are being rewritten (eg. from Amazon.com to Amazon.com.prx.uk.teleport.to). URLs in <a href="..."> fields are not, but only if they point off the domain you're visiting.


It's certainly not the intended behavior, but it's not a surprising bug either. The rewrite was surprisingly tough to make work even most of the time. But if you could share the specific site this happened on, I will likely be able to fix it.


Though it's certainly a valuable number to know, I'm not sure a huge "TIME WASTED WATCHING TV: x DAYS" is what people want from a TV watchlist. (Whereas this would be a valuable feature in a productivity app.)


I'd though so, but I have a friend that run a similar site, and he told me that this was one of the most request features.

Sure, the choice of wording is unfortunate. "Wasted" is a negative word, I think "Time spent watching TV" would work better.


"TIME WASTED" is one of their feature. I think much more valuable will be knowledge what you have to watch next and what you have missed.


Probably best not to upload your private key to Github!

https://github.com/hal9000xp/euclid/blob/master/core/server....


This is a throwaway key that's used for tests. But other people may miss it. So I've explicitly marked these files and config cmds as test files and cmds. Also, I put a warning msg to log and to README.

If you put production cert & key to config (see README), warning disappear.

Thanks for the report!

P.S. See updated status of issue #2


It's more helpful to private message people these things, sometimes the author doesn't even know their project has been posted to HN.

Last week I wanted to comment about a bug on HN, then I realized it's more constructive to open up an issue on their Github repo.


I compared the author's Github username and the submitter's HN username and assumed that they were the same person. Though a private message is probably still a good idea.


Yeah, I'm working on this project alone. Feel free to ask me for features.


As far as I can tell, this is a throwaway key thats used for tests.


Likely it is just a throwaway.

If nothing else, this might remind those who see it that you can leak private keys / passwords if you put then in source control.

Chris Poole described having this exact problem, in his recent post about 4Chan being hacked - AWS keys in the commit history. (http://chrishateswriting.com/post/84931829578/when-a-bad-day...)


This doesn't actually extract sheet music, only the chords present in the music.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: