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

For ham radio, I would strongly recommend buying some 12v LiFePO4 batteries, or a product based on them. It seems many of these consumer "power bank" products (like ecomax) are built on lithium ion batteries, and with that comes much less useful lifetimes, finicky care requirements, and much higher possibility of fire/explosion.

It's pretty easy to convert 12v to anything you might need. Most ham radios will work on 12v. I'm very happy with my DIY setup with 48AH batteries (24AH x2 in parallel) in a harbor freight dry box, some anderson plugs, and a cigarette lighter adapter that I can plug a real AC inverter into, and/or a nice USB PD based charger.

I'm sure there are companies out there that have this all packaged up as a product. I think the key is to look for LiFePO4 batteries.


I too am very curious. I've seen this same message repeated a few times now. I've noticed there strange echoing in the reporting and messaging around this whole event, so I'm taking it all with a grain of salt.

My assumption is that if someone/something hadn't reacted quickly and cut load off the grid & remaining generators, the entire grid could've been pulled offline by the load. Since the TX grid would've been in bad shape, and isolated from others, a Black Start https://en.wikipedia.org/wiki/Black_start is what could've taken months.

I'm not any sort of expert, but I know that getting phases of AC grid synced back up can be tricky.


In theory, if you had individual leads to each LED, possible. However, I don't think the way WS2811s (and similar) are addressed would allow this.


The QR code contains data unique to your web session. You're already authenticated to WhatsApp on your phone. So the data in that QR code is sent back to WhatsApp's web server, through your phone, and they connect the open web session to your account. Websockets make it seamless.

Also, this is just an educated guess.


Very cool. Much easier to get working than powerline, imho.


Myself and some friends built a very similar tool during the LAUNCH hackathon. It's a shared code editor with some github integration for saving your work, and webrtc handling the video chat. Check it out, we'd love some feedback. https://seshcode.com


Relatedly, github insists on this width in both their language style guides and code windows on the web site. The VT100 had a 132 columns and was released 34 years ago!

Why are we still limiting code to 80 characters per line?


I find 132 columns is too wide for code (Good for tabular data, but not for code.) I want something I can read by running my eyes down the code. For me, this means no more than about 90 characters. A width of 132 cols means I have to stop and read back and forth, making it impossible to scan for something. Of course, YMMV.


Firstly, I can attest that migrating the datastore of an application which has scaled to require a NoSQL solution is no trivial task.

Secondly, I believe the author of the original posting really meant that "premature optimization is the root of all evil." Like this post points out, NoSQL solutions vary wildly in their abilities and usefulness. A relational database is a good place to start on the path to an MVP. And if you need features that a NoSQL solution can provide, and you understand the problem you're trying to solve, then use a NoSQL solution.


I think that most people who argue that such a migration "isn't that bad" haven't actually done it. Or at least they haven't done it for anything sizable.


It matters little how bad the migration is, when you ain't gonna need it in 99.9% of cases. When you are big enough to need the migration, your company has enough resources to roll your own Hadoop distribution.


I'm in Santa Barbara and am very interested.


Drop me an email (in my profile) or add yours to your profile and I'll get something out to everyone.


I also use Netbeans IDE. It works through a native gem and requires a specific version of the gem to work properly. Its a little funky, but I almost never need it.


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

Search: