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

The only Morse code message I know is SOS which is ...---... and I imagine it's reasonably easy to understand when being tapped in an emergency situation. It would tell rescuers that someone is still alive and to continue their search.


Fun fact: the default message ringtone on old Nokias was ...--..., which is Morse for "SMS".

https://youtu.be/-uuG4ZCJmyU?t=57


I'd be screwed. Probably would be alot of irritated hams that day wondering why some asshole keeps tapping out OSO.


The article goes to great lengths to describe the difficulties in manufacturing and assembling the mechanism in the band itself but then also mentions that there a large ecosystem of third-party bands available. How do all those get made? Does every manufacturer have to use the same high-precision machines?


I've got two third-party straps. Basically, only the middle button in the strap works and attaches to the middle notch. Most of the time this is enough to keep the strap in place. But it is not as nearly as secure as it is with the original Apple strap. I use the original one when doing stuff like playing tennis or squash.


I had no idea that third party straps connected differently! Thanks for the info.

I have had two third party straps tear off, once during boxing and once while playing with my kids. The (much pricier) Apple ones never have, and so I only use those for sport as well.


Surprised that you don't take the watch off during boxing, is that supported? (Not saying you can't do whatever you want with it, just that are they really that durable?)


There's a "boxing" workout, but yeah it tore apart the third-party band I was using. Since then I have used my older Apple bands for boxing workouts and it survives. The watch itself is totally fine


Once I had a third-party strap tearing off while I was cycling. I was lucky it happened during a break. Since then, I only use original apple straps for any sport.


The strap side of the mechanism is much simpler than the watch side, and I suspect that for some styles of bands, you can even obtain fasteners from some wholesale manufacturer and attach them to your band, instead of fiddling with the dimensions yourself.


I'm in the same boat. What kept me from replacing the battery is that the device is EOL and won't receive any software updates, including security fixes. Did you also change the firmware?


Not yet - it's currently on stock software, but I've run custom ROMs before and I'm planning to switch back to one soon. I was basically waiting to see if I could successfully replace the battery before putting much effort into the software side.


Just switch to Calyx or Graphene, Pixel 2 is well supported


I think I understand how signing keys removes the need to update every server when adding a user to the system, but it seems like that comes at the price of having to update them all when someone leaves to revoke their certificates. What is the benefit of pulling revoked certificates to all servers periodically vs pulling authorized_keys files? Is it possible to work around this at all, e.g. conceive a system that eliminates all needs to push to servers? Is an online lookup like LDAP the way to go there?


If you use certs, then you also get Certificate revocation lists. You don't just trust the CA, you also trust the CA's CRL.

https://en.wikipedia.org/wiki/Certificate_revocation_list


The certificates have an expiration date, so if something goes wrong on that end at least it will expire after some time. Also, this takes care of role-based access - this you might not have with an authorized_keys file solution?


Certificates should have an expiration date, any system implemented with this pattern should expire after a couple of hours.

If manual, I would even consider doing it every week with the caveat that it would be a large attack vector.


The Reaction Control System (RCS) [1] uses hypergolic fuels [2] which are highly toxic. Such fuels are desirable in this application because they combust whenever the fuel and oxidizer are brought in contact. There's no need to an ignition system, which reduces the chance for failure.

[1] https://en.wikipedia.org/wiki/Reaction_control_system

[2] https://en.wikipedia.org/wiki/Hypergolic_propellant


From the headline I assumed that technicians were literally able to smell whether a chip is new, possibly by it releasing gases shortly after production. It reminded me of the distinct smell of new hard drives when you open the factory sealed pouch.

I was slightly disappointed when I found that the article describes software based testing instead.


I can confirm from experience that if you apply too much voltage it takes on that “never going to work again” smell :-)


"All diodes can be light-emitting - once"


Funnily enough, all diodes actually are light emitting, and light receiving, to some extent. It's why diodes are generally in opaque encapsulation. Whether a PN junction is an LED, PV cell or rectifier/switch is a matter of what the design optimises for. Try putting a voltmeter across a glass encased signal diode and shining a strong light on it to see it act as a PV cell. One wouldn't normally use a diode as a PV cell, but if the desired power was very small, a glass encased diode might be used as a cheap PV cell.



Of course chips don’t work if the smoke escapes, internally they operate on smoke. We tested this with a chip socket connected to 120VAC. All the chips that we connected released smoke, and none of them ever worked again.


From tinkering with electronics my brain has imprinted the smell of various components (resistors, capacitors), isolation. I often wonder what effect inhaling those fumes had on me, can't imagine it was a positive one.


One can imagine your disappointment when you discovered "code smell" has no actual odor.


That is an awesome product idea: A device connected to your computer that emits a pungent substance when you commit "smelly" code.

It could be part of CI. Instead of giving you an error, it fails silently but releases a terrible odor.


I saw this https://en.m.wikipedia.org/wiki/ISmell at Internet World in Palo Alto in 2000. It worked but it had no market. Maybe it can be resurrected.


You've just described my gastrointestinal system.


I'm sure a few web shops are quite happy bad code doesn't actually smell


Are you sure about that? I never want to be down in those CS labs ever again.


It does on my floor. =<


It's, uh, a reference to "new car smell" -- the combination of fragrance and volatile outgassing from new plastics that only lasts for a few months after manufacture. Even if you missed the social reference you got the idea: "new hard drive smell" is surely a physically similar effect.


I understood that part of the reference, but "tech" is ambiguous. If it meant "technician", then it would imply to me that the "new memory smell" was both figurative and something that a human nose could detect, in a literal sense.

Reading the article makes it clear that "tech" refers to "technology", making it more likely that the "smell" is purely figurative.


I too expected to read about people smelling the flash memory. The reason I expected that was exactly because I have smelt new car smell.


You can buy that smell in a spray can.


In my imagined version there was a chemical sampler/detector connected to a machine-learning algorithm, so basically a robot was doing the smelling.


I personally assumed it was a dog called 'Tech'.


Now if only they could detect how much wear and tear is on the filament.

6.3 VAC


Uhhhhhh, embarrassingly, same.


It looks like this paper has more information: https://arxiv.org/pdf/1712.01208v1.pdf


I tried "curl ipdata.co" and got a 301 page. It'd be great to get the same json back that's shown on the webpage.


The API endpoint is https://api.ipdata.co try "curl https://api.ipdata.co"


Here's a very funny rant about the overuse of QR codes: http://www.youtube.com/watch?v=V2rVYvylvZc


I found the title of this post to be misleading or at least stressing its point. The article says

"Some Internet Archive employees have elected to receive some of their pay in Bitcoin in April."

so it's not all employees, not all of their pay and not all of the time, as I expected from the headline.


I totally agree. This should really be changed.

Giving employees the option to take pay in bitcoins is a completely different issue to mandating it, as the title seems to imply.


And then when the title is changed, we give admins hell for changing titles. But you're right.


Thanks for clarifying this. I agree. I went into the article thinking it would be a compulsory change to bitcoin, not one employees could choose. That changes it to being somewhat cutting edge instead of tyrannical.


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

Search: