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

Can't stress this enough, especially the hyper heat models: caulked compressors (very high pressure) with phase control injector, not only it runs at very low temps but the performance and COP is linear down to -15C.

Insulation matters more with heat pumps, especially ceiling for cold starts (for descending heat build up from the top) as low temp air heating is not as radiative as IR from traditional heating appliances, or the conventional oil radiators that move air passively.

CO² heat pumps are less impacted due to the much higher air temperature but they are very uncommon for split system (dangerous), and usually used for water heating in AIO unit in a basement.

Had a house electrical failure recently with solar, ran one 18k BTU unit for 60m² on a tiny 5hp Diesel generator sipping 0.4L/hr. (2-4L for Diesel burner in comparison)

These models need proper installation as they use a synthetic proprietary lubricant compared to the commonly used mineral oil, moisture or contamination during tubing installation is a big deal for twin rotary compressors which may reduce service life.


This is the first time I've heard that CO2 heat pumps might be dangerous. Can you elaborate on why that is?


I wonder if this benefits people with Arthritis with the little movements.


I feel like this would be worse tbh. Not enough finger movement and pushing the fingers outwards doesn’t seem like a great idea long term.

I just don’t get the fascination for these minimal type keyboards, have tried a few and they frustrate the heck out of me.


A relative of mine with Arthritis prefers less finger movement. You generalized minimal type keyboards.


They are novel. We have had the same basic design for a century. People like seeing new concepts.


QUIC is UDP, and TCP does not use CCA in userspace.


QUIC absolutely uses congestion control. See section 6 here https://tools.ietf.org/id/draft-ietf-quic-recovery-26.html


No denying in that.


QUIC does run in user space, and also uses congestion controllers running inside the QUIC stack, in user space.

(I work on a QUIC implementation in Rust.)


QUIC is a protocol... "...CCA in userspace" CCA stands for congestion control algorithm.


Agreed, although it differs vastly between models, I'd say it's rather the opposite if you opt for passive 3d party heatsinks(chassis) which are plenty for Intel's NUC, even 80W TDP models (Iris Pro). Passive cooling for desktops is way more complicated. I've been using Akasa for my Skull canyon for years for my dead silent setup.


Akasa's fanless Intel NUC cases are excellent. Hopefully they will create a fanless case for Ryzen NUCs, or generalize an Intel fanless case to support multiple port layouts.


"Off-Topic: Most stories about politics, or crime, or sports, unless they're evidence of some interesting new phenomenon. Videos of pratfalls or disasters, or cute animal pictures. If they'd cover it on TV news, it's probably off-topic."


Almost the entire comments mix "crypto" with Bitcoin or "all cryptos are the same" which is factually false. Please explain how different it is in comparison, the thread is flooded with baseless claims. This is analogous to placing your money under the bed vs. in a bank vault, they're both unsafe technically, but the difference is vast.


Approach and hypocrisy matters. Apple did boast about privacy and security many times before...


Have you tried the multi tcp feature? It should solve the bandwidth issue with Amsterdam servers (torrenting allowed). Yes from ntop regarding nDPI.


Speedify seems to be capable of doing packet aggregation, load balancing, and redundancy simultaneously per each connection flow. Any alternative? (preferably open or self-hosted)



Good suggestions but these do not offer redundancy/seamless-failover nor load balancing in case one of the links is poor (only failover), needs excellent and fast connections (the entire thing crumbles, BLEST barely helps), at this point a load balancer with sticky session is better. Very little packetloss with OMR is unusable, and MLVPN needs equal homogeneous uplinks (at least in latency), ubond fork needs manual tuning. Overthebox = OMR, infact OMR is a fork. MPTCP requires excellent connections, unless redundant mode is enabled, no aggregation. Overthebox also switched to Glorytun UDP due to the failover issues, but the performance is poor, and upload is not aggregated.

Speedify/Riverbed($$$) can do bonding, load balancing, and redundancy at the same time per each flow going to the VPN, it also does packet steering if one link goes down in aggregation mode. If parallel downloads are detected, or flows with the same source, they are load balanced instead of aggregation, provides much better performance and no buffer bloat. Uses DPI to detect sensitive connections and routes them to the redundant channel. It also stops bonding and sticks to load balancing if the majority of the uplinks are bad. e.g:

ISP1 Good: LB + aggregation channel with 2 + redundant channel / ISP2 Good: LB + aggregation channel with 1 + redundant channel / ISP3 Bad: LB + redundant channel

or

ISP1 Good: LB + redundant channel / ISP2 Bad: LB + redundant channel

"Bad" as very high latency difference or/and packet loss. Packet aggregation is used only when a single TCP download session is detected. LB is preferred.

It solves all the issues when combining different types of internet which deemed to be impossible or poor before.


> I thought everybody felt that way.

Does it incur any impact on your life? Was it a thought or a challenge?


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

Search: