HackerLangs
TopNewTrendsCommentsPastAskShowJobs

jcgl

406 karmajoined قبل سنتين
sysadmin and low-key programmer

[email protected]

(my website and mail are hosted on my laptop; they may be offline at any given time.)

comments

jcgl
·قبل 11 ساعة·discuss
Oops, yes, I don't know why I mistyped a question mark. That's exactly what I was wondering, thanks.
jcgl
·قبل 12 ساعة·discuss
There is some cool stuff here.

I like using column to format the table. Appending it to alloyed's command fixes their header problem.

The stdbuf to multi-command block (term.?) is a neat trick. Although, one time when I ran this, I only got a couple lines of output. No idea why and I can't replicate it, but there could be some flakiness that results from the buffering somehow?

Question: how do the ? markers on the sort and column invocations work/what do they do?
jcgl
·قبل 14 ساعة·discuss
Yes, the point was about doing it in a pipeline. The pipeline is the basis for composition of plain text in the unix shell. If something as basic as sorting a table is hard to do, it should make us question just how good the unix shell/plain text philosophy actually is.

Baking --sort flags into shell tools is a sign that the tools do not compose well.
jcgl
·قبل 15 ساعة·discuss
Ooh, I was so hoping someone would take up the challenge! This is a far shorter answer than I had honestly thought was possible. More readable too, somehow? Great use of tee that I would never have come up with (though I hear what you say about there maybe not being ordering guarantees).

Unfortunately, it's not 100% correct, due to misaligned headers:

  REPOSITORY TAG IMAGE ID CREATED SIZE
  registry.fedoraproject.org/fedora-toolbox 44 5a36f433c691 2 months ago 2.14 GB
  quay.io/keycloak/keycloak latest 1361d6e49205 9 days ago 478 MB
  ...
I think that speaks to your final point, which is spot-on:

> I'd probably just end up dropping the header and living with worse output in reality

This pretty much sums up plain text and unix shell imo. It's very much the pragmatic solution here, and it's what ~100% of shell scripters would choose to do. And it should make anyone question the orthodoxy around the "power" of plain text in shells.
jcgl
·قبل 18 ساعة·discuss
Great example! How do you like using elvish? Even though I am a proponent of structured data and like PowerShell a lot (mentioned in a nearby comment of mine), I use fish as my regular shell. Big fan of fish's careful focus on user experience, but would be open to trying something structured.
jcgl
·قبل 18 ساعة·discuss
I think you're mistaking text-with-structured data for structured data itself.

Because unix shell is irrevocably text-oriented, kludging in something like JSON is basically the best that can be done when you start to want to do structured operations on structured data. (I'm sympathetic to your point about the AWS CLI tools doing JSON by default though--that just sounds like bad design.)

Being text-oriented imposes drastic limits on composability. Because there is no structure, every element of a pipeline needs to do its own parsing of the input data. This leads to brittle pipelines where every element is tightly coupled to its input's textual representation.

As an exercise, try to write a pipeline that sorts podman images by size without removing the column headers[0]:

  $ podman image ls --all 
  REPOSITORY                                 TAG         IMAGE ID      CREATED       SIZE
  docker.io/prom/prometheus                  latest      937690d77350  2 months ago  367 MB
  quay.io/keycloak/keycloak                  latest      da9433c9fac3  2 months ago  466 MB
  registry.fedoraproject.org/fedora-toolbox  43          a32da54355ca  4 months ago  2.19 GB
  docker.io/powerdns/pdns-auth-49            latest      8c1385c9deed  4 months ago  208 MB
  docker.io/testcontainers/ryuk              0.13.0      b75bc7ce94c3  6 months ago  7.21 MB
As far as I can tell, there is no way to do this in a manner that's even remotely composable. Your best bet is to basically do everything from within awk. Whatever the result would be, it certainly won't be pretty!

Contrast that with what you can do in PowerShell. You can write a couple of standalone functions[0] that are readable and composable, resulting in this pipeline:

  podman image ls --all |
      Replace-SpacesWithTabs |
      ConvertFrom-Csv -Delimiter "`t" |
      Sort-Object -Property {Convert-HumanSizeToBytes -Size $_.size} -Descending

[0] Repurposing this from a blog post I wrote: https://www.cgl.sh/blog/posts/sh.html#this-should-be-basic
jcgl
·أول أمس·discuss
> Isn't that what you want on that platform? ADCS even supports issuing remote-attested TPM certs via EK, no need to reinvent the wheel.

This is really cool. Did not know about it: https://learn.microsoft.com/en-us/windows-server/identity/ad...
jcgl
·قبل 3 أيام·discuss
Just as importantly, they have little to no alternative. And then they are given every opportunity to learn—at school, by parents, and so on.
jcgl
·قبل 6 أيام·discuss
Sure, I take your point that the smell-test works reasonably well for domains related or adjacent to one's own.

But (not speaking about your use specifically here) many people (most, I'd wager) use LLMs for many things beyond their own expertise. And it's there that they're most likely to be ensnared without even knowing it.

I definitely agree with your notion that learning-by-doing is a helpful salve for LLM falsehoods. It's no panacea (working != correct (an incorrect solution can appear correct over a given interval)), but it's a good way of working in general that helps keep LLMs in check. And it's very natural to code or other things that can be immediately applied.

But learning-by-doing of course doesn't work with topics that aren't immediately applied. Which includes lots of topics that people use LLMs for (Wikipedia too, for that matter).

The set of unfamiliar-or-unapplied is practically a lot larger than the set of familiar-or-applied.
jcgl
·قبل 6 أيام·discuss
> bad info becomes apparent, almost immediately

Can you elaborate on this? I suspect that you’re thinking mostly of cases in which you already have a fair bit of domain expertise. But in the general case, this seems to be very untrue. Which is why it’s so pernicious that LLMs can generate such quantities of syntactically-plausible-but-factually-untrue text.
jcgl
·قبل 15 يومًا·discuss
Agreed. That would make this way more insightful. Otherwise most searches will basically be a version of https://xkcd.com/1138/ during periods of site growth.
jcgl
·قبل 17 يومًا·discuss
> This is covered by allowing for single-use credentials. IIRC the EU personal IDs will use this. Basically, the wallet requests a batch of single-use eIDs that all use different device key-pairs. Each credential is only used for one request and then deleted.

But this then means that the issuers and the verifiers can trivially collude to deanonymize holders/users.
jcgl
·قبل 20 يومًا·discuss
Citation needed. These numbers are quite consistent with the growth pattern that started well before usable LLMs were even a thing.
jcgl
·قبل 23 يومًا·discuss
First of all, multi-party democracy needn’t be slow. Parliamentary systems in multi-party countries often react faster than the US. This is due in part to legislation being systematically easier to pass.

Second of all, winner-take-all presidential mechanics don’t imply a four-year cycle of funding instability for research. That only happens if the president has sufficient control of funding. Which, through the administrative state (which is supposed to basically be a delegate of congressional authority), really is supposed to be insulated in large part from presidential, partisan politics. With increased centralization of power in the president (which, imo, is largely just an ~evolutionary response to Congress’ sclerosis), this insulation is lost, exposing research more to the four-year cycle of heavily partisan presidential politics.
jcgl
·قبل 24 يومًا·discuss
How do you reconcile that position with what Graphene OS lists as requirements for support, as linked by another commenter? https://grapheneos.org/faq#future-devices

I’m not an expert, but all the listed points there sound reasonable. If indeed only the Pixels support them, well, it’s too bad there’s not other, similarly secure hardware out there.
jcgl
·قبل 27 يومًا·discuss
I’m no expert, but as long as they’re represented by tokens in the end, they’re just tokens. Even if you train the transformer to treat them specially, a token is a token, and there’s no free lunch. At best, you’re going to be trading off between paying attention to this would-be security boundary and delivering high-quality results; the more you focus on one, the more you lose on the other.
jcgl
·قبل 28 يومًا·discuss
Case-in-point: just started a new chat with a new person (we had a previous room in common)--My desktop client, NeoChat, shows "This message is encrypted and the sender has not shared the key with this device." for all of their messages. FluffyChat on my phone shows their messages correctly.

Welcome to Matrix. It's the best option there is, and it's not very good.
jcgl
·قبل 28 يومًا·discuss
> has good clients

So far, I've only found clients with different bugs. Calling them good would be a stretch. Passable, perhaps. But the scene as a whole is more of a choose-the-bugs-to-live-with situation than choose-a-good-client.
jcgl
·قبل 28 يومًا·discuss
You’re mistaken: DKIM always signs the entire From field. Signing is done on the MTA, so yes, it is “the reputation of the server” like you say, but “server” can be a relatively granular thing here, using different DKIM selectors for different addresses, MTAs, etc.
jcgl
·قبل 29 يومًا·discuss
This is mostly what it is for me too. We're all awash in an information deluge, and we need heuristics to keep from drowning. Human effort, proof-of-work if you will, is a heuristic that helps with the AI-generated part of the deluge.