

The cruelty is the point. Just keep repeating that and you’ll understand most of the decisions.


The cruelty is the point. Just keep repeating that and you’ll understand most of the decisions.


And now I remembered we’ve got over 3 more years of this garbage to fight through.


Not even close to that third comma, amateur.


Not already fascist enough


I didn’t say it was impossible, I said it was hard. Bigger radiators absorb more heat when exposed to the sun. One of the problems becomes keeping the solar panels exposed to sunlight while keeping the radiators out of it. Putting them behind the solar panels might work, but they have to be smaller than the solar panels and any energy the solar panels don’t convert to electricity will be re-radiated as heat and picked up by the radiators, requiring a larger size. You could put them on the 'back" side of the spacecraft, but that limits the size. As mentioned in another comment, you could position the spacecraft in geostationary orbit on the terminator, but then reaction mass requirements for station keeping and data signal latency go way up. It’s a problem that has been worked around by people much smarter than me, but a lot of work went into figuring it out.


Space isn’t cold, it’s nothing. It’s a vacuum and vacuum is terrible at heat transfer by convection. It’s why thermos bottles have a vacuum layer to prevent heat transfer. You can try to lose some heat by radiant cooling, but that’s slow and if you’re using solar for power then any radiators become heat sinks picking up more heat from the sun. Then there’s conduction, and again, there’s really nowhere to conduct any heat to, what with the large distance between objects and the vacuum and all. Thermal management in space is kind of a hard problem.


Video generation, copyright matching, CSAM detection, those are just the first few that pop into my head.


Because that’s literally the minimum upload speed they can give you. If you’re pulling down data at 1.2Gbps, you’ll be sending back 40Mbps in response traffic. If they could give you less, they would.


They’re likely imitating his posture. It serves the dual purpose of signaling their sycophantic loyalty and normalizes the absurd stance to the rest of the world.


Maybe something like this. https://www.amazon.com/gp/aw/d/B0F93N2H36?psc=1


In Z-waveJS my Kwikset locks have a User Code V1 setting. Under that is all of the user code slots. The interface isn’t very pretty or intuitive, but it works well for adding, removing, enabling and disabling the codes.


And they only have to win once, we have to fight and win every time they introduce a new variant. Its exhausting.


What about mounting it sideways?


Rheeme Econet devices do this. They have an app to control them, but there’s also a diagnostic port that exposes everything in the app and a lot more. There’s an esp32 project that connects to the port and brings all of that into Home Assistant, no app or wifi needed.


Sounds like it’s time to take to the seas me bucko.


A layered defense is always best. Nothing is 100%, but knowing your threat model will help define how far you have to go and how many layers you want in the way. Defending against State level actors looks different than swatting the constant low effort bot traffic. You’re right, if a bad actor gets root on your machine, all security is forfeit. The goal is to minimize that possibility by keeping applications and packages updated and only allowing necessary connections to the machine. You mentioned wireguard or tail scale. Set that up first. Then set up the host firewall to only allow outbound traffic onto the VPN to the required ports and endpoints on the LAN. If the VPS isn’t hosting any public facing services, disable all traffic except the VPN connection from and to the public Internet both on the cloud provider’s firewall and the host firewall. If it is hosting publicly accessible services then use tools like fail2ban and crowdsec to identify and block problem IPs.


Firewall rules on outbound traffic from the VPS to the LAN would do it. Allow traffic to the hosts and ports that the VPS needs to reach and block everything else.


That’s true, from a certain point of view. What they actually did was give everyone a common target. We still get everything compressed and limited into a flat line, just now we don’t have to adjust the volume on our stereo between songs.


The Happening
It was just a plane or something