Wait till you learn about companies replacing the opensource parts of their stack/products with something an AI coding agent produced. They do this to get rid of all the burden that comes with using opensource like risking to get sued if they dont ship the source code according to the licence. This is why sboms are a hot topic right now. Also coding agents are now good and cheep enough to do this.

Nice.

I just use org-mode + lots of recurring tasks.

Like car.org has monthly tasks for check fluids, clean inside, clean outside. In April and October theres a task to remind me to change tires and as I'm German a task to remind me yearly to check the first aid kit (you get a fine if its expired and they spot it when they stop you).

So, almost every appliance has its org-file with routines. Same for me and my family, check vaccinations, see the dentist ...

So, if you are already using org, theres no need for an additional tool. Plus, its all text, just throw it in your git. Also, there's tools like beorg to have your org on your iPhone.

Pet food and clothes, quite some portfolio to add a company like Threema

Got 10 hits. 8 of the email adressess were invalid like user1@ and user2@ while user@ would be the valid one

Curious question, this case is pure PP. What about shilding EMV emissions? Is this "legal" to run a pc open like that?

It varies, but in many places you couldn't sell a device without proper shielding, but unless you are causing disruption to a public service or safety equipment there is nothing that stops a person owning and running one. Just think of the world full of rPi units, other SBCs, and other PCs, running completely caseless or in cases without much/any thought towards EMC shielding - it obviously isn't a problem, or it would be a big problem.

Most rPi units and similar are fine as they can be argued to be sold as parts rather than devices just like any other motherboard¹. The Pi400 presumably gets away with it, as something this is conspicuously sold as a device not a part, because that chonky heatsink² is enough to disrupt any errant EM fields outside the ranges that it should be emitting (those around 2.4GHz and 5GHz).

There are many grey areas, and indeed those where the letter of the regs is broken but not enforced. To cut a long story short wrt “Is this "legal" to run a pc open like that?”: yes running a PC in a case like that with no extra shielding is legal pretty much everywhere, though selling a complete PC with a case like that probably breaks regs and maybe even laws.

----

[1] putting the responsibility with the purchaser, where it isn't enforced unless it is a problem (I chose not to shield my TV-box Pi4, not the company, and it isn't putting enough junk out to disrupt anyone else's anything else)

[2] everything else about the case is plastic

Yes because this is just a case, if you build a product in it and sell it then you need to meet EMC regulations (EC marking in europe).

I'm not sure what customers Synology is targeting. Small office/home office (SoHo) was their original market, but these customers won't be willing to pay high prices per drive. Medium-sized businesses? They mostly move their infrastructure to the cloud, which probably leads to low sales volumes. Plus, they're very price-sensitive too. Large enterprises and corporations? This is the domain of established providers like NetApp. Synology might dream about the high prices that these major storage vendors can charge, but this market is difficult to enter without years and years and years of proven reliability in hardware and service.

I don't think this will work the way Synology imagines it.

naming things - always the easy part of the setup

sure you can, take your business elsewhere

It’s a minor (but annoying) issue to make the reason to migrate 1,500 users. Who many of which would still need licenses for Excel anyway.

Microsoft being annoying and frustrating and having so many issues is why I have a well paying job in IT.

that sounds like the lump of labor fallacy. there's plenty of things to do in IT besides babysitting hypocrite hypergiants.

I hear you, but some people just want an easy high-paying job where they essentially work a few hours a week. Not everyone wants to fold proteins.

Because I get to make those calls, not people two or three or four levels above me.

Isn't most of their stuff open source?

It is, but if you're running on different hardware than us, you'd have to do a bunch of porting. Buying a solution would be a lot simpler, as we'd have already done the porting.

Have you thought of building an affordable small-scale product for home labs and maybe SMBs? Even if that line didn't turn a profit, it could function as a loss leader in getting engineers and consultants familiar with Oxide, and an opportunity to experiment with (and ultimately evangelize) your tech stack without needing to already have an enterprise-scale use case.

In general, we love the love we get from homelab folks, but the issue is that the current thesis of our designs is "take advantage of the scale of building at the full-rack level."

We really can't afford to do loss leaders before we have more of a business. It's already difficult enough to build a company like this, and that's with making money off of sales. I fully agree that in general, this idea completely makes sense, but you can only really employ it once you have a business to be able to absorb those losses. Right now, building and selling the current product takes up 110% of our time.

I respect that, and I hope you get to that point! As a tech leader in a organization that currently falls short of the scale we'd need to justify Oxide products, I'm hoping that day comes soon.

We're getting to the point where people are building large clusters of Raspberry Pis and the like for hobbyist projects, so I hope that within a few years, the concept of "full-rack level" can encompass hardware with hundreds of nodes small and cheap enough to be packed into a "rack" that still fits under a desk and sells for a couple grand.

In the meantime, I'll guess I'll have to settle for exploring your code and listening to your podcast!

As long as you have enterprise products like zscaler, that do not support IPv6. Or switches and routers that are broken in different ways with every update. Userproperties in Active Directory that are to short to insert an IPv6 address.

Why should any enterprise company move to it? Why should any enterprise (at least) double the cost by having to support two protocols when most problems can be solved by various types of NAT?

> As long as you have enterprise products like zscaler, that do not support IPv6

ZScaler is a burning piece of privacy-violating garbage that as a developer rather get rid of than have.

Nice for non-IT collegues who were previously protected by the corporate proxy server while working in the office, now work at home or other places, and are prone to scamming and visiting forbidden [by the employer] sites.

As a developer a system-wide MITM SSL-decrypting proxy server is a major pain in the ass. Every runtime of developer tools, python, Node, .NET, Docker, Linux (WSL) flavors, etc have their own way to trust root certificates, and as a web developer you do tend to touch a lot of different tools. Secondly, when you do a bit of devops, you can't even check basic things like checking if a website has the correct (valid) SSL certificate without RDP-ing to some server which doesn't have ZScaler installed.

Sorry for my rant. But I'm not allowed to disable ZScaler - but am forced to live with it.