Upset millennial.
Code quality matters.
You are correct in identifying that trying to make fetch happen won’t work. There’s already a multitude of options for establishing network security native to any OS, or an open project that’s deviated in their own way.
You could write a wrapper for everything, but unless that’s the intent of your app it may be scope creep.
This is Information Theory at work. You’re compacting (n+1) signals, where n is any number between 1 and infinity, to 1. With javascript execution, anyone can get timing, webgl, location, device hardware access, etc… Without it, they just get a single bit that tells them to fuck off.
It’s a technical arms race and good hygiene to review code from untrusted third-parties.
They’re the fucking boot
They do say, you gotta eat the booty like groceries
I gave the example of PPPoE, the other option is to read the linked kernel docs to understand traffic steering and infer where those situations could occur.
Opensense is often bound by single-core operations depending on where a network packet may plumb itself through the kernel. A great example is any PPPoE connections on the base OS BSD. Vyos doesn’t have these same limitations since it’s minted on Linux - which supports traffic steering.
Really though, IaC for vyos has always been rock solid. Even though the persistent config in Opnsense is cool, adding new features or configs can be a bit of a pain in the ass
Lolol, they’re real.
Behind the Bastards did a great episode on these weebs: https://www.iheart.com/podcast/105-behind-the-bastards-29236323/episode/part-one-how-ai-chatbots-became-cult-leaders-332611718
Possessive nouns over people are annoying af, mad get it. It’s not supposed to come off that way but, words mean things.
Reading is hard 😂 sorry homie.
That’s acid etched homie, I’d clean it out with some barkeepers friend and then see if you can polish that haze for a cool two tone bowl
The paper linked in the article is most excellent for anyone looking for a basis on technical writing.