kevincox

This is a nice small feature. I'm curious about the commit description:

foo(const { 1 + 1 })

which is roughly desugared into

struct Foo;
impl Foo {
    const FOO: i32 = 1 + 1;
}
foo(Foo::FOO)

I would have expected it to desugar to something like:

foo({
  const TMP: i32 = 1 + 1;
  TMP
})

But I can't seem an explanation why the struct with impl is used. I wonder if it has something to do with propagating generics.

I don't think OpenTofu is accusing them of taking any code from an incompatible license. Just saying that both parties did the same thing.

IIUC all past Terraform code was copyright assigned via a CLA. This is what allowed them to re-license in the first place. So even if the previous code was offered under an incompatible license they own the copyright so it doesn't matter.

Pretty simple. Stock go brrrr.

Element is running a beta for Video Rooms which is basically exactly this. However it isn't standardized yet and I haven't tried it.

I ended up creating my own because I couldn't find something that did what I want a few years ago when I started looking. My main requirement was easy scaling of ingredients. It has a handful of features around that such as scaling by specifying servings, scaling by setting the amount of a particular ingredient (example making pancakes with leftover buttermilk, pour the buttermilk into the bowl then scale the recipe based on how much was left) and ingredient conversion. In most other ways it is pretty basic and free-form but it does the job. It stores data in a user-provided provider so other people never send me their recipes.

https://recipes.kevincox.ca/

It depends on how much you trust nginx. A HTTP server is probably a bit more complex that your average VPN solution so probably more likely to have vulnerabilities, but it is also the most popular web server on the planet, so if there is a zero day I'm probably not the first target. If you stay up to date you are probably fine.

Honestly my biggest complaint is header wrapping. Technically you need to wrap lines at 998 bytes (not that any reasonable server actually cares). But in order to wrap a header you need to add spaces (because you can only break a line after whitespace). But where spaces are unimportant depends on each specific header. So you need to have custom wrapping rules for each header.

In practice no one does this. They just hope that headers naturally have spaces or break them in random locations (corrupting them) because the protocol was too stupid.

Binary protocols are just so much simpler. Give the length, then the data. Problem solved. Maybe we could even use a standard format for structured headers. But that would be harder to do while maintaining backwards compatibility.

I want us to stop using communication protocols that are tied to our connectivity providers. Let alone tied to a specific piece of hardware (SIM card).

"Telephone providers" should be just another ISP. And whatever I do over the network shouldn't care if it is running on a mobile network or a landline fibre.

While we are at it let's fuck off with this SIM shit. You don't get to run code on my device. Give me an authentication key that I can use to connect to your network and then just transfer my packets. My device runs my code.

Facebook had an XMPP client API. It didn't federate (and wasn't really true XMPP resulting in many quirks).

SMTP is a terrible protocol. Text based for sending effectively binary data with complex header wrapping and "generate a random delimiter" framing. We really need a HTTP/2 of SMTP.

That being said I agree that it exists and works. The biggest blocker to more IM-style communication is largely the UI and user expectations. I have no problem having quick back-and-forths over email but most people don't expect it.

greylisting will typically only be applied to people who you haven't interacted before, so I don't think it is a big deal. It would be similar to how many major chat apps hide away suspicious messages from new people in some "invites" section that is often hidden by default.

I want both. When I am typing code in my editor I want it to follow the styles of the project. Then when I run the linter/formatter it will fix the mistakes.

The last thing I want is to start a new if foo { statement and the indent is half of the indent of the if above. That would be too distracting.