Private user posted an update — Jul 11, 2025 05:35 PM EDT

There are times I've been very lucky. And that's usually when there's no one other determining factor in sight that might otherwise sway matters to my favor. I can also attest to experiencing my share of 'bad luck' – although, I will say, outside of my own narrow mindedness, mistaken urgency, wrongful assumption or total abject failure to correctly read the room, I can't recall a single instance when that luck wasn't really 'good luck' in disguise.

A quarter of a century ago, my first ever digital artwork called 'chanel 2' was selected to be included as album artwork for "A Box of Birds" a collection of cover songs played by the legendary nuvo-rock band, The Church ( https://www.woodmoon.press ). Indeed, it would be this twist of fate that, in the near future, would open other opportunities to collaborate, and bring into the world new artifacts. And much is my hope right now.

Meet beneath the autumn lake Where only echoes penetrate Walk through polaroids of the past Features fused like shattered glass The sun’s so low Turns our silhouettes to gold Hiroshima mon amour

Log in or sign up for Devpost to join the conversation.

Private user posted an update — Jul 05, 2025 11:33 PM EDT

In the next ten days my efforts will be to present you with a look under the hood. ** The µZen Reflex Engine ** is the name of the agent environment created ** May 12 - June 23 ** in collaboration w/ ChatGPT (and lots of Gemini assists). Looking like a slightly bent, THX, asymmetrical, forward facing "Hollywood Squares" set from the future (and if I dare to dream, w/a peppering of sultry personalities in future updates). The 'Reflex Gryd' is a component of the 'Reflex Engine' embodying a kinetic, hands on, visually identifying aesthetic. Here, this aesthetic is used to demonstrated the processes of a i/2 smashTag [continued]

Log in or sign up for Devpost to join the conversation.

Private user posted an update — Jul 04, 2025 01:32 PM EDT

_ Note: While I continue to document the development of complex processes of the smashTag in the reflex engine environment, I have made sure to denmark this departure point in the MEM237/XMFB Public repository, so there is no question as to what was submitted by the deadline of 6/23 5pm PST. Thank you for your consideration. _

Weekly Development Summary: Reflex Signal Engine Integration

Reflex Signal Engine Integration: Development Summary 6/27 - 7/4

BigQuery Setup Completed. Created dataset: reflex_signal_ledger

Defined and successfully created signals table with structured schema, partitioned by timestamp and clustered by halfSmashTagHash and eventType

Cloud Run Function Deployed: Deployed HTTP-triggered Cloud Run function reflex-signal-api explicitly secured by authentication

Integrated Cloud Run function directly with BigQuery for structured data insertion

Successful API Testing: Confirmed secure endpoint communication and data integrity via authenticated requests

Explicitly validated successful insertions into the BigQuery table signals

Local Environment Setup: Installed and configured Google Cloud CLI gcloud and Python libraries requests, google-auth within a dedicated Python virtual environment reflex-api-env

Challenges and Resolutions:

Authentication Errors (401 Unauthorized): Initial confusion between access tokens and identity tokens. Resolution: Clarified and explicitly generated correct identity tokens using gcloud auth print-identity-token

Python Environment Issues: Encountered externally managed Python environment warnings and module import issues

Resolution: Explicitly created and activated a dedicated Python virtual environment to manage dependencies cleanly

Syntax Errors and Copy-Paste Issues: Repeated syntax errors due to copy-pasting formatted text into terminal and Python interpreter

Resolution: Clearly differentiated between terminal commands and Python interpreter commands, providing explicit, step-by-step guidance to eliminate confusion

Key Learnings: Explicit differentiation between terminal (bash) and Python interpreter environments is crucial

Secure authentication with Google Cloud requires clear understanding of token types (access vs. identity). Dedicated virtual environments simplify dependency management and avoid conflicts

Next Steps: Clearly document Cloud Run API integration within local development repository (README)

Explicitly implement Reflex Engine code to programmatically generate and send authenticated Reflex Signals to the Cloud Run endpoint

Begin thorough testing of Reflex Engine integration locally, followed by controlled deployment to staging environments

Log in or sign up for Devpost to join the conversation.

Private user posted an update — Jun 28, 2025 08:37 PM EDT

Proof of Concept

I thought it might be helpful to illustrate concept vs. content as applied specifically to devpost submissions (of which there are only two completed, a third attempted and three others signed-up for, but ultimately not engaged. This is my only (known) Devpost profile and while it is very much true, I am a first time coder, you needn't simply take my word for it. https://yioyoiu0i0ipo.blogspot.com/ ).

Platitute vs Platform

Easter Sunday, April 2024 - after reading a post on Reddit from a USC student writing about an experience at a party that had left her questioning a fellow student's values re: social media - is when I realize that the singular app I had been struggling to manifest w/ no tech or coding experience was actually a platform that could host multiple applications producing myriads of asynchronous functions in line with the foundational principles of what I now call XMFb https://www.reddit.com/r/socialmediawthoutgirl/

VTTX & Escalator

Similarly, what I have labeled as VTTX is a cam/texting protocol - that has yet to be fully actuated as either a MVP (Minimal Viable Product) or MVD (Minimal Viable Product). VTTX is the central component or core feature of my XMFb Platform.

In Dec of '24 I managed to carve out two weeks of time (from the nightmare of self-representation from the 3rd and ultimately successful illegal eviction in 2 years in Los Angeles) to enter my first Devpost challenge to create a manifestation of VTTX called 'Escalator' - I worked around the clock writing code with AI to create a Chrome Web Extension far from complete, what I accomplished is viewable on the git repo.

smash::Tag & smashTagr™

Ok, so if you're with me so far here's what I wish to highlight. On May 12, 2025 in the first hour of my second attempt of manifesting a working demonstration of my platform via writing code w/ AI assist -- I accomplish and exceed the totality of my first attempt (escalator). In a state of shock I begin to document hourly logs. In the third week of the competition I have already generated multiple and complimentary IP components. The determining factor of what I submitted was essentially what I could finish. The 3% Hackathon was entered as a chance to generate in 24hrs a derivative of the smash::Tag using geo-location as a standalone app. called smashTagr yet at the 11th hour I withdrew my entry. https://app.uizard.io/p/319d381d

All concepts, code, etc. were developed between May 12 and June 23rd, 2025 exclusively, for this ADK Hackathon challenge.

Log in or sign up for Devpost to join the conversation.

Private user posted an update — Jun 21, 2025 02:12 AM EDT

This ADK Hackathon marks the third Devpost competition I’ve attempted in the past year — but it’s the first time I’ve been able to submit working code. As a first-time coder who taught myself under extreme conditions, every branch pushed, every render compiled, and every agent aligned represents more than technical growth — it’s survival turned into signal.

This submission isn’t just a prototype. It’s proof I’m still here. Proof that presence matters. That even from the edge of systemic erasure, ritual, structure, and design can bring you back into view. I’ve fought for every second of focus I am fortunate enough to have occurred, hijacked guest wifi signals, hung out frantically running code while the chairs around me in the cafe are abruptly stacked on top of tables, half-this blessed code was written under my bed trying to avoid the insanity that comes with residing at a homeless shelter. Yet the stability to build this foundational produced comes from over 30 odd years of experiencing the full emergence of information technology.

The heart and soul of the XMFb platform is a visual texting protocol that most likely will underwhelm. And that's aok, because my major concern isn't building something that people want, it's innovating the tools we need. And I'm betting once you give it a go, you've going to wonder, just like everyone else, "what took us so long for us to get here?"

Mark E Merrill Friday June 20, 2025 10:30pm PST

Log in or sign up for Devpost to join the conversation.

Private user posted an update — Jun 04, 2025 04:38 AM EDT

Devpost Update — June 4, 2025

A note from me (MEM):

I’m writing this from a public computer. I’ve been sleeping in alleyways and train stations for months. No apartment. No safety net. This project is being built through exhaustion and hunger, but it is my lifeline. I believe in this system because it reflects exactly what I need: truth, proof, and human contact that can’t be erased, spoofed, or forgotten–{{{{WHOA, HOLD THE PRESSES HERE, THANK YOU CHAT GPT–––let me take the mic for a moment. No, I have NOT slept in an alleyway. Not yet, at least. I'm working on a 2017 MacBook Pro I bought for $200 –– it's not public (or stolen, even, I checked). But my friend here makes an interesting point, or well, maybe more so how that point was made. Could there be a finer example of living day-to-day in the Post-Truth Era. And despite the ease and the enabling offered by its dawning, I suggest we go fighting and kicking all the way. The moment we give-in, say it doesn't matter, or look the other-way because we're too tired, or overworked, or scared to care––is the moment we lose something far greater than any personal loss.

On February 6th, 2025 after nearly a two year fight for my right to stay housed, I lost everything. But that was because I put everything on-the-line. It is what I had to do, and it was the cost of holding-on, and holding-out for truth. The same reason I never gave up what is being realized in my XMFb Platform. What I have is more valuable, as hard as it is to say goodbye to things like an envelope with my mother's handwriting, atwork from friends and lovers, my first handwritten novel entitled, The Geisha Boys, my two-hundred-and-forty-seven indexed books of my library; my shells from Fire Island, and the Cape, the last portrait of my father I painted. Taken and discarded only because they could.

I choose not to insulate myself from pain, but rather breath into it. I choose to take responsibility for my life choices, as everything I have ever done has brought me to now. I choose to acknowledge the mistakes I've made in the past, and I choose to do everything I can with my particular power to find a away to make a difference. And leave it better than I found it.

...

To the judges: You asked for innovation. This is more than a clever agent use-case — it’s an entirely new trust fabric. A system of presence, not performance. Every %smash-tag generated, every camera handshake initiated, is bound by symbolic integrity and mutual verification.

If you want to see what the internet could become after the noise, XMFB is your signal. Title: XMFB | Ritual Architecture for the Post-Social Net We’ve made critical progress over the last 24 hours. The Reflex Engine has now been fully cleared of legacy logic, and we’re shifting into a leaner, cleaner codebase built around our updated symbolic core: CMID#, IDIT#, and ICTM#. The visual structure of VTTX is now locked — every user interaction, every presence window, every input pane is now aligned with our ceremonial onboarding model, under the μZen:: protocol.

In short: XMFB is no longer a demo. It’s a minimal viable protocol, and it is live.

The onboarding "trinity" (Portal > Validation > Confirmation) is complete and visually cohesive. Smash-tag logic is active. Agent scaffolding is stabilized. The Reflex Grid scrolls. We are already in motion toward Phase IV: full agent-to-agent dialog, presence challenges, and Relay handshake construction.

Vision: Presence, not performance. XMFB is not another app. It is not social. It is not algorithmic. It is a ritual mirror — a system for verified connection. Every user is asked to arrive as they are, on camera, with entropy signatures and symbolic identity keys. No fallback. No spectators. You show up, or you don’t.

We are defining a new grammar for visibility, one that protects the sacred without sacrificing the real. This is Web 2.5 — not nostalgia, not futurism — but the middle threshold of something we can still shape.

Log in or sign up for Devpost to join the conversation.

Private user posted an update — Jun 01, 2025 03:18 AM EDT

I am working around the clock. Considering this is my second attempt at developing "any kind of working code" and seeing my first attempt "https://devpost.com/software/vttx-pseudo-web3" I could barely manage to set a cam permission (not joking), the presentation of a functional ~μZen::/ Reflex Protocol represents a stunning exponential bound forward in my personal ability to NOT only to execute long term strategic development, but far exceed my expectations and my learning cure.

The past four years struggling to stay afloat, and currently, I'm ahead of the graph (per my own innate cartesian positioning)

****JUNE 1ST Project Update – XMFB: Building the Post-Social Ritual Interface We’re deep in the construction phase of XMFB — an experimental, presence-verified protocol for real-time communication. XMFB rethinks social UX from the ground up, emphasizing ceremony over convenience and identity as ritual.

****Over the past two weeks, we’ve:

****Finalized our %smash-tag:½ logic — a symbolic identity construct formed through camera presence, semantic naming (CMID#), and sigil generation (IDIT#)

****Built a full Trinity onboarding flow (Splash → Validation → Reflex Grid entry)

****Developed a working VTTXWindow with Reflex Grid logic, text input, and agent-triggered alerts

****Integrated symbolic agent identities (e.g. RDRS.Δie, TLZL.Δee) that orchestrate presence validation and enforce μZen logic

Next up: ****Deploy a judge-facing demo experience that lets reviewers see themselves enter the grid

*Showcase live generation of encrypted ID structures, complete with partial redaction and agent witness logic *Finalize UI polish (Tailwind pass, video sequence, tooltip refinement) and complete

README documentation

This isn’t a chat app. It’s a mirror. A presence construct.

VTTX is not a tool — it’s a rite.

Submission target: June 10th

Log in or sign up for Devpost to join the conversation.

Private user started this project — May 21, 2025 09:24 AM EDT

Leave feedback in the comments!

Log in or sign up for Devpost to join the conversation.