kj4ips

Note: Globus is no longer an interoperable gridftp server.

It now runs the control channels inside TLS ALPN with the string 'ftp', and rejects connections that are not from globus's cloud services, and requires one of two certificates, both of which globus controls.

It still uses gridftp under the hood, but they require a premium subscription to adjust turntables, or to view status as an administrator in the webui.

They also seem to be putting way more effort into their Compute and Flows offerings.

I often wonder what would have happened if rkt had been more successful.

Note that the MOTD is shown to users who are not authenticated. It's displayed in the client's server list, and is included in the same response that includes the current player count.

I'm still unsure how I feel about this, since M$ can reasonably say that they are providing services that the server (may) rely on (mainly yggdrasil), and they can set the terms for that. I assume they are treating a block from M$ provided servers, which would prevent authenticating users... However, if a server is in offline-mode, then their actions may be moot.

The call to implement MOTD compliance scanning is a bit uncalled for, especially since the notchian server doesn't implement this, and there's no consensus on what is permissible. TBH, I feel the first action should be for M$ to implement a client side filter, where it greeks things they consider objectionable in the MOTD, and giving the end-user the option to opt-out if they so desire.

I don't envy M$'s position here, since they get rap for the actions of others, and have to strike a balance between using their position as an infra provider to mitigate that, and minimizing their meddling with community servers. They assuredly want to avoid the reputation that roblox has gotten.

Discord and Steam have a user login flow that is very similar to what SQRL was aiming for, including a QR code alongside the username/password fields. While it's a closed implementation of a different system, I think of SQRL every time I use it.

I might be biased, I used the PPP Pam module on linux for years, until I moved to TOTP, and then eventually to pubkey-only.

The trend of slapping two STT 4-port hubs together is so common, that even name-brand hubs for reputable brands are often this, including the back feed issues. I purchased hubs form a solar-named company, and one that has a similar name to a large US department store, and they were cascaded 4port, STT, ganged overcurrent and switching.

I've started buying PCBAs from Ali, where the vendor advertises the exact chip set in use. It's often cheaper than domestic options.

Listings for assembled hubs (whether ali or domestic) almost never include information about the hub's actual characteristics, unless you're looking at a 300+ hub sold to audiophiles.

I'd really like a source for a true 7p hub, with MTT, proper power, per-port overcurrent and power switching, but I can't seem to find one, especially since vendors tend to rev b2c products with no notice (one of the name-brand ones I bought had been downcosted shortly before I bought it).

I like the idea behind ostree and bootc, but I feel that OCI (with tarlayers) is not a good fit. `repack` makes an absolute hash of things, and since the layers are logically packaged, they will have to be composed somehow, and then ostree becomes only slightly more useful than coreos's A/B usr.

OCI roughly assumes that layers will be laid out in some logical way, and that a given host will see opportunities to reuse across different instances, but with bootc, there will only ever be one instance.

OCI also assumes that individual layers are small enough that it is always worth pulling and unpacking a layer instead of some kind of authentication delta, which is great for a k8s cluster in a center, but not great for devices out on the edge, where you might want this kind of pseudo-immutable system even more.

I really want some standardized way for a manifest in OCI to say that "this content is also available in other format X here".

Note that the status on this is entered/not assigned, so it's in the works. However, the court may have required that they do so before proceeding.

The offending use does not have to be a 1:1 match to dilute.

(not a lawyer; not legal advice)

Trademarks are about recognizability, not about some objective similarity. There's no magic Levenshtein distance from a trademark.

However, they are also scoped to domains, so if there was some non-car business with such a name, they would also be entitled to the name, and the domains tend to be first-come first-serve in those kinds of cases.

Think of all the "Acme" or "A-1" companies that all have different products, and the general public doesn't have an issue conflating them.

(not a lawyer; not legal advice)

I agree pretty strongly. A translation layer like this is making an intentional trade: Giving up performance and HW alignment for less lead time and effort to make a proper port.

They have a Ubuntu derivative called DGX OS, that they use on their current lines.

It's my opinion that nvidia does good engineering at the nanometer scale, but it gets worse the larger it gets. They do a worse job at integrating the same aspeed BMC that (almost) everyone uses than SuperMicro does, and the version of Aptio they tend to ship has almost nothing available in setup. With the price of a DGX, I expect far better. (Insert obligatory bezel grumble here)

At least in most jurisdictions, the egress to a gathering area can __never__ be blocked, there is some provisions for delay on emergency exits, but those require NRTL certification, and are actually usually mechanical.

You might be able to lock it down during periods of limited occupancy, and you can rig it to an annoying alarm, and maybe try to identify the person, and ban them from future. It is possible to get variances for this, but you usually need to either be a medical or penal facility.

Two main reasons I can think of:

Most current BMC platforms are older than seL4

Most run on hardware that is not supported by seL4, or at least on hardware where it has not been validated.

Not to mention that a task manager would be needed as well as tons of other services which aren't provided out of the box, and don't share the verification provided guarantees.

HPE at least makes you flip a DIP switch, otherwise it complains loudly and halts.

Pretty much all of them allow unrestricted access from KMS from factory, tough all of them have a way to disable it once configured, and HPE even throws shade until it's limited. KMS only works from the host itself.