skrtskrt

I mean compete at least in part on the price that end-users will be charged

More applications should mean they have to compete on price tbh.

Sure if AirBnb wants to administer .airbnb and charge a lot, whatever.

But `.bit` domains should be some bargain basement price if so many people want to run it.

Seriously that is the sort of thing that could get you hunted down by angry nerds.

I am NOT going to use .home.arpa.

I have been looking for an expansion of TLDs that are short, have a decent ring for self-hosting stuff, and don't sound too scammy.

Like `.link` is pretty cool but it's expensive because one of those personal-link-inbio companies created it and wants to cash in on it.

Just from scanning these, maybe:

* .air

* .bit

* .hub

* .iam

* .index (long but I love how universal it is)

* .lab

* .log

* .pod

* .port

* .self is really interesting, wonder if that would take off

* .sys

* .zen

Yeah Mimir cleared a billion series years ago prior to several recent re-architectures that make it faster and more efficient to run.

And packaging + distribution is ridiculously easy.

We are moving every script we can to Go. Compared to bash it's a no-brainer, every dev can understand it, it has approximately .0000000000001% of the possible footguns, a great debugger, etc.

> Conclusion

> Looking at the visual timeline, we can see that changes to example.com happen sporadically.

I am glad to see someone else struggling to write a non-awkward conclusion to a technical blog. I always feel like I am just restating the obvious to the point that it is borderline insulting to the reader. But I don't have much more to say and removing the conclusion makes it seem like the whole thing just fell off a cliff.

Do you do any sort of rate-limiting to stop people/bots from hammering it (accidentally or otherwise)? Or do you just let it fall over under load.

Scoffing and thinking "hasn't this guy heard of Jupyter" says more about your attitude than it does the tool or its README copy.

Hasn't this guy heard of [old product that is a huge pain and no one likes]? Why would he ever make something that suits his own interests and preferences?

> no revenue line to follow, and no market to lose

Two paragraphs later, the topic is:

> Cost

I mean this is just incredibly lazy thinking and writing. There's always a cost line to follow, just because there's "not a revenue line" means absolutely nothing it just sounds pithy.

And if you cut your cost hard enough, you will put platform stability in danger, or hamstring your engineering org's ability to test and iterate, which will make you lose your market.

Again, incredibly lazy thinking and writing.

Not only is this utilitarian nonsense, the "math" here is full logical nonsense.

It shocks me how anyone could string this pile words together and think they sound like anything at all.

> "2 out of every 10 productive dollars"

As if those dollars have anything to do with the time people work, or that they would get those dollars and time back by not caring about health.

As if the tiny portion of those dollars that actually gets spent on patient healthcare isn't dominated by end of life care.

The US healthcare system spend is so far divorced from whatever idea of "productive dollars" anyone has when it's 60-80% admin cost. The US should not even be mentioned in any conversation about the ROI of health spend.

That system you described is quite rare - it would have to poll N databases of N possible events constantly to see if it should give you a reminder. Which is why none of the common calendar systems do that.

They just create events, which have a time zone and represent and exact point in time. And they don't change the event or when you get notified when you change time zones.

But there is zero use case difference between these two things you mentioned:

> if a point in time should be sticky to a calendar store a datetime _without_ a timezone

> If you want a point in time which will not "physically" change, store a datetime _with_ a timezone

Both of these things are exactly identical. You are still storing an exact point in time in both cases. The only thing about a calendar use case is the presentation layer.

You're still just talking about client conversion on the write instead of the read. A Unix epoch is a UTC timestamp. That number is not time-zone-less it's just in the default computer time zone.

What’s the difference between these two other than how the client would convert to display to a user?

The built-in formatter drives me insane it's always choosing or not choosing to line break in places that make zero semantic sense.

Low-latency fiber interconnects to other nearby data centers are a core feature of datacenters.

OAuth2 is fine, I mean:

1. It's not an authentication protocol, but it was abused as one for until OpenID Connect came along

2. OpenID Connect is the compatible authN protocol, and it actually has a spec unlike OAuth2

Both of those are annoying because they are over-complicated for simple use cases and for a long time there were very few simple open-source providers that weren't hiding all the important stuff behind their enterprise/cloud versions.

Open source options like Zitadel are improving this space somewhat, though they are still sort of painfully complicated if you want to deploy something small and simple that you can understand. In order to be big business they have to support tons of 3rd-party provider plugins with all their out-of-spec wrinkles.

It would be nice to have something like Zitadel that is signficantly less concerned about all those third parties - like let me very easily just host username/password and passkey auth in a small package.

Even if everyone had enough financial security (or realized they did), you need coordination, people are never going to independently and spontaneously turn down these jobs at evilcorp en masse - you need coordination, a.k.a strong unions which can actually effect the policies of the employer.

That is not true for debit cards in the US, which is my point.

Amazon and other clouds already patch the hell out of Linux, but they don't distribute physical devices with that Linux on it to anyone, so they don't have to deliver source code either.

I am not totally sure I see the actual concern here, that a company is going to sell devices with a really great `find` implementation but not contribute it upstream?

X11 and everything around it is unfixable security hazard slop, just slop that was painstakingly created by humans.

Also Wayland is it being forced on us? I have plenty of coworkers that run X daily because they are still afraid of the Wayland boogeyman despite the fact that their supposed clipboard and screen sharing problems in Wayland (the only two supposed problems they can name) have been solved for years.

In theory there could be a the MIT version relicensed to GPL and this version could be carried as a standard if having MIT software as core utilities was considered enough of a threat - right? You just have to retain original license/attribution.

That would be an awfully awkward move in the realm of Linux-related politics but if having an MIT-licensed coreutils was such an existential thread, at least you can fix it with aggressive license moves and not code.

How do “stream over an open connection” and things like “sleep for months” play together?

Naively without digging into the code I would look at a “streaming over an open connection” as likely to strictly more brittle.

Does this actually matter that much for some tools when the kernel is GPL?

In the US there are very strong fraud protections for credit cards, but a debit card is just unfettered access to your bank account.

For safety reasons I never use a debit card for anything but an ATM.

Don’t you need a runtime to do Go/Java style?

ArkKVM is a fully open source product now

Sweeping Nazi shit under the rug is one thing, sending them free money is even more pathetic.

No don’t worry they said it’s not slop because there’s tests lol