I would argue moving SSH to a non-standard port is security, but it's a different kind. By reducing the noise in logs, it reduces the workload on the human or agent reviewing the logs. So, you can detect an attack in progress or respond to an attack before it gets out of hand. With SSH on a standard port, the harmful malicious logs can blend in with the annoying malicious logs much better.
> By reducing the noise in logs, it reduces the workload on the human or agent reviewing the logs. So, you can detect an attack in progress or respond to an attack before it gets out of hand. With SSH on a standard port, the harmful malicious logs can blend in with the annoying malicious logs much better.
Advice like this should be at the top of the chapter in the textbook that teaches young sysmonkeys how to admin a box securely. Well stated.
I can't think of anything that doesn't just work in that it's broken in some way. There are things that are different. I've been using MicroOS with Plasma for at least 4 years now on my personal machine and my work laptop. At some point they changed the name to Kalpa. There were some times in there where things were broken and it needed to roll back and pause automatic updates for a few days, but otherwise it functions just as expected.
A couple of annoyances exist. For example IDEs want to use the system's shell, so you have to make a custom entry to use your distrobox. Tools like python, node, tofu, etc are installed in a distrobox and then exported with `distrobox-export -b $(which $BINARY)` so that you can call them from the IDE.
For me, it's worth those few rough edges. When I install an OS for non-technical people who just need a web browser, I install Kalpa. It looks close enough to Windows to be easy to use, and it's never broken in a way I can't explain over the phone or a text how to fix.
It even passed the wife test in our house. It took a few years of marriage to convince her that her laptop shouldn't take 30 minutes to boot and open Chrome. She let me switch her over to Kalpa (it may have still been called MicroOS Desktop then) a few years back. That old laptop is still kicking and fast enough for her needs. Had she stuck with Windows, it'd be a brick now because of the requirements for upgrading to W10 and 11.
Bouncing signals off of the ionosphere is most definitely not an option here. The bandwidth of the signals that Starlink needs in order to provide service are far wider than the range of frequencies that bounce off any layer of the ionosphere. If you could get a 10GHz signal to bounce off of the F layer, you'd have a lot of very excited amateur radio operators who would start using that instead of the moon as their reflector.
The cookie consent banner here is the ultimate dark pattern. No deny all option, and the options are impossible to determine. Is the first toggle to turn on or off? I assume on, but that's not labelled anywhere. Based on convention, I'd assume to the right is enabled, but it's entirely against their interests to have it default to off.
> but it's entirely against their interests to have it default to off.
It's been a long while since I've seen a cookie banner, but I always understood the law as that the user has to explicitly do something to opt-in which is why the customize options default to off and the "accept all" button is usually made the prevalent option instead. Not sure displaying non-essentials all default to on would really be in compliance, but to be honest I'm not sure anyone really cares enough about all of this anyways or the law would have been amended
by now to block this kind of crap.
Just for fun I disabled my blocker to see the atrocity. They hid the "real" customize your choice in the bottom left, and (if you can ever find it) it's one of the better. The buttons do seem to be left is disabled/right is enabled on both pages. An impressive amount of work went into making this one as complex and confusing as can be, they should enter a competition!
Almost the same situation here. The only thing I used was Kafka, and I only used that to allow horizontal scaling of Argo Events sensors. Moved over to jetstream, saved a bunch of compute and memory, and realized I didn't need to scale Argo's sensors horizontally. Really, Bitnami's decision made my life easier in the end.
The author's complaints about the various solutions hit home. My wife and I tried a bunch of solutions for shared tasks and lists. Finally I found vikunja, put it on my home cluster, and it's been a game changer. We never run out of milk due to a lack of communication, and I have no excuse to forget the chore she asked me to get around to last week.
There really is a sweet spot between helping productivity and overcomplicating life, and most of these applications go for the latter. Glad we finally found something that works for us. I'm just sharing here hoping it'll help someone else.
I was thinking the same. When a person starts repeating what I said back to me, especially if it's nothing outrageous, it feels like I'm being interrogated. My response is to deny. E.g.:
> Me: Last week I went to the beach.
> Conversational adversary: You went to the beach last week?
> Me: No.
Maybe this explains why I don't have many friends.
reply