JimmaDaRustla

I'm probably explaining something most everyone here already knows, but:

I don't know what Glacier uses, but the "offline" storage is much the same how mainframes use tape - disk based files (datasets in mainframe speak) are migrated to tape after a given amount of time to decrease storage costs. These datasets needs to be recalled back to disk to be used again. This is nearly identical to how Glacier operates with S3 as explained by Amazon.

The reason tape isn't available immediately is because the tape drive, unlike a traditional harddrive, doesn't contain a reader. So multiple tapes typically sit in machines with only only a few readers that move back and forth based on requests made to read the tapes. If there are many requests, the amount of time to recall a dataset increases.

Glacier may or may not be using tape, but the behavior is nearly identical to how tape has been used in past systems.

Only if you've already accepted the terms of use initially, this is fine.

I'd love this feature - connecting to all the open wifi connections around downtown and then letting my phone/laptop log me in through their terms of use acceptance pages (looking at you Tim Horton's) seamlessly.

Probably not, they knew that their jobs would be much harder if Apple failed.

Welcome to HN, where people vomit their assumptions like it's fact and get to the top of the comments section.

"Recycle your Android Phone"

Well, that's quite petty insinuating that the Android device is essentially garbage.

Source Forge has been doing this for a while now, not just gimp.

Pretty sure I downloaded Synergy and it deceivingly downloaded a common installer which was small and installed adware as it downloaded the proper executable which you desired to download in the first place

First SkyDrive, now Skype? What is this company's deal with attacking Microsoft and others over a very very generic word?

For what it's worth, Sky is only 60% of Skype, and Skype has 2 more letters.

Battery University typically looks at a discharge as a discharge.

For example: Discharging the battery fully might yield 200 cycles, but discharging a battery 50% might yield 500 cycles. Obviously with the 50% discharge, you're only using half the capacity, but when you multiply the number of cycles by the capacity used, you can compare them.

That's assuming that devices don't already operate in this range of SOC within device...which I wouldn't believe to be true.

The only concerns I have with this advice is the heat generated by constantly draining/charging the battery will degrade the life, plus constantly cycling will degrade the battery in other ways as well.

If a charger could be tweaked to charge the battery slowly and not overcharge it, that'd be the ultimate solution.

SOC is relative to the application, but it is possible many applications nowadays purposely operate within a specific SOC and not exactly 0-100%. We need an Apple battery engineer in here to confirm ;)

Edit: You already acknowledged this elsewhere.

Heat is a major cause of battery degradation, partially why I don't agree with constantly charging/discharging since it causes more heat.

Keep your laptop cool, perhaps even consider battery saving options while plugged in if you find it is generating too much heat.

Edit: A running laptop will cause heat, so shut it off when not using it. A plugged in laptop shouldn't create much more heat than a laptop running on battery power, if anything, the battery should be cooler when plugged in and fully charged (assumption made).

A few things:

1. A lithium ion battery charger is smart, it will not overcharge or harm your battery in any way keeping it charged.

2. In terms of discharging a lithium ion battery - they are not susceptible to memory like ni-cd and ni-mh batteries, so regular discharging is not required.

3. Apple and other companies will suggest discharging your lithium ion battery fully. The reason being that a complete discharge followed by a full recharge will update an internal counter which records the capacity of the battery. The capacity decreases over time, so your battery charge indicator will need this full discharge/recharge regularly to stay accurate. Not important for actual capacity you get out of your battery.

4. There is a recommendation that in order to get the MOST NUMBER OF DISCHARGE CYCLES out of a lithium ion battery, you should only discharge it to 50%. I put MOST NUMBER OF DISCHARGE CYCLES in bold because it is important to know that this is the most important factor in the life of your battery - you do not need to discharge the battery to 50% in order to get a longer life, but if you do need to discharge it, 50% discharge is optimal to avoid any damage by over-discharging. If you discharge your battery EVERY day because you charged it to full, you are going to severely decrease the lifespan.

5. (Edited in) Laptops and phones use a State of Charge estimation model to decide how full the battery is. Depending on the device, the manufacturer may suggest fully discharging and fully recharging the battery so that the estimation model understands the capacity of the battery and avoids overcharging: http://chargedevs.com/features/the-challenges-of-battery-sta...

My recommendation: Don't discharge when it is full. Only discharge when you need to. Charge it at 50% if possible to avoid over discharging. KEEP IT COOL - heat kills batteries lifespan as well.

