28 results for “analog_cafe”
Hey #believeinfilm friends,
If you print at home, you may be familiar with f-stop timing, but devices that make it actually convenient can be expensive.
Darkplug is a $25 f-stop timer app for iPhone that uses a smart home gadget you may already own: https://www.analog.cafe/comments/odu9
Hey #believeinfilm friends,
I spent nearly all of October rewriting the internals of film Q (a web app for inverting film negatives online).
The new version features significant image quality improvements:
- Eliminated highlight/shadow clipping,
- More accurate colours,
- And a new colour correction algorithm.
Plus, fun new UI elements with faster processing speeds.
I explain how and why those upgrades work in today's article: https://www.analog.cafe/r/scanning-film-just-got-easier-mxge
Near the end, I also outline what could take it to the next level and ask for your feedback on future developments.
Thank you all for your support. This would not be possible without you!
"PT has lived in the city for about a decade, and when he wanted to promote his own business, he searched online for a list of bulletin boards where he could post his flyers. Finding no such resource, he decided to assemble one himself. He hopped on his bike and began searching and cataloging what he calls “community work[s] of art.”
Many of them reside in laundromats and cafes across the city. They typically sport homemade ads for cleaning services and music teachers, but these boards represent more than just free marketing. One librarian he spoke to described community bulletin boards as “the First Amendment in action.”
“It’s just so messy, and everyone’s talking over each other. You can put up whatever you want,” PT said.
Described this way, bulletin boards sound a lot like an earlier, more optimistic version of the internet. Now, social media ostensibly fills the same role, but, as in music and literature, PT says people still feel a pull toward the analog version.
“I’ve had more than a few people say it’s almost a ritual where they’ll grab a coffee from the neighborhood coffee shop, walk up, and just sit and look at [the board] instead of doom scrolling,” he said."
https://epicentersf.substack.com/p/where-have-all-the-bulletin-boards
The analog side of my music studio in action! Haha :D
News: Dual Analog makes declaration of identity and ambition with first music video from forthcoming album
City Views on Tour #1405 Analog Berlin Wideangle 75
#photography #cityviews #berlin #kreuzberg #landwehrkanal #cityphotography #streetphotography #analogphotography #filmphotography #minolta #fomapan200
https://foto.bibra-medien.de/2026/10/23/city-views-on-tour-1405-analog-berlin-wideangle-75/
AnalogMimic (0.1.0) by tkgktyk
➡️ https://github.com/tkgktyk/analog-mimic-arduino
Controls the Analog Mimic programmable analog module over I2C.
Vintage Tones on a Budget: Why We Love Kodak ColorPlus 200 https://petapixel.com/2026/10/23/vintage-tones-on-a-budget-why-we-love-kodak-colorplus-200/ #Reviews #Analog
#ITByte: Great Sky’s #Superconducting #Neuromorphic #AI chip is an analog brain-inspired #Processor designed to analyze high-speed data from nuclear fusion reactors and large-scale AI infrastructure.
https://knowledgezone.co.in/posts/Superconducting-Neuromorphic-AI-Chip-6adb124c62f261c3f18a60c0
https://www.europesays.com/ie/749590/ New disclosure rules expose big gap between Analog Devices’ Irish tax charge and sum paid – The Irish Times #Accenture #AnalogDevices #Apple #Business #CorporationTax #Éire #EU #IE #Ireland #Microsoft #tax
Immidiate Synthwave by Glitchedtones 🎹
24 synthwave kits (12 keys), 72 MIDI files, 96 WAV loops, 24 Cthulhu presets. 756MB.
🎁 FREE (reg. $20) until Nov 6, 2026
🔗 Link in bio!
PS4Bluepad32 (1.0.1) for esp32 by Pham Thanh Tuyen
➡️ https://github.com/phm-tuyenn/ps4-esp32-lib
Read DualShock 4 buttons and analog inputs using Bluepad32.
Was gonna get fancy for Mom with a set of noise canceling Bose headphones and a Bluetooth audio sender for the Roku TV…
But that’s one more thing to charge, one pairing that can fail, one gadget to plugin…
Did ya know a 35 foot analog audio cable is $17?!?!
Simple tech for the win!
Finally got my Casio G-SHOCK (GA-2100) hands adjusted properly. Hold "ADJUST" for 5 seconds until "SUB" flashes, adjust the day-of-week pointer to point to SUnday, then adjust the analog hands to 12:00, and exit. The analog machinery then steps to the correct time of day and day of week!
Jetzt fix: 2027 kostet die Jahreskarte für die Wiener Linien 483,10 Euro
Der städtische Verkehrsbetrieb hebt die Preise aufgrund der Inflation ab 1. Jänner 2027 an. Ob man Jahreskarten digital oder analog bezieht, macht preislich keinen Unterschied mehr
#PHTV73: This isn't another glorification and/or lamentation post of the oldest TV network. I've heard like that years already.
And now they have 30 days of analog transmission.
https://timowsturf.wordpress.com/2026/10/23/phtv73-counting-down-going-down/
Tilecrawling in Pocket Starforged.
Inspired by the beautiful illustrations by u/FrankReady on r/RPG_Illustrated (e.g. https://redd.it/1www9g3 ), I learned about @capacle 's #tilecrawling idea, and wanted to try drawing some tiles based on my own #IronswornStarforged sessions. I also recently learned about the awesome #artist_trading_card format, and this was a perfect match for both. And it worked way better than I imagined and than I thought I could be able to, which has me really quite proud and excited! ☺️ In the pic you can also see my Pocket Starforged set that I used to play the actual sessions.
#ttrpg #solorpg #illustration #sciencefiction #rpgart #sketch #traditionalart #handmade #humanart #scifi #mastoart #fediart #theWorkshop #analog #blackandwhite #blackandwhitedrawing #pendrawing #drawing #drawtober
New Signal Check is live: Episode 205 - October 23, 2026. This episode covers critical PHP vulnerabilities already being exploited in the wild, a zero-day in Arista's SD-WAN platform, and the unsettling rise of fully autonomous AI agents scanning and breaching websites without human oversight. Adrian also touches on the NYC Marathon as a grounding analog counterpoint to the digital chaos—because sometimes the best security is just putting one… Listen: https://share.transistor.fm/s/e080cb3f
Oh Wonder ▶️ MAD WORLD
London’s beloved indie-pop royalty Oh Wonder have officially broken a four-year studio silence to deliver a profound, cinematic masterpiece: «Mad world», released today (October 22, 2026). The Anatomy of an Analog Rebirth: Stepping away from digital overproduction and shifting trends, Anthony and Josephine Vander West retreated to their creative sanctuary, H I G H W A T E R, to forge a stunning new sonic chapter. «Mad world» places pristine piano chords and gorgeous string arrangements […]https://musicwayatx.com/2026/10/22/oh-wonder-%e2%96%b6%ef%b8%8f-mad-world/
`Argument using analogy is just a tool bro`
---
Amazing that #TNG established the analogy between the warp/subspace crisis and the #anthropocene decades ago and still neither timeframe has done jack shit.
The Joe Tidy controversy is exactly why I don’t advertise myself as a ‘cyber expert’, rather a ‘cyber regulation/policy person’.
Because I don’t want to convey the impression that ‘I am a go-to voice on cyber’, versus ‘I have deeply studied cyber regulation as a PhD’.
Defence analogy:
Imagine claiming to be a fires expert/fires-focused journalist but not having heard of nitrocellulose.
Yes, this is a hill I will die on (and die mad about, because there's nothing that's gonna change it now)...
Internet != internet.
There's a generational breakpoint where the only meaning of "internet" is "wifi access", and in fact "wifi" means access to the Internet. Whereas the geeks and the older folks think of "wifi" as the last-feet layer-two transport / auth / etc only.
Put another way, analogy from electricity:
"internet" = "is the power on in my home"
"Internet" = "is the overall electrical grid OK"
... and The Youts make no distinction between the two.
So when 404 Media's headline says "is the internet cooked?", they really should say the Internet, not the internet.
Docker can look intimidating at first.
Images, containers, volumes, networks, registries, Dockerfiles...
The basic idea is actually simple:
Package an application together with the environment it needs to run.
The "Works on My Machine" Problem
Imagine your application requires:
Node.js 22
MongoDB
Specific npm dependencies
Environment variables
A teammate might have:
Node.js 20
Different MongoDB version
Different operating system
Problems appear.
Docker helps standardize the environment.
Dockerfile
A basic Node.js Dockerfile might look like:
FROM node:22
WORKDIR /app
COPY package*.json ./
RUN npm install
COPY . .
EXPOSE 3000
CMD ["npm", "start"]
This describes how the application environment should be created.
Image vs Container
An image is the packaged blueprint.
A container is a running instance of that image.
Think:
Image = Class
Container = Object
It's not a perfect analogy, but it's useful for beginners.
Docker Compose
Multiple services can be defined together:
services:
api:
build: .
ports:
- "3000:3000"
database:
image: mongo
Now your development environment can include both the API and database.
Why Developers Should Learn Docker
Even if you don't become a DevOps engineer, Docker helps with:
Final Thoughts
You don't need to memorize every Docker command.
Start by understanding:
Dockerfile
Image
Container
Volume
Network
Compose
Those concepts will take you surprisingly far.#docker #devops #containers #development #software #coding #engineering #inclusive #community
Docker for Developers Who Don't Want to Become DevOps Engineers
----------------
🛠️ Tool: PacketSmith v5 Integrates Yara-X into Network Traffic Analysis
===================
PacketSmith from Netomize shipped version 5, codenamed Pinus strobus, and the headline feature is an integrated Yara-X engine. The vendor describes the release as the result of extended R&D for network detection engineers, SOC analysts, and malware and vulnerability researchers, adding "unique, unparalleled" capabilities. Marketing aside, the integration itself looks substantive: Yara-X is not only pointed at payloads, it is wired into a structure of protocol attributes that the compiler can reference.
Key features
• Scoping across data categories: raw frames, individual TCP/UDP packets, reassembled TCP/UDP streams, and ICMP (v4/v6) payloads.
• Deep protocol attributes provided as custom Pattern Identifiers (PaIDs), nested identifiers that let rules target network metadata instead of raw bytes only.
• Cross-layer correlation: a single YARA condition can reference link-layer, network-layer, and transport-layer dissected data simultaneously.
• Results as high-detail console output, JSON, or XML Workbook, with the option of logging matched content.
Technical implementation
The dns case study is the most concrete part of the announcement. It targets the Denis backdoor, publicly documented by Kaspersky on Securelist under "Use of DNS tunneling for C&C communications".
Sample indicators:
MD5: 1a4d58e281103fea2a4ccbfab93f74d2
SHA-1: 1a2cd9b94a70440a962d9ad78e5e46d7d22070d0
SHA-256: f5872f49943c39b73026fc3982b85330953a138cc27c23487a28103337bfdbb5
Win32 EXE, Microsoft Visual C++, 179,202 bytes
Detected behavior: the malware sends check-in DNS requests to Google's public resolver 8.8.8.8 on port 53, base64-encoded with the custom alphabet [A-Za-z0-9_-], and the initial check-in consists of one tunneling label at a fixed 32-byte length. The vendor ships a reference capture (denis_bkdr_dns, 2,292 bytes) together with a sample rule combining ip4 and dns PaIDs. The rule condition shown:
dns.is_set and not dns.over_tcp and not dns.flag.response
and dns.flag.opcode == 0
// optional check:
ip4.is_set and ip.dst.addr == "8.8.8.8"
Use cases
1. Detection engineering against known malware captures, where rules are validated directly on pcaps.
2. Tunneling signatures built on protocol structure, which holds when payload content is encrypted, since the pattern lives in field shape, resolver choice, and flag combinations.
3. Offline pcap triage. The vendor's own analogy: PacketSmith plus Yara-X is to a pcap what an IDS/IPS is to live traffic.
Limitations and open questions
• The claim that no other tool on the market has this capability is vendor-provided and unverified.
• The post demonstrates only the ip4 and dns PaIDs. The announced protocol list at other layers is larger, but per-protocol identifiers require the official documentation.
• The sample rule is tailored to this sample's fixed 32-byte label, so expect tuning for other tunneling families and false-positive pressure from legitimate long DNS labels.
• The release material is framed around pcap analysis; nothing in the post describes high-volume live traffic handling.
References
• PacketSmith official documentation, with technical specifications and advanced use cases for identifying malware C&C traffic and network exploitation attempts.
• Kaspersky Securelist: Use of DNS tunneling for C&C communications.
🔹 tool #PacketSmith #YaraX #NetworkDetection #DNSTunneling
🔗 Source: https://packetsmith.ca/yara-x-packetsmith-detection-module/
Write or be written off
I’ve written before about why I write and why it’s important for personal and work reasons. I often use it to sense make and it inspires me. I’ve not been as purposeful of late and a lot of it has probably to do with AI. As you can imagine, AI makes it a lot easier to choose it to write for you, rather than do it yourself. It makes you lazy. This is my recommitment post, to my own writing.
I’ve started reading On Writing Well by William Zinsser, this fired me up. He said, “the act of writing generates some cluster of thoughts or memories that you didn’t anticipate. Don’t fight such a current if it feels right. Trust your material if it’s taking you into terrain you didn’t intend to enter but where the vibrations are good. Adjust your style accordingly and proceed to whatever destination you reach. Don’t become the prisoner of a preconceived plan. Writing is no respecter of blueprints.”
I share that not in support of the title of this post, I’ll get to that. What he wrote is more about the act of writing well and how to go with the flow if it is to work. It reminded me why I love writing for the pleasure of it. When it creates a state of flow and the effort becomes effortless, you enjoy it and the writing is better for it. You’re better for it too – there’s nothing more satisfying than punching out some powerful prose or getting an intended reaction from someone.
But there is also the connection to living for which writing is a wonderful analogy. And especially William’s point about what the act of writing instils in you.
There’s something about getting your words down on a page or screen that is life affirming. I like to believe that “I write, therefore I am”, to paraphrase. It’s not so much an affirmation of existence as it is simply a way of actualising lived experience. When you write what you know based on what you’ve done, it adds a certain concreteness to life.
In the same breath, Michael Pollan said, “don’t write if you know the answer”. Writing is one of the best ways to improve your critical thinking. This is needed for the right learning. Writing is subsequently an excellent way to solidify what you have learned. It reinforces learning because it forces your brain to slow down, organize thoughts, and process information deeply.
I’m making a lot of these points in the context of AI use and how, if we’re not careful, we’ll lose the ability to write and thereby lose all of the benefits it brings.
Reading is a closely related cousin and is in a similar predicament for other reasons. Reading levels have gone down drastically in recent years with social media doom scrolling replacing it.
The casualties in all of this is us. Whatever the causes, we cannot stop doing the things that make us human. The ability to read what others have written and reflect and learn from this and vice versa. And to think rationally and critically as a result, with a deep connection to others so that it grounds our actions. This is not something we should easily give up to algorithms and AI.
#inspiration #writing #reading
Introduction
On October 21st, at 07:41 UTC, Chainguard unilaterally breached a coordinated disclosure embargo by releasing a PHP security patch more than six hours ahead of the agreed schedule. This premature disclosure exposed critical vulnerabilities in cybersecurity collaboration, undermining weeks of meticulous coordination among stakeholders to synchronize vulnerability disclosure. The PHP community, which had shared the patch with distributors like Chainguard under strict embargo terms, sharply criticized the company for jeopardizing the security of a significant portion of the web. By releasing the patch prematurely, Chainguard enabled malicious actors to analyze the binary fix before widespread deployment, creating an exploitable window.
The causal mechanism of risk escalation is clear: Chainguard’s embargo breach introduced a temporal disparity between the patch’s public availability and its deployment by end-users. This gap provided attackers with a critical opportunity to reverse-engineer the patch, pinpoint the underlying vulnerability, and develop targeted exploits. During this interim period, PHP users remained unprotected, as the official disclosure—intended to align with patch availability—was delayed. This misalignment significantly heightened the risk of exploitation, effectively nullifying the protective purpose of coordinated disclosure protocols.
This incident exposes systemic vulnerabilities in the enforcement of cybersecurity embargoes. Unlike legal embargoes, which are backed by enforceable penalties, coordinated disclosures in the tech industry depend on trust and voluntary compliance. Chainguard’s actions underscore the absence of formal repercussions for violations, revealing a system susceptible to conflicts of interest—such as distributors prioritizing their own user base over the broader ecosystem. Without robust deterrents, such breaches risk becoming normalized, eroding trust among researchers, distributors, and users. This erosion threatens to fragment the unified response to critical vulnerabilities, leaving the global web infrastructure increasingly vulnerable to rapid, large-scale exploitation.
The implications are stark: if coordinated disclosure processes fail, the global web infrastructure becomes more susceptible to widespread, rapid exploitation. This incident highlights the urgent need for stricter adherence to embargo protocols and the establishment of clear, enforceable consequences for violations. Strengthening these mechanisms is essential to ensure that collaborative security efforts are not compromised by individual actors, thereby safeguarding the integrity of vulnerability management practices.
The Security Patch and Coordinated Disclosure
In cybersecurity, coordinated disclosure serves as the cornerstone of responsible vulnerability management. This process is a meticulously timed sequence where researchers, developers, and distributors align the release of security patches with the public disclosure of vulnerabilities. The objective is clear: to provide users with a critical window to update their systems before malicious actors can exploit identified flaws. This mechanism operates as a high-stakes race against time, where adherence to agreed timelines is paramount—deviations can precipitate catastrophic outcomes.
Chainguard’s Breach of Protocol
On October 21st at 07:41 UTC, Chainguard unilaterally released a PHP security patch six hours ahead of the agreed embargo, constituting a critical failure in the coordinated disclosure process. This breach unfolded through the following mechanism:
The Causal Chain of Risk Amplification
Chainguard’s actions initiated a cascading sequence of events:
This sequence is not speculative. In cybersecurity, time is a quantifiable resource—each hour gained by attackers corresponds directly to increased user exposure. Chainguard’s breach effectively granted attackers a tactical advantage, nullifying weeks of coordinated preparatory efforts.
Systemic Implications and Structural Vulnerabilities
Chainguard’s actions underscore a fundamental weakness in cybersecurity embargoes: the absence of enforceable penalties. Coordinated disclosure operates on a framework of trust and voluntary compliance, rendering it susceptible to organizational priorities. Key implications include:
The conclusion is unequivocal: coordinated disclosure is not merely procedural—it is a critical mechanical safeguard for global cybersecurity. Violations of this protocol do not merely bend rules; they destabilize the entire system. To safeguard digital infrastructure, stricter adherence to protocols and tangible consequences for non-compliance are imperative. Absent these measures, we jeopardize not just individual patches, but the resilience of the entire global network.
Impact and Reactions
Chainguard’s unauthorized release of a PHP security patch on October 21st at 07:41 UTC—six hours and eleven minutes ahead of the coordinated disclosure schedule—directly compromised the integrity of global vulnerability management. This breach not only violated established cybersecurity protocols but also triggered a cascade of technical and systemic consequences, exposing millions of PHP users to heightened risk. The following analysis dissects the immediate and long-term ramifications of this action.
Immediate Technical Consequences
Upon Chainguard’s release of the binary patch, malicious actors gained a critical window to exploit the vulnerability. The reverse-engineering process—which involves disassembling the binary into machine code, performing differential analysis against prior versions, and mapping code changes to identify patched vulnerabilities—was accelerated. Mechanistically, this process mirrors forensic code analysis, enabling attackers to reconstruct the vulnerability’s root cause with precision. The temporal gap between Chainguard’s release and the official disclosure provided attackers with a tactical advantage, allowing them to develop and deploy exploits before the majority of PHP users could apply the patch. This scenario is analogous to a security breach in which an adversary gains access to a system’s blueprints while its defenses remain unactivated.
Reactions from the PHP Community and Experts
Long-Term Implications
If such breaches become normalized, the coordinated disclosure framework risks collapse. This erosion of trust manifests in the following systemic consequences:
Mechanisms of Risk Amplification
The risk amplification resulting from Chainguard’s actions can be modeled as a causal chain:
Practical Insights
Chainguard’s breach underscores the necessity of enforceable consequences for cybersecurity embargo violations. Without penalties—whether legal, financial, or reputational—organizations may prioritize narrow interests over collective security, akin to disregarding traffic laws for personal convenience. Strengthening protocols to include binding enforcement mechanisms is essential to safeguarding global web infrastructure. In cybersecurity, time is a quantifiable resource; its misuse through protocol violations directly correlates with increased user exposure. Addressing this gap requires systemic reforms to restore trust and ensure compliance with coordinated disclosure frameworks.
Lessons Learned and Strategic Reforms
Chainguard’s unauthorized release of a PHP security patch prior to the agreed disclosure timeline underscores the fragility of coordinated vulnerability disclosure (CVD) mechanisms. This incident not only exposed systemic weaknesses in embargo enforcement but also amplified the risk landscape for millions of PHP users. The following analysis distills critical insights and proposes actionable reforms to fortify global cybersecurity practices.
Critical Insights
Strategic Reforms
Proactive Mitigation Strategies
To preempt future breaches, the cybersecurity community must address the root causes of embargo violations through systemic, educational, and technical interventions:
Chainguard’s breach serves as a critical inflection point for the cybersecurity community. By addressing the structural vulnerabilities exposed in this incident, we can reinforce CVD frameworks, safeguard global web infrastructure, and ensure that time—a decisive factor in cybersecurity—is not weaponized against users. The path forward demands not just technical innovation, but a recalibration of norms, incentives, and governance to prioritize collective resilience over individual expediency.#cybersecurity #embargo #vulnerability #exploitation #software #coding #development #engineering #inclusive #community
Chainguard's Premature PHP Patch Release Undermines Coordinated Disclosure, Increases Risk for Users