clan

Other players as well:

https://github.com/helloSystem/hello

I know as well that they are often impressively quick to respond.

But it is not the initial setup I am really worried about. It is those fan meet fecies moments. Being able to respond to a situation instantly. Mfsbsd was a godsend.

Trying to fix problems on one OSis from a different OS is a much harder issue. Especially under pressure.

I would much rather have seen they added OpenBSD to their PXE environment. Just the vanilla stuff - no fancy optimizations.

Nice write-up. It should really not be that hard but unfortunately it is. And it is getting worse.

It made me sad to see that Hetzner had discontinued the FreeBSD rescue system. But it seems to be correct: https://community.hetzner.com/tutorials/freebsd-openzfs-via-...

How much did it really cost them to have the mfsbsd image available?

Yes, according to the archived Rust implmentation[1] which in turn refers you to either clap[2] or structopt[3]. Other implmentations does not mention this but those I looked at had not been touched for years. Either very stable or unmaintained. Unfortunately the latter according to the Rust crate. The dotNet implmentation had a very small version bump in the dependencies but the rest of the project does not seem to have been touched the past 2 years.

[1] https://github.com/docopt/docopt.rs

[2] https://docs.rs/clap/latest/clap/

[3] https://docs.rs/structopt/latest/structopt/

Secure is not a binary term.

If sjunet is managed as a number of interconnected airgapped networks then I for sure find that more secure than a Internet connected network. The attacker surely still have vectors in but whole classes of common attacks are mitigated.

Even if it is just "one big intranet" it is still better than one big intranet with one really good ((zero) trust me bro!) firewall to the Internet.

Various levels of zero trust principles can easily be applied within sjunet. That makes it better in my eyes.

For critical infrastructure I find this an important step. In the end security relies on us stupid humans. And it is easier to manage an airgap. It is the number of things we do afterwards to bypass it which is the problem.

The idea of an Intranet is still sound. But private does not mean secure. It is just a security layer. The next layer is if you run it fully open. Are the rooms locked? Do you require 802.11X certificates for connectivity? Are all ports open for all clients/hosts. Do you have a sensible policy for you host configuration? Have you segmented the network even further? Etc. Etc.

So your point is still valid for sure! You should secure it like on the public Internet aka a hostile environment. That is the important takeaway.

My point is that is should no be used as an argument against a private network. For large critical infrastructure such as hospitals it makes good sense. It is an added layer for the attacker to overcome - it is not security theater. For some the hassle might not be worth the while but that is then the trade off as with all forms of security.

It ain't binary but discussion often end up like that. Done right it can be additive. Done wrong it just adds pain and agony.

We all dread the security theatre. I boldly claim this aint't it.

I have only seen it as harassment mainly on news sites. "We cannot play this video" or the all too common Twitter or Instagram embeddings. On one hand I know I waste my time but I am such a weirdo I make "my stand" by always declining. Are the consent forms too broken or conveluted I usually leave the site. But we are in the minority and all of us are probably HN users. And my gut feeling is that on HN we are still a small minority. I think the more common approach here is auto accept extensions.

And 80% off on GOG: https://www.gog.com/game/chris_sawyers_locomotion

Yet, Ladybird.dev is happening.

And you need to keep the bits on current technology. That is the real gambit.

So your NAS idea is probably the best with the caveat at your need to upgrade it regularly as well.

Compare it to a floppy disc from your grandparents. Not that bad for 3,5"? How about 5,25"? No? Then 8". These are now hard to come by. And this is just in the time span of 30-50 years.

The best bulk storage format was actually available early on and very shelf stable if treated reasonably: Paper tape. Low density and readers are hard to come by today.

Your primary point that our grandkids won't care is on point. We would drown if we keep everything. But the counter point would be that if we do not even try to preserve anything we would probably end up with nothing.

But for every average Joe who does not care we seem to have plenty data hoarders to make up for that.

They did. And if you have a newer drive it is already supported on your DVD or Blu-Ray. Can be read by all drives but requires a recent firmware to be able to write.

