Because it's dope.
Also, according to their website the 10 and 25 Gbit/s packages cost the same per month.
Also, still cheaper than my 1 Gbit/s connection.
Because it's dope.
Also, according to their website the 10 and 25 Gbit/s packages cost the same per month.
Also, still cheaper than my 1 Gbit/s connection.
The RFC you linked recommends that no new X-
prefixed headers should be used.
The paragraph you quoted does not say you should use the X-
prefix, only comments on how it was used.
See section 3 for the creation of new parameters: https://datatracker.ietf.org/doc/html/rfc6648#section-3
I still work on software that extendively uses X- headers.
I wouldn't worry too much about it. The reason they give is mostly that it is annoying if a X-
header suddenly becomes standardized and you end up having to support X-Something
and Something
. Most likely a non-issue with real custom headers.
We don't have many unit tests that test against live APIs, most use mock APIs for testing.
The only use for this header would be if somebody sees it during development, at which point it would already be in the documentation or if you explicitly add a feature to look if the header is present. Which I don't see happening any time soon since we get mailed about deprecations as well.
My dad has an old Makita cordless drill from 1995 which he used for everything from assembling Ikea furniture to drilling holes in cement walls. Complete metal innards, full metal case, battery that's big and heavy enough to bludgeon somebody to death with.
Until one day I bought a fancy new Bosch cordless screwdriver with Li-ion battery, brushless motor and 1/4 the size and weight of the Makita.
At first he laughed at me for buying a toy, then he tried it. He ordered one as well the week after and uses it pretty much exclusively since then.
Still keeps the Makita box and drill around purely for the retro look but even with fresh batteries the amount of torque they put out is not even in the same league.
Obviously that is the exception rather than the rule and most technological advances went into making companies more profits instead of building better products, but there are some advancements that made power tools better. Li-ion batteries and brushless motors being two of the big ones.
I don't really get the purpose of a header like this, who is supposed to check it? It's not like developers casually check the headers returned by an API every week.
Write them a mail if you see deprecated functions being used by a certain API key, probably much more likely to reach somebody that way.
Also, TIL that the IETF deprecated the X-
prefix more than 10 years ago. Seems like that one didn't pan out.
They are expensive but I run a OPNsense DEC740 and have no issues with my Gigabit fiber, even without modem and the PPPoE overhead.
You can still try playing with hardware offload on/off and if you use PPPoE, it runs on a single core by default.
I have an AMD GPU and play all my Switch games on the last yuzu EA build on Fedora. Works pretty much flawlessly.
I really liked the first season, a much darker take on the usual cutesy anthropomorphic animal world.
Not a huge fan of season two, felt really rushed. It had some great episodes and I'm definitely checking out the next season but I felt disappointed after the strong first season.
Found the Austrian. :) #tirolgehtanders
This integrates Meilisearch but without having to mess with the Jellyfin search code while Jellyfin is transitioning to EFCore.
FYI, you may need to change the logo. I didn’t think 3rd party tools are allowed to use the official logo, but someone who knows more about that will need to weigh in.
Good point, I don't mind changing it if it's against their guidelines. It's more of a crutch until full-text search arrives in Jellyfin proper, no need for a fancy logo either way. :)
I don't think you can import pfSense configurations into OPNsense. I switched from a DIY pfSense box as well and redid the config.
You can look for a converter or install pfSense onto it though.