JSON Problem Details

https://datatracker.ietf.org/doc/html/rfc9457

• It has a specification, so a consumer of the API can immediately know what to expect.
• It has a content type, so a client sdk can intelligently handle the response.
• It supports commonly needed members which are a superset of all of the above JSON examples, including type for code and repeating the http status code in the body if desired.
• It is extensible if needed.
• It has been defined since at least 2016.

This specification’s aim is to define common error formats for applications that need one so that they aren’t required to define their own …

So why aren’t you using problem details?

Its use looks contrived to me on the linked GitHub page. The comparison with @ and # is flawed because those symbols are part of the resource name, whereas here the symbol is superfluous. It’s like adding a 🌐 in front of every web URL.

This isn’t the evolution of C at all. It’s all just one language and you’re simply stuck in a lower dimension with a dimensionally compatible cross-section.

I’m sure the original comment had incorrect units as used, but this explanation that cumulative units “can’t peak” seems wrong.

If you consider the total stored energy (Wh) over time of a solar-battery system under load, there certainly will be peaks or, in other words, maximal excess capacity of the system.

So no, it’s not impossible to define a unit of Whp as such. “Cumulative” and “momentary” values are not exclusive and also do not have any bearing on whether a function of such values has maxima and minima.

Those companies aren’t “the Internet.” They’re products connected to the Internet.

The OP argument is like saying the Internet is dead because Netflix is down.

Doubtful. By far, most servers responsible for Internet traffic are not running crowdstrike software.

This incident was a bunch of fortune 500 companies caught with their pants down.

Isn’t it available on PS5?

Thanks for the clarification and I believe I misunderstood your original comment.

To add to your list there is an often underutilized feature of GitHub for discussions too.

You mean pretty much a single GitHub account?

Also your quick question may have already been asked and answered but difficult to find on Discord. Or if it hasn’t been asked yet, now a future person can’t discover the same question easily. So either way you’re just wasting other people’s time.

The distinction is web workers and offline mode.

It means your PWA can preload everything it needs to run offline, and you can actually use it offline. That is different from a “cached website” which can only cache the pages you’ve already visited and otherwise does not allow you to update data locally.

Yes, although that recently changed in the EU (only) with the Digital Markets Act.

deleted by creator

Really interesting! I wonder what would happen if you combine these two properties. Suppose some length of the middle is all walls, and the hooks are infill, or vice versa. Is there an optimal mix that maximizes the weight it can support in your testing, or have you found the optimal configuration (with infill along the entire length) already?

I recently went through these exact pains trying to contribute to a project that exclusively ran through Discord and eventually had to give up when it was clear they would never enable issues in their GitHub repos for “reasons.”

It was impossible to discover the history behind anything. Even current information was lost within days, having to rehash aspects that were already investigated and decided upon.

You can also mark designs as ready-only and they no longer count, so this limit is really 10 concurrently editable designs. I just keep everything read-only unless I’m actively working on it.

You’re right, “pounds” is ambiguous.

0lbs ≠ 0kg in the absence of gravity.

Do you understand how many computer programs will crash when you try to introduce a “month” consisting of a single day for this New Year holiday, or alternatively a day which does not have a corresponding month?

Is your Netflix subscription going to renew in December, and then next in January, or is there a troll of a month sitting in between where you’re charged for a day?

How many schedulers have rules like the second Tuesday of the month, or the last Friday of the month, and those days don’t even exist!

Is this special holiday even assigned a weekday? If it is, do we repeat the same weekday twice to keep the 28 day months on the same weekday schedule?

Madness! /S

Download Bambu Studio and slice some multi material prints. The preview tells you how much filament will be purged. There are several settings and model characteristics that will affect the purged volume.

Flushing volume: this directly controls the volume purged while swapping between any two filaments. Darker to lighter colors will need a higher flushing volume. You’ll also need a higher flushing volume when changing materials.

Purge to infill: this reduces the purged volume by accounting for the volume that can be printed as infill before reaching perimeters. It’s not very effective for smaller models because there is just less infill area.

Printing multiple copies: this reduces the ratio of waste to printed parts, since for each layer you’ll need the same number of filament swaps.

Part orientation: often the part orientation will have a dramatic effect on the number of filament swaps. Imagine a blue cube with a red face. This can be optimized to one color swap if the red face is horizontal instead of vertical.

Print sequentially: For multiple parts on the plate, grouping them by color similarity and printing groups sequentially can reduce the number of swaps. Imagine two blue parts and two red parts on the same plate. This can be optimized to one color swap for the entire print instead of one swap per layer.

In my experience, the waste for average complexity multicolor prints is similar in scale to supports, and is easily offset if you’re upgrading from a less reliable printer. Failed prints are filament waste too.

Haha I’ll bite. What’s your suggestion?