Battery technology has changed a lot since I worked in the industry - they're always advancing and changing. There are many resources to keep yourself well informed: http://batteryuniversity.com/learn/article/how_to_prolong_li...

Edit: All applications and devices are different. My recommendation might not be the best - some have suggested avoiding keeping your battery at 100% constantly, whereas my suggestion assumes that the charger won't harm the battery by overcharging. For example: battery is at 100% on the device, but in actuality it is sitting at 90% state of charge in the context of lithium ion technology.

Usually the reason behind discharging fully once per month is because when this happens, the laptop records how much capacity is required to recharge the battery. This will keep your battery % left accurate.

The actual preference for getting the MOST DISCHARGES out of a lithium ion battery is discharging it to 50%. This, however, doesn't not to equate to longest battery life (in terms of age) for the use within a laptop/phone.

Edit: There is something state of charge estimation models which may rely on this variable to decide how full they'll charge the battery. If you don't fully discharge and fully recharge the battery to update this capacity value, the SOC estimation model might overcharge the battery, thus decreasing the lifespan.

Sounds like it could have been intentional - I see people in the banking industry constantly jumping jobs across all products and different sectors of the bank in order to gain experience and understanding of the company from all sorts of angles.

Interesting. I guess he/she is implying that Lumen is PSR-7 compliant than by the last sentence?

Thanks!

They compare it to Slim 3, which isn't completed yet, sitting in a development branch...

Slim 3 will also be PSR-7 compliant, I don't see anything about that anywhere in these Lumen docs.

C# was fully designed and developed by Microsoft.

> It was developed by Microsoft within its .NET initiative and later approved as a standard by Ecma (ECMA-334) and ISO (ISO/IEC 23270:2006).

http://en.wikipedia.org/wiki/C_Sharp_%28programming_language...

Thanks for just ignoring my question - THERE IS NO ENCRYPTION IN THE ORIGINAL ARTICLE, so WHY are you restating that encryption is involved at all?

Straight from the original artical:

  hashed_password = scrypt(password, salt + pepper)

or

  hashed_password = scrypt(scrypt(password, salt),pepper)

Absolutely zero encryption going on here. Therefore, no ability to "decrypt" the pepper result. The pepper IS NOT a key for encryption. Period.

Your question depends on your definition of retroactively.

I think the article's context is if you don't currently use a pepper, you can easily add one and update all of your password hashes in the database.

Where in the original example was encryption involved? The salt and pepper were only ever used in a hashing algorithm.

In pacofvf's example, you are correct.

But, the original example is hashing the password. No encryption involved. So what makes anyone think that they can reverse a hash?

Excuse my ignorance, but you probably shouldn't be able to reverse an irreversible hash.

I drove a 2000 Jetta TDI for a short time about 12 years ago. The fuel economy was way better than gasoline (something like 40% more?), and the price of diesel was cheaper (15%?)

Now the price of diesel is always more than gasoline (12% today). When I bought my new car, I had priced out a TDI Jetta, which only came in higher end trims. The amount of money I would save wouldn't break even with the additional cost of the car (over a gasonline model) until about 300k km of fuel savings, which is longer than the average lifespan of a car (diesels probably live longer though). Sure I would have a nicer car, but it was out of my price range and I would be stuck with an under powered engine.

The irony!

I didn't even make that connection until you said something.

True. But it feels like a chapter out of 1984 when people can't make ambiguous opinions without someone knocking at your door to correct you and deny you your speech.

I am/was a bit opinionated, but within reason. I never made threats or claimed anything I said was fact.

It seemed like there were a team of people who were on news sites denying comments like mine, probably just your average tech site commenters though. Some people were adamant that brute forcing (algorithms and dictionaries) would not be possibly and would take 20+ years to crack one password.

The real interesting thing to me was how it was permanent ban without warning and without ability to be appealed.

I got banned from theverge.com for suggesting that celebrities' Apple ID passwords may have been cracked by a brute force vulnerability with iCloud.

Permanent ban, no explanation, no e-mail. The fishiest part, someone (not verge staff) replied to my comment saying "enjoy your ban".

I've been weirded out by the power and bias of Apple employees and/or fans ever since.

I find biased views too often at the top of HN stories, so it is rare for me to read them.

I use serverbear.com for comparisons

Will bookmark this one though.

Absolutely. And the pirated versions keeps getting updates just like a fully paid version of Windows.