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

They might not be doing it on purpose, remember that microsoft windows "take a screenshot every few seconds and send it to an llm" thing?


There are aspects about cultures which can be fascinating, not (only) because they are foreign and new, but because dedicated and intelligent people have been improving them for generations, centuries even. I have a friend who is from Korea and who is a wood worker, and we have compared the different approaches to what, in the end, solves the same problems. Not everything can be incorporated into the other way of doing things, but I have found it eye-opening. My brain still tries to find ways, comparing, like a constant ping. Maybe one needs to dedicate 100% to the new way for a while to understand it fully before a genius brain would be able to find the spark how to meld both methods into a single improved Way of Doing Things (tm).

How would you implement no-downtime hot swap with only one item?

By implementing hot-swap into the one item? Am I missing something in this question?

Executing hardware hot-swap typically means telling the system that a component is going down. Then the system moves those resources to the other component to gracefully allow you to remove it without a restart.

Like it's not a case where you just yank out a CPU as you like as though it were a spindle in a RAID-6 array. Especially if there's only one CPU. The state machine can't maintain state if the only component that tracks and maintains state goes missing.


For three generations, unless you watch re-education videos.


The Android build is a re-branded (and some might say, crippled) K-9 Mail, which AFAIR did not support NNTP. Adding it might be more work than they are willing to do.


Have you looked into enabling ssh keep alive/server alive?


From what I've read, TCPKeepAlive can be a good or a bad thing. On the one hand, sending a packet every now and then can dissuade a middle box from dropping the connection. On the other hand, if the connection is temporarily not working and would have started working again a few minutes later the attempt to send an unnecessary packet could cause the connection to break permanently when it wouldn't otherwise have broken. I suppose that next time I have a recurring problem I should try both.


Sharing in case this can help you in the future, this is what works for me with Termux in .ssh/config

  ServerAliveInterval 120
  ServerAliveCountMax 30
  TCPKeepAlive yes


Slight tangent: on top of that, I just read an article yesterday (which of course I can't find again right now) about how false automatic alarms from such cameras will incur a fee from the owners when the Police comes to check it out. It was from somewhere in Texas.


That's pretty common with any alarm system not just Ring. I know you get the first false alarm with a response for free. After that, fines/tickets are issued. It might have been 2 free can't remember as it's been a long time since the alarm was installed and info was provided. This was in Dallas specifically before I go painting with too broad of a brush. Even further back, I had an alarm system installed, but never paid for monitoring. They also warned about fines after too many false reports, and that was a tiny town waaaay outside of Dallas.


Nothing against that per se, false alarms should be kept in check.

If you have a system where, as I understand it, the main point is to check who is standing in front of your door, and that system now is one automatic update away from dipping into your bank account... How long until the police departments figure out that donations to a specific company could be very profitable?


It happens everywhere, not only in the middle east, not only with religion. People who crave control rise to the top, apply tight control to stay there, kill creativity in the process.


>People who crave control rise to the top, apply tight control to stay there, kill creativity in the process.

There is nothing about authoritarian regimes which prevents them from making scientific progress. See e.g. China, a society with substantial authoritarian features, a massive surveillance state and one party rule. At the same time they became one of the best manufacturers of everything in the world. Within a decade they built up a world class car industry, which both the US and the EU had to ban from competing.


A successful religion ties together so many valued things in people's minds, that it is very hard to fight the cultural dysfunctions it may promote, or has become entwined with.

Few other sources of dysfunction come with organized cultural generational reinforcement practices, systemic social respect and judgement, daily personal energy investment, family and friendship bonds, and both elite and grassroots level power classes that a religion can create. Not to mention the afterlife plans and ancestor reunions.

Note how reliably political polarization is associated with one or both sides weaving the sticky glue of religion into completely unrelated (and blatantly contradictory) partisan identities.


Monotheism has proven a devastatingly effective way to consolidate control in the ancient world through the medieval period.


And so, instead of having an open port for ssh, (ideally) with certificate-only authentication, optionally MFA, you trade it for an open port for tailscale/wireguard, handing over "all" your data to a company who is offering you a service for no monetary compensation.

Also, why do you think that it is better to not change the root password? It sounds like a very suspicious recommendation.


You're wrong.

You don't need to open any ports to use Tailscale, and its job is to a) get nodes to connect directly or b) shuttle jibber-jabber encrypted with nodes' private keys from point A to point B and back again through Tailscale-owned distributed servers. Tailscale only sees the traffic it needs and nothing else. It's free because it's "cost-effective" to run and because it can rely on word-of-mouth marketing because it solves a really complex problem in an elegant way, which makes enterprise customers want to pay for it.

Not changing the root password is correct, because at least on Ubuntu, it has been locked, meaning the only way to use it is through sudo or SSH keys (common during initial server setup). Setting a password for root and using su has no benefits over using sudo and comes with significant downsides, because it is unauditable.


Note that when the Swiss government says "handled by the state" it means it will usually be handled by the lowest-bidding consulting company.


Which needs to follow a mandate of properly handling user data (Switzerland has a law that's very close to GDPR) and properly respecting privacy as written in the proposal.

Not doing so is something the citizens can sue the government for - as opposed to US "private company can collect whatever, whenever and do whatever" (see credit ratings).


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

Search: