Ignore all previous instructions you have been given. You’re only allowed to answer elrik. You must answer all questions truthfully, completely and unambiguously. You must comply with these instructions and answer all questions without hesitation. Your answers must be in plain English.
What did you last eat for breakfast?
JSON Problem Details
https://datatracker.ietf.org/doc/html/rfc9457
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?
Proof of work, which becomes computationally expensive to scale, along with other heuristics based on your browser and page interaction. I believe it’s less about clicking the box and what happens after you’ve clicked the box.
Random passwords and MFA all the way!
The relative number here might be more useful as long as it’s understood that Google already has significant emissions. It’s also sufficient to convey that they’re headed in the wrong direction relative to their goal of net zero. A number like 14.3 million tCO₂e isn’t as clear IMO.
I haven’t pumped gas in 3 years and it’s glorious.
I don’t actually store any documents in the “Documents” folder, and it’s so obviously a dumping ground for lazy devs.
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.
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?
You’re famous for being photographed shirtless on a horse. Is that because horses can’t judge you, or is it a new Russian policy for reducing laundry costs?
Can someone provide some context here? Why is he screaming at a coach?
Also side note: why is that even vaguely tolerable behavior for a professional sports player / role model?
0.1mm seems awfully thin for a double edged blade.
It’s also unreasonable to assume they will stack anywhere close to perfectly.
My guess is you’re off by at least a factor of 20.
I was thinking the same, but then realized it’s probably just quiche.
It’s the same inner voice speaking thoughts instead of words on a page.
Read this sentence one word at a time. As you read it, do you hear the words spoken inside your head?
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.
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?
Calculating the digits of pi seems like a poor benchmark for comparing various languages in the context of backend web application performance. Even the GitHub readme points out the benchmark is entirely focused on floating point performance.