jcgl

16 ms·

241.
by jcgl 10mo ago
What makes ss different? In any case, interesting to think of shared libraries (specifically shared libc) as a risk here. Makes sense, but I hadn't thought about it before. That said, I'm having a hard time doing a threat model wh
242.
by jcgl 10mo ago
How are TUI tools just as accessible as the terminal? Take a visually-simple program like neomutt or vim. How does a vision-impaired user understand the TUI's layout? E.g. splits and statusbar in vim, or the q:Quit d:Del... labels at
243.
by jcgl 10mo ago
Completely agreed. Not sure what the historical reasons for lsof and ss are, but unix tools are structurally in a hard place when it comes to having sensible defaults over the long term. Generally speaking, you can only have sensible defaul
244.
by jcgl 10mo ago
What network effects? Like a sibling comment already pointed out, privacy addresses come standard on all consumer OSes.
245.
by jcgl 10mo ago
What do you mean? Apps for iOS and macOS have had perfect v6 support for a long time because of this. Linux has unified address families for netfilter and internet sockets that abstract the details. Various programming languages have perfec
246.
by jcgl 10mo ago
Those naughty incoming packets can hit your private devices even with NAT-without-state full-firewall. The details depend on how your NAT actually implements the translation, but it’s perfectly possible for $randomHighPort to send all its
247.
by jcgl 10mo ago
Misspoke: more like a CLAT thing/464XLAT, rather than SIIT, I think
248.
by jcgl 10mo ago
Providers can do v6-only in their core while still providing public v4 to users. SIIT if they can still afford a public IP per customer, and MAP-T if they can’t.
249.
by jcgl 10mo ago
ULAs. It’s like a better version of v4’s RFC1918 addresses.
250.
by jcgl 10mo ago
- Devices using SLAAC (idk about DHCPv6) do a thing called Duplicate Address Detection to manage just this. No need to worry. If you’re manually assigning addresses and have a conflict, one of the devices will mark its address(es) as duplic
251.
by jcgl 10mo ago
> The hang up here is SWEs belief those abstractions must be stored as some syntax they know What does it matter how it's "stored"? I think (hope?) that most SWEs know that that syntax and its semantic aren't how thin
252.
by jcgl 10mo ago
Podman makes this easier to do safely by default. I'd suggest checking that out.
253.
by jcgl 10mo ago
Agree with the other comments about writing OpenAPI by hand. It’s really not that bad at all, and most certainly not “verbose to the point of absurdity.” Moreover, system boundaries are the best places to invest in being explicit. OpenAPI s
254.
by jcgl 10mo ago
You’ve still gotta do that for every TLS library used then. There’s a finite list of them of course, but it’s more than just a few.
255.
by jcgl 10mo ago
You're talking about Bluesky's ATProto instance (term.?). Other commenter is talking about ATProto as a protocol .
256.
by jcgl 10mo ago
Also, it should be obvious that sources from the cryptocurrency industry have a conflict of interest. If there are better sources than something like Binance, then those should be used. If there aren't better sources, well...
257.
by jcgl 10mo ago
Lightning isn't Bitcoin. It's an L2. It helps implement actual practical payments for Bitcoin, and doesn't (afaiu) manage account balances. In other words, you cannot seriously compare it to Mastercard; you've gotta incl
258.
by jcgl 10mo ago
> compared to the existing banking system it's trying to replace I don't think it's appropriate to compare it to the existing banking system (whose featureset goes far beyond payments and managing account balances). It&#x2
259.
by jcgl 10mo ago
> The result is that you have a zoo of iteration-related helper functions all throughout. You'll need to learn those when onboarding to a new code base as well. This is overblown, imo. Now just generics exist, you just define Map()
260.
by jcgl 11mo ago
And has a lot more practical benefit than any competing implementation of, say, your libc or coreutils.
261.
by jcgl 11mo ago
Not to split hairs, but that sounds more like plain hackery rather than proper extension. Let alone a viable future. I don't doubt what you say that it's possible in the most technical sense of possibility. But actually possible
262.
by jcgl 11mo ago
First of all, non-standard extensions to federated protocols have a pretty rough history. Even when an extension reaches median adoption (rare, I assert), the long-tail adoption is dismal. For something as fundamental as Second of all, how
263.
by jcgl 11mo ago
I don't tend to believe in cryptokey-first protocols like Nostr, where your identity is tightly coupled to a keypair. Human identity doesn't work like that at all, and keypairs as the basis of identity will never be suitable for u
264.
by jcgl 11mo ago
Unfortunately it's most ActivityPub-oriented, right? Which means no name portability. That's a major shortcoming compared to an AT protocol-based thing like Tangled appears to be.
265.
by jcgl 11mo ago
I switched away from Nomad when HashiCorp moved from FOSS licenses to the BSL. But man, I do miss its simplicity.
266.
by jcgl 11mo ago
If you don't like those additional name resolution methods, then turn them off. Resolved gives you full control over that, usually on a per-interface basis.
267.
by jcgl 11mo ago
It's a great option to have, but ultimately it's at-best pretty slow.
268.
by jcgl 11mo ago
That doesn't seem right to me, assuming you still want the paradigm of one-time principal-to-domain authentication with just-in-time principal-to-resource authentication. While I think you could probably use x509 certs to streamline an
269.
by jcgl 11mo ago
That's pulling on a dependency. An ugly case, but a very specific one relating to a tricky backwards-incompatible change that the Go team fudged on back in the pre-module times. That story doesn't generally speak to the reality
270.
by jcgl 11mo ago
> Golang included the "log" package, which was also a disaster. No one used it so they introduced log/slog recently, and still no one uses that one, everyone is still using zap, logrus, etc. I honestly don't know how

More ›