no particular message, read into it whatever you want to
#logging
5 posts5 participants0 posts today
Indonesia is the first test case for the Forest Stewardship Council’s new remedy framework, which allows logging firms to regain ethical certification by addressing past environmental and social harms.
However, NGOs have found serious flaws in the process, including lack of consent, rushed assessments, and exclusion of many affected Indigenous communities.
by Hans Nicholas Jong
https://news.mongabay.com/2025/07/hope-and-frustration-as-indonesia-pilots-fscs-logging-remedy-framework/
Mongabay Environmental News · Hope and frustration as Indonesia pilots FSC’s logging remedy frameworkJAKARTA — Indonesia is testing whether one of the world’s most powerful timber certifiers can deliver justice — or merely a reset — to forest communities harmed by industrial logging. At stake is the credibility of the Forest Stewardship Council’s (FSC) first-of-its-kind “remedy framework,” an ambitious mechanism that allows logging companies stripped of certification to […]
Albanese government plotted to maintain native forest logging in NSW if court battle was lost, documents show https://www.theguardian.com/australia-news/2025/jul/24/albanese-government-plotted-to-maintain-native-forest-logging-in-nsw-if-court-battle-was-lost-documents-show
Albanese has no love for our environment.
The Guardian · Albanese government plotted to maintain native forest logging in NSW if court battle was lost, documents show
So there's this #ai thing out here.
People who are on the bleeding edge and doing this in prod/at scale/at enterprises: how do you handle #otel #tracing and #logging of #llm calls?
There's only really semconv for traces as of now, and everyone in their playground is happy about seeing those huge prompts as attributes, but I think (and hear) that this won't work at most enterprises.
I can see that #GenAI Events[1] are the recommended way of handling messages/responses, which actually makes sense in terms of separating likely sensitive information from the more useful telemetry. I can imagine these to be generally more useful for security teams (auditing) than ops people.
I have a couple of questions from a practical point of view though:
- How should one separate these events from tracing data in terms of processing/ingestion?
- How should one still have the complete audit trail of what has happened (which agent called what other agent that get information via another tool and dumped some part of the source code as a response to the original question)?
I guess linking events to traces/spans would work, but depending on whether you have a single backend (SaaS vendor) or multiple this can get tricky from a UX point of view.
Boosts are welcomed!
[1]: https://opentelemetry.io/docs/specs/semconv/gen-ai/gen-ai-events/
OpenTelemetrySemantic conventions for generative AI eventsStatus: Development
GenAI instrumentations MAY capture user inputs sent to the model and responses received from it as events.
Note: Events are in-development and not yet available in some languages. Check spec-compliance matrix to see the implementation status in corresponding language.
Instrumentations MAY capture inputs and outputs if and only if application has enabled the collection of this data. This is for three primary reasons:
Data privacy concerns. End users of GenAI applications may input sensitive information or personally identifiable information (PII) that they do not wish to be sent to a telemetry backend. Data size concerns. Although there is no specified limit to sizes, there are practical limitations in programming languages and telemetry systems. Some GenAI systems allow for extremely large context windows that end users may take full advantage of. Performance concerns. Sending large amounts of data to a telemetry backend may cause performance issues for the application. Body fields that contain user input, model output, or other potentially sensitive and verbose data SHOULD NOT be captured by default.
Waiharara road blocked by rolled logging truck, motorists advised to avoid area
Northern Advocate 22 Jul, 2025 10:36 PMQuick Read Subscribe to listenAccess to Herald Premium articles require a Premium…
#NewsBeep #News #Headlines #advised #area #avoid #blocked #by #closing #logging #motorists #NewZealand #north #NZ #road #rolled #to #truck #waiharara
https://www.newsbeep.com/13754/
One of the last “dolphins” (cluster of pilings) from the old Comox Logging & Railway booming ground at Royston. There are a number of these still standing. They’re now host to birdhouses. Mostly for purple martins and swallows.
I just got in from swimming out to the dolphin and back.
RUMlogNG2Go for iOS version 6.3.17 now available
RUMlog is a contact logging tool for amateur radio, very similar and log file compatible to the Mac logger RUMlogNG.
Use the same log file on your Mac computer
4 user definable logging fields
Exchange the logs via iTunes File sharing, iCloud or Files
Import ADIF files via email, clipboard, iCloud or Fil ...
https://machamradio.com/blog/2025/07/20/rumlogng2go-for-ios-version-6-3-17-now-available/
Pre-release for testing KLog-2.4.2-RC1
KLog is a multi-platform free Amateur Radio logger, the only one able to run in Linux, Windows and macOS!
KLog provides QSO management, useful QSL management DX-Cluster client, DXCC management, ClubLog integration, WSJT-X, DX-Marathon support and much more! KLog is available in several languages: Catalan, Croatian, Danish, Engl ...
https://machamradio.com/blog/2025/07/19/pre-release-for-testing-klog-2-4-2-rc1/
SkookumLogger v5.3 now available
Bill Myers, K1GQ has released the latest version of the contest logging software SkookumLogger for macOS.
*** Please note: The final version of SkookumLogger available on the Mac App Store is 5.1. All future versions will continue to be available on the k1gq.net web site's downloads page. They are always notarized, and h ...
https://machamradio.com/blog/2025/07/19/skookumlogger-v5-3-now-available-2/
RUMlogNG version 5.19.5 released.
Tom Lindner (DL2RUM) has released the latest version of RUMlogNG for direct download or via the App Store.
RUMlogNG is a HAM radio logging, QSL handling and printing tool, especially made for the short wave DXer, made by a DXer. Basic logging features are included for the higher bands up to 1.2 cm and for satellite. RUMlogNG can handle an unlimi ...
https://machamradio.com/blog/2025/07/19/rumlogng-version-5-19-5-released/
HAMRS Pro 2.42.1 released
HAMRS is a simple, multi platform, portable logger designed specifically for portable activities, like Parks on the Air (POTS), Summits on the Air (SOTA) Field Days, and more. HAMRS is available for macOS, Windows, Linux, Raspbian and for iOS devices. Download the latest version here—it’s fast, has a bunch of new features, and auto-updates itself.
Please ...
https://machamradio.com/blog/2025/07/19/hamrs-pro-2-41-1-released/
No Encrypting and compressing files does not always work and especially not if the data is minimal or has compression integrated in the data format – not new but always funny in your own projects.
```tracing
2025-07-19T08:01:20.550231Z INFO myproject: 
file encrypt in 210 bytes
2025-07-19T08:01:20.550610Z INFO myproject: 
-770.00% file compressed
```
Continued thread
Looking north, towards the old Comox Logging & Railway log dump and breakwater. Town of Comox across the bay. At one time during its history the CL&R was the largest private railway operation in the British Empire.
Hacker News When Root Meets Immutable: OpenBSD Chflags vs. Log Tampering
https://rsadowski.de/posts/2025/openbsd-immutable-system-logs/
#ycombinator #OpenBSD #Logging #securelevel
rsadowski.de · When Root Meets Immutable: OpenBSD chflags vs. Log TamperingRafael Sadowski
Environmental issues sidelined in Tasmanian state election
Less than a week out from the Tasmanian election, the Liberals and Labor have steered clear of announcements…
#Environment #climatechange #DeanWinter #Forestry #Independents #logging #rockliff #rosaliewoodruff #salmonfarming #stateoftheenvironment #tasmanianlabor #tasmanianliberals #TheGreens
https://www.europesays.com/2240226/
plusieurs ressources concernant les pratiques de #logging dans vos applications #Python :
- https://www.dash0.com/guides/logging-in-python tutoriel et conseils sur le module logging (et qq bibliothèques)
- une vidéo sur le même sujet : https://youtu.be/9L77QExPmI0
- une bibliothèque éprouvée pour logguer vos messages sous la forme de messages, pour une exploration avec des outils comme #kibana
www.dash0.comApplication Logging in Python: Recipes for Observability · Dash0Stop debugging with unstructured text Learn to build a robust Python logging system with structured JSON automatic context and full request lifecycle tracking
Imo you should not use technical logging (as in std:out via slf4j or similar) for business functionality like audit logs or reports.
It is too easy for developers to break something accidentally by changing a log statement in the code. You are using a mechanism for business functionality, that was not meant for it. Technical and business stuff get mixed up in the log file or your log aggregator. Logging is much harder to test than explicit APIs.
Where do the weapons & mercenaries come from, those that destabilise the Sub-Saharan Sahel region in Africa?
Who trains the troops of warlords?
Who runs the gold, diamond & rare earths mines that employ child labour?
Who controls logging companies destroying huge swathes of Africa's rain forests?
That's right: The Wagner group, from Russia.
https://www.youtube.com/watch?v=0HgL23XDGyE
#africa #wagner #sahel #russia #mining #childlabour #logging #nafo
Mid-day at the Wrecks, looking east towards Comox across the old booming ground. I knew men who worked here in the 1940s and 1950s. This is where the Comox Valley old growth forest was dumped off railcars and boomed up for Fraser Mills in Vancouver. I knew these men when I was a boy and they were old, white-haired loggers who worked with my father.