An example drive would be Asus BW-16D1X-U.

It is supported by the major drive manufacturers but it seem the media is only produced by CNC Magnetics or Mitsubishi Chemical. Sold by brands such as Verbatim or Ritek.

It is rated for 100+ years.

The variant is called M-Disc: https://en.m.wikipedia.org/wiki/M-DISC

Discs: https://www.verbatim.com/subcat/optical-media/m-disc/ https://www.ridata.com/M-DISC/eng/index.asp

Blu-ray license list: https://blu-raydisc.info/licensee-list/discmanuid-licenseeli...

The hard part will actually be to get hardware in 100 years which can read this. So it will not be write and forget. But reasonable shelf life should at least be available.

I did. And I always hated the "until it is right" instructions.

A thermometer is a key tool which was not used when I grew up. I even commented to an aunt that my mother was a better cook because she did not use one for her roast. I have since learned my lesson.

It is a golden kitchen tool. You can up your baking game by using it. Understand proofing temperatures and time. And now our Rye bread comes out perfectly every time as we know to pull it at 97 C.

Cooking is not hard. But good cooking can be achieved without years of learned intuition.

If you want to go one step further get an induction stovetop. One of the praises for those would be that many better ones have temperature sensors. It is rarely advertised but if you get one with "auto" cooking it has a sensor which will turn down to your desired setting when boiling. That class of device would then often have a "keep warm" function. Those are typically set around 70 C. On mine i can choose heat levels I, II and III besides the regular adjustment. III I can set and forget for a simmer. Somewhere deep down in the manual I think it said 80-90 C. I can only find a later version of the manual online which only have a "keep warm".

Just to say that you can get nice things for your home without going the route of the Breville Control Freak.

In practice I often find it easier to use the oven.

For other who is new to proper simmering/braising have a look at: https://www.ricardocuisine.com/en/articles/food-chemistry/64...

I say this with great care as I do not want to launch a flamewar.

If you do not consider Linux with namespaces an OS (because of fragmented userland): Would you then consider FreeBSD with jails or Solaris with zones for fully fledged?

If you still consider those flawed (maybe because thet do not force you into jails/zones) should we at least no consider OS/390 or z/OS as proper operating systems to that/your (not meant inflamatory!) standard?

Yes. Though you do not mention them directly DOS and Windows has ruled the world for years and they opened the door for the nasties. But they were not all there was - only the popular/easy choice. Everything is a trade off.

That is a really dark pattern which I personally hate.

Sucker me in and then raise the barrier. It is on the same level as those "create free account" but nothing is actually free except for the account creation process.

We have word for this: Demos. It could be a "free demo" account or an "account free" demo. Two different but easily understandable things which clearly communicates intent and value. Nothing Sneaky and no hiding weasels.

It just triggered me that this marketing funneling newspeak actually has become commonplace and generally accepted.

Change the wording to "launch demo (recording)" and communicate it clearly will make this grumpy fart happy. And yes: There is a subtle difference and therein lies the darkness.

The video and ticker are however great ideas as-is without me complaining.

Really horrible UX.

You send a mail to an address - and then need to click "View Results". This sends you to "https://dkimvalidator.com/results" with a message of "I haven't received an email recently to....".

They do catch Ctrl-F5 keypress for reload. But if you just go to the URL bar and press enter you are returned to the front page with a new ID. You can paste the old address and then get the results but not a nice experience.

So. Nice domain name and points for effort. But a far cry away from https://www.learndmarc.com/ and the old dog https://www.mail-tester.com/ which both are really great. Less battery included but MxToolbox Supertool is still preferable to this (https://mxtoolbox.com/SuperTool.aspx).

Even shivdeepaks weekend project (https://dmarcverified.com) is more straight-forward and to the point.

So not to be a party pooper but as this was not a "Show HN" this is not really worth your time.

Years ago I worked support at an ISP who had usernames which was a 12 digit number. Most regular users and 1st level support do no know the NATO phonetic alphabet. An easy trick is trick is then to read back the number for confirmation but use another grouping of digits. Most users read 1 digit at a time so I would read back 2. One-Two becomes twelve. If they used 2 digits I would for ease use 3 rather then 1. This is a very easy way to do a fake "checksumming" regular people.

Tangent: All number started with 12 which in effect made them 10 digits. They worked together with a banking system and the bank folks thought 10 digits was not secure enough so they complied and added 12 in front of everything.

I agree and get your point.

But localsend has worked well for me. Yes, it requires an app but if we could get vendors to bundle that rather than a boatload of bloatware.

I know that it would be to optimistic to hope for Google.

See https://localsend.org/

Spread the word.

What I find weirder is that people chase Ozempic even though they have introduced Wegovy. Which is basically the same drug but without glycemic control and hence more suited for non-diabetics. Both are Semaglutides and Wegovy directly targets weight loss.

The link is correct.

The simple arrows you prefer are there as well. But the overhead signs are important when there is a lot of traffic as you will see the road markings too late.

You have to look at the satellite image to see the unusual (around here) parts: Traffic lights, stopping lines inside the roundabout and the left turn lane within.

I used to agree. But people are creatures of habits. There is a well-known "large" roundabout near Copenhagen often called the IKEA roundabout. Obviously next to IKEA but still so known that it has a "popular" name. It has large overhead signs. On road signage. Traffic and street lights. The overhead signs show that you should take the left most lane to go left. Two middle lanes for straight ahead. And a breakout lane to the right which goes right. It is all very easy to understand and logical. But the number of lanes and the fact it is so busy it is regulated with traffic lights makes people very uncomfortable. As I find it very logical and easy to navigate I have come to my own conclusion that it is because this type of roundabout is unusual and uncommon around here. You will notice peoples lizard brain set in. They are scared they cannot exit so they clearly choose the outer-most of the 2 straight ahead lanes. And dangerous situations when people who needs to go left take the outer lane because you can "always" do that in a roundabout (but not here!). And for further anecdotal evidence this has come up several times in conversations and people have stated they do not like it.

You can see it here: https://maps.app.goo.gl/jr39hNie4d9fennq7

Nor in Danish.

Works reasonably well on Windows: https://support.microsoft.com/en-us/windows/multiple-desktop...

I can never remember the (easy) shortcuts so this is helpful: https://learn.microsoft.com/da-dk/windows/powertoys/shortcut...

From PowerToys: https://github.com/microsoft/PowerToys

(Which also have the (in this context) useful FancyZones)

I see your point but is firmly on "team window". I feel the scalability problem is better solved with multiple desktops. My work is rarely in one application so grouping based on work context is a better fit for me.

This can work really well even on MS Windows. It is unfortunately not default nor obvious to the regular user. But what comes in the box sprinkled with a PowerToy is rather good.

That is the paradigm I strongly prefer.

I have always liked the tight integration on Mac (such as printing - no driver fuss) and the UI looks really sleek. But the UX of the window/app handling does not sit well with me. Not for the lack of trying.

My first GUI was GEM Desktop which might have damaged me for life.

Try with buttermilk. The tartness does good things. If buttermilk is not readily available kefir can be used in a pinch. As it is thinner than whole milk I would skip the water.

Can you recommend a good book on the subject? Especially one which includes the transitioning pitfalls. I have been living through it all and can get a little confused as to what is status quo. First I heard that SLAAC was great. Then came DHCPv6 and some complained it was an ill concieved bandaid. Now I was under the impression that link local addresses would make my day easier but not you indicate that ULAs are the way to go.

All of this is made much harder by ISPs actively fighting IPv6 adoption. They have the usual moat babble that users do not request it. But in my case they even blocked /protocol/ 40. This was not documented anywhere. Imagine the layers of support I had to work through. Imagine working with new technology and be sure enough that you have exhausted all other possibilities. So learning practical IPv6 has been an uphill struggle for me. Years ago I had a SixXS tunnel going before major adoption took off. Now I am living in another place and wanted to look at it seriously. SixXS was no more so I went with HE. To my dismay dark corners of the Internet have abused these offerings so I have my tunnel disabled most of the time as it gives too much grief. And I have even worked in operations at a large ISP in the 90s. Adoption is not easy even for the willing.

But the reason? No one here seems to mention it: Money. There are no technical excuses left. But it is surely a nice moat.

Sorry for the rant! A good up to date book recommendation would be appreciated :-)

Poul-Henning Kamp wrote a personal memorial "RIP: Dave Mills" in danish: https://www.version2.dk/holdning/rip-dave-mills

Read it in english with Google Translate: https://www-version2-dk.translate.goog/holdning/rip-dave-mil...

Quote of the last paragraphs:

Dave accomplished many things in life, he started his career with the "Bandits of the Beltway" as they were called in "MilssSpeak" and there were things he was still not allowed to talk about, for example the guidance computer of the Minuteman-1 missiles, things no one wanted to hear on, e.g. 16-pulse Tactical Loran-C and things that are so big that they are hard to grasp: If Vint Cerf was the "father of the internet" Dave Mills was its grandfather.

Somewhere in the middle of that long list should also be said that he kept a single father and two young children sane and on track, on the opposite side of the globe.

Glory be to his memory!

Would it not be a little blasé to simple describe it as "evacuation happened as per procedure". Even if we sprinkle "successfully" into the sentence?

While I am not a religious person and hence does not care for some of the connotation in the word - I find it hard to find a more descriptive word in this case.

Neither do I believe any magic happens when all the stars align. But I do like it as a poetic rewrite of "simple luck".

So I understand your beef but you offer no alternative.

Best case outcome in a though situation does not have the same ring to it.

You seem to be in the "read the code" camp. I am not.

Rather than using plain language and reason about dependencies, limitations, workarounds and more or less informed choices you need to infer this from the Docker file. Pray that they have left even a single little comment regarding non obvious issues.

Akin to saying everything is documented in the Makefile. Why not a quick glance a main() to see if we parse any args.

You can give people step by step instructions on where to go. But you empower them with a map.

Documentation is hard. Quality documentation even harder. A dockerfile is a very poor substitution for me.

I do not mind projects who prefer Docker and they get all my love and appreciation if they document the manual building steps. And I am totally fine by them telling me I should probably not do that. But I am seeing more projects skipping this and instead spend effort and time on using and debugging with Docker.

But I am old and my beard is getting grey. I have learned to fear the programmer who tells me to read the code to understand the system. I have been told that it is concise and is good for velocity. Not everything old is good and we should move on. I for one miss the days when documentation was considered a priority.

Virtual Machines (VMs) is 1960's technology. Started out on the mainframes.

x86 virtualization came along in the 1990's. VMware Desktop everybody knows today was released around 1999. Other players have been around.

This is the same year jails was introduced with FreeBSD 4.

The funny thing is that jails are often referenced as "virtualization without the overhead".

Jails are really fast as it is the same shared kernel. Hardware VMs have additional security advantage as a guest kernel vulnerability will (normally) not affect ofter guests. But it comes at a cost.

Personally I find the FreeBSD package approach more elegant. We have the "pkg" package manager as standard on the system. If you want to install into a jail you simply add the -j flag.

There has not been a lot of documentation on how to do service jails. Maybe because a full jail (with a full and reasonably sized OS) is so trivial to setup.

But there is no denying that Docker have had great marketing and a good use case.

I do however think the real reason no matter how much of a FreeBSD Jail or Solaris Zones fan boy you are - you know that Linux is the elephant in the room. That brand name alone without arguing distributions.

Linux already had a huge market and mindshare compared to FreeBSD or Solaris. And when Linux got CGroups you had (within reason) feature parity. For anyone who are not daily distro switchers changing your base OS is no minor feat. So even if CGroups was not perfect the incentive to switch is not huge.

But it does make me sad that Docker has become so prevalent that a Docker image is the only way some projects make releases. All too commonly without documenting the build steps. Do not be so hard on your posix friends, please!