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

> and that this is common folk knowledge among solar installers.

I think it's partially that people want to spend less money and undersize their inverter setup. The average end user non technical consumer (maybe a person buying an off grid PV system from an installer) may not fully understand what 1500W really is, and that something as boring as a $35 tiny space heater that sits on the floor can be a 1500W load.

People will be really surprised if you tell them that their tiny floor space heater uses the same amount of energy as charging twenty high performance laptops simultaneously.

It takes just a few high wattage single item electrical things to totally screw up the electrical load budget of a site, if somebody has something like a single 8000W rated inverter.

If you want to use electric space heaters and kettles and hairy dryers and hair curlers and such, along with the other regular daily load items of a house, you're looking at a setup with multiple 6000-8000W inverters in parallel with each other and synchronizing their output waveforms. Not many people want to spend the sort of money that'll get them 3 x 8000W inverters in parallel with each other all properly installed in an electrical room next to the PV stuff, breaker panels, etc.


It rather resembles the CGI protomolecule from 'The Expanse'.

Latest-gen zigbee stuff and zwave 800 seems to have already thoroughly occupied that niche for a great deal of home and office automation equipment.

> And yeah, you pretty much already have to have a visible line of sight to get anything even close to 1 Gbps

If one considers that the higher speeds in 802.11ac and 802.11be require 256QAM modulation or better, this is completely expected (assuming 5 GHz band of course, which doesn't go through material very well at all). If you've sen a live eyeball chart of a 256QAM or 1024QAM constellation on test equipment for clear-air microwave link purposes, and seen how quickly it can degrade or get fuzzy if there's anything in the way of the link, it becomes more readily apparent. MCS levels 8 and onwards here:

https://en.wikipedia.org/wiki/Wi-Fi_7

"Clean" eyeball example of 256QAM: https://www.everythingrf.com/community/what-is-256-qam-modul...

examples of "fuzzy qam" in 16QAM, same principle applies to denser QAM

https://www.researchgate.net/figure/Typical-eye-diagram-Symb...


how many spatial streams are you using (2x2, 3x3, etc) and are you using an 80 or 160 MHz channel?

If you have a set of full capability 802.11be clients you'll see the best performance with a 3x3 AP and 160 MHz channels.


It's an interesting thought experiment to consider how much of 'the internet' would still find a way to communicate with each other and fix the problem if somebody waved a magic wand and all http and https servers and clients magically disappeared worldwide instantly.

For instance some of the folks who run core BGP at medium to large sized ISPs would revert back to a few legacy IRC channels and find each other to chat and figure out WTF is going on.

"the internet" would still exist, a subset of the application layer stuff that runs on top it wouldn't...


I bet we'd see a bunch of unexpected breakage in presumed-to-be-lower-level-than-http[s] infrastructure so that eg. your legacy IRC server goes down because it's running on rented hardware and the hosting provider's operations rely on some internal http services.

This is extremely likely in the case of many automated provisioning, billing, and web interface control panel systems for shared hosting platforms, VPS, virtual machine service providers that likely do something https to https internally to communicate between tooling.

In my intentionally absurd theoretical scenario, what would remain up would be the bare metal in colocation in certain service providers' environments...


Indeed. "Compliance" can mean some internal audit/monitoring system has tripped and requires in depth investigation and preservation of logging, or it can mean "federal law enforcement with badges are right now standing in our datacenter and/or NOC serving a court order".

At times like this it's worth remembering that message boards strongly favor whatever narrative is going to be most fun and exciting to talk about.

I heard the CEO of Lets Encrypt, Warren Buffet, accidentally started a fire while charging his e-unicycle in the data centre and that knocked out the server that issues the certificates. They've got a backup, but it's in a safe only two people have keys to; one keyholder, Anne Hathaway, is at a parrot show in Singapore this week and her flight back is delayed due to fuel shortages. The other keyholder, Henry Kissinger, it turns out has been dead for 3 years.

I sincerely hope it's the most mundane and least spectacular explanation possible, just saying from my point above that compliance has a very wide range of possible meanings and interpretations (also depending on the background/career POV of the reader), until the incident is further explained..

In that sense, prepare yourself to be bored.

Federal law enforcement in your DC isn't something you'd call a "compliance" issue, that's not what that term means. Yes it's various derivatives of the English word "comply", but this is a field of well-defined verbiage, and that ain't it. Compliance means they failed (or are being questioned) about following particular practices that they have agreed to, nothing else really.

NB: "legal compliance" is another term. So is "{legal,lawful} enforcement"


Compliance here means compliance with the CA/B Forum Baseline Requirements (and similar other policies), which cover a lot of operational obligations, from character encoding to physical security.

Considering the open source nature of Letsencrypt, I wonder what the barriers/costs would be (theoretically) to a wealthy benefactor who wanted to duplicate its server side infrastructure and a core staffing level of persons, and fund a "parallel" equally trusted, alternative entity with a solid governing board. Same general idea how Acton funded the Signal foundation.

Somewhere that none of the physical infrastructure/hosting environment overlapped with existing Letsencrypt stuff so that the failure of one entity would have zero blast radius affecting the other.

I know there's a long and complicated process to go through to become a trusted root CA and get your CA public cert auto-installed in every OS and browser trust store. Indeed in the early days of letsencrypt I recall their root CA certs were signed by other older root CAs.


A lot of Let’s Encrypt is not the software but a bunch of auditing and process that ensure compliance and make it legible to the required auditors.

I understand there's probably a big thorny problem of duplicating the corporate process/policies on the human level that ensure compliance, but is the back-end software pipelining stuff to CT logs not also something that can be replicated? Or is it not part of the server side stuff which has been open sourced?

https://letsencrypt.org/docs/ct-logs/


Google has their own free ACME endpoint: https://pki.goog/

They implied it used a GCP account. It would require to give Google personal information, a phone number, and automatic payment permission. And Google not disable your account because your spouse uploaded images for your child's doctor.

ZeroSSL should also be drop in

ZeroSSL advertised for free 3 certificates with no multiple names or wild cards. The next plan was $180 yearly.

For people who don't think they have an immediate use for either meshtastic or meshcore, it's fine to disregard it and just dig in further into the capabilities of the LoRA radios used. They can be used fairly effectively for some very long reach serial bridge connections for telemetry and command/control of DIY IOT things and similar.

LoRA is also used extensively for hobby size UAV handheld controller/ground control station to air unit controls, and in its narrower channel sizes can be very long range. The well known TBS crossfire serial bridge radio system which predates LoRA by a number of years uses a chipset that is sort of an ancestor of current-gen LoRA stuff.


Considering that a 'base' raspbian type install can be something like 160MB of RAM used with openssh running and a lot of other launched-from-systemd daemons in the background, that leaves plenty of RAM available for a stock apache2 or nginx setup with TLS. No it won't be able to serve a ton of simultaneous requests, but I'm in agreement with the other comments here that doing purely port 80/http and putting it behind a secondary TLS proxy is not really "serving the website" from the raspberry pi.

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

Search: