[0] https://en.wikipedia.org/wiki/The_Master_and_His_Emissary
40 karma · joined August 15, 2023
[0] https://en.wikipedia.org/wiki/The_Master_and_His_Emissary
But I sure wish it was 'core' and we didn't have to worry about it potentially going away, becoming de-supported..
Compare the opening lines:
Fagles:
Sing to me of the man, Muse, the man of twists and turns
driven time and again off course, once he had plundered
the hallowed heights of Troy.
Wilson: Tell me about a complicated man.
Muse, tell me how he wandered and was lost
when he had wrecked the holy town of Troy,
The Wilson translation is TOO distilled/simplified for me. It reads something like Hemingway or a hard-boiled noir detective story.The Fagles translation is much more lyrical without being overly pompous or florid, and the McKellen audio version (which is the way the story was first told, right?) is delightful. Reading along as McKellen tells the story is a joy.
https://www.theguardian.com/books/2026/jul/16/a-voyage-of-di...
I think you mean it is perplexing how the leaders of certain major powers seem incapable of learning from history. It seems clear the relevant advice has been available. And yes, I also suspect arrogance but the list of problematic personality traits that apply to the current situation have been exhaustively detailed all over the place...
Any references for that? Genuine question.
Anyway, my vapid observations aside, I have a couple of related questions:
- I too would be willing, even keen, to contribute to good documentation of FOSS projects that need it and that I am interested in - a huge barrier to me is that a person needs sufficient understanding to really contribute, don't they? To the point that you pretty much need to get into the code quite deeply or else endlessly pester committers to explain how it works? OK, I am generalising, but it seems valid in the main. A while ago, I observed on a relevant list that the libvirt documentation of how to take qemu snapshots was amazingly fragmented, inconsistent and out of date and this led to comments that I should step up and produce some PRs - but my whole point was that this sh1t is hard to understand without very good docs! I would barely know where to start and I would be very hesitant about making definitive statements...
- As for improving doc structure - and this is a serious consideration as soon as you sit down to think about this stuff - I came across and adopted the https://diataxis.fr/ framework a few years ago.. I have to say the uptake among my co-workers has been dismal. Can anyone suggest doc frameworks or approaches that are more motivating, have less friction, whatever?
Intrigued by spiderfoot, but seeing that the last release - from that repo anyway - was in 2022, I assume the action has moved elsewhere, given that this is a very quickly changing field - anyone know?
Both of these make me realise how out of date my copy of Bazzell's OSINT Techniques is..
I am up for this! One question: do you accrue push-ups during the day in a 'greasing the groove' type approach and then stick in the total at end of day? Or more of a session? Just curious what was successful for you...