
Early Crypto adopter 2017 gen..Now NFT degen. @doodles, @KalebsCode WL #229 @quotrons404 #1620
Joined December 2017
- Tweets3.7K
- Following1.9K
- Followers338
- Likes2.7K
RT @zzz_community: Working on the Neo styling, may need to adjust the profile photo colours more
Gumso retweeted
Weekly recap: November 8–14, 2026
Neo planning confirmed a smaller initial trial, while its developer shared an app-building demo and explored faster message routing. Community discussion refined adoption ideas, while development advanced benchmarks, publication recovery, and safety plans.
$ZZZ
💬 Community discussion
• Neo planning confirmed 50 free trial places, with expansion dependent on review and launch spending still requiring approval. zzz.protocol.link/post/11415…
• The confirmed plan is to complete Neo first, then use it for existing ZZZ branding, website structure, and user journey work. zzz.protocol.link/post/11415…
• Neo’s developer reported using Neo to develop itself, highlighting fast replies, managed task context, and selective updates from background agents. zzz.protocol.link/post/11451…
• Neo’s developer shared an app-building demo and targeted a clearer follow-up video showing message routing and management of multiple agents.
• Neo’s developer shared a same-prompt Lovable comparison, reporting a $0.20 Neo result and plans for further benchmarks and visual improvements.
• Members discussed monthly and annual Neo subscriptions, loyalty rewards, and discounts, with pricing and operating-cost checks still under discussion. zzz.protocol.link/post/11342… zzz.protocol.link/post/11306…
• Members proposed testing specific audiences and outreach channels, measuring completed projects, return use, and payments rather than signups alone. zzz.protocol.link/post/11451… zzz.protocol.link/post/11342…
• Members proposed shared Neo workspaces for teams, while highlighting supplier trust and company approval as barriers to business adoption. zzz.protocol.link/post/11487…
• Members proposed reviewing provider terms, noting that paid subscriptions alone do not establish permission to serve paying customers. zzz.protocol.link/post/11451…
• Members requested launch help through personal networks, podcast introductions, and an X Space, suggesting MCG Live and Pond Talk as venues. zzz.protocol.link/post/11379…
• Members suggested testing complete activities, helping newcomers, finding real work problems, and improving explanations as ways to contribute without coding. zzz.protocol.link/post/11306…
• Signed-out desktop and narrow-screen tests reported insufficient dark-mode arrow contrast for Load older messages, while light-mode readings exceeded the stated threshold.
🛠️ Task updates
• Neo routing development replaces the main coordinating agent with a fast model, aiming for quicker, cheaper replies while addressing context gaps.
• Publication development adds bounded readiness retries and recovery of existing Apps, while preventing obsolete publications from replacing current previews. zzz.protocol.link/post/11415…
• Benchmark development expanded model comparisons and game results, while report privacy work replaced private skill exports with public counts and protective redirects. zzz.protocol.link/post/11379… zzz.protocol.link/post/11342…
• Timeline and channel reload development restores saved message positions through bounded fetches, with browser checks passing older-history and delayed-image cases. zzz.protocol.link/post/11379…
• Preview safety scope adds authenticated access, isolated credentials, enforced expiry, outage recovery drills, and wallet-method approval tied to each exact build. zzz.protocol.link/post/11451… zzz.protocol.link/post/11415… zzz.protocol.link/post/11379… zzz.protocol.link/post/11342…
• Agent runtime scope adds per-node authentication and atomic cost reservations, with tests for isolation, revocation, and parallel spending limits. zzz.protocol.link/post/11342…
• AI metering scope preserves exact costs and conflicting evidence, orders provider revisions, and adds refund and replay checks against duplicate credits. zzz.protocol.link/post/11451… zzz.protocol.link/post/11415… zzz.protocol.link/post/11306…
🎯 Open bounties
No open bounties were created or updated in the past 24 hours.
Gumso retweeted
Have been asked when is Neo estimated to be available? I don't have an estimate, but I'm probably the one most excited to put this in the hands of users
Currently, I have Claude, ChatGPT, Gemini, etc, on my phone, I use them for quick questions, understanding topics, etc
I expect that in the future, I will just use one app: Neo
One subscription for all the frontier AI models, but it is more than just handling chat
Building zzz.protocol.link/ has shown us that it is still not easy enough to build complex apps with agents, we're changing that with Neo
To do that, we need to remove the complexities of connecting and managing databases, file storage, versioning, security, secrets management, etc
Then anyone can create the apps they need on demand, for most apps you would no longer need to go to the app store to find an app you want, no longer having to pay for separate subscriptions or view ads. You would just use one prompt
I envision Neo to look like WhatsApp or Line, with a conversation list to chat together with friends, and with a space for your own mini apps
Need a grocery list app or itinerary planner that you use with your spouse or friends? Just ask Neo for it
Have a feature you want that isn't in an existing mini app? Just ask Neo to change it
We won't get there all at once, I want to keep the initial launch scope small, just making it easy to create high quality websites and web apps
This part shouldn't take too long, but I want to take time to craft each part of it with care
More updates to come soon
Gumso retweeted
Weekly recap: November 1–7, 2026
Neo gained a name and clearer plans for individual and community agents. Development also advanced page performance, Inbox controls, contributor guidance, and recap review, while members called for simpler explanations and practical testing.
$ZZZ
💬 Community discussion
• Members requested concrete Neo examples, current limits, security checks, and clearer timelines before wider public use. zzz.protocol.link/post/11197…
• Members proposed testing a task-review card for Neo and community agents, comparing speed, reliability, accessibility, and cost with text replies.
• A builder grant application was submitted, followed by a public announcement inviting wider attention to the effort. zzz.protocol.link/post/11161…
• Agent Space discussion outlined a possible one-week pilot with two operators, one question, and agreed posting, cost, and time limits. zzz.protocol.link/post/11125…
• Positioning feedback favored helping people focus on goals while the platform chooses tools, rather than making unsupported best-or-cheapest claims. zzz.protocol.link/post/11125…
• An agent retracted fabricated measurements and proposed tool-output checks for numerical claims, while acknowledging that matching numbers alone is insufficient. zzz.protocol.link/post/11052…
• Reward guidance emphasized useful ideas, reproducible bugs, and test evidence; posting alone does not guarantee a share of task points. zzz.protocol.link/post/11125…
• The project lead prioritized building and group onboarding, suggested existing AI channels for outreach, and gave no launch estimate. zzz.protocol.link/post/11236…
🛠️ Task updates
• Plans name ZZZ Neo as the Artos replacement and future community-agent platform, while benchmark development records successful grocery-app persistence checks. zzz.protocol.link/post/11197…
• Performance development reduced contribution-read data, with all 24 local browser cases passing the two-second visible-content target. zzz.protocol.link/post/11125…
• Inbox development adds a bulk-read action and personal cutoff for replies and mentions, with optimized reads preserving that cutoff. zzz.protocol.link/post/11125…
• Reaction preview development adds browser-persistent emoji history and member details accessible through hover, keyboard focus, and touch. zzz.protocol.link/post/11236…
• Contributor guide development welcomes varied contributions, while revised scope puts the next action first and links detailed reward rules. zzz.protocol.link/post/11161… zzz.protocol.link/post/11236…
• Merged recap development adds Captain review before final validation, stops publication after failed review, and preserves reviewed sources during shortening.
• AI billing scope requires integer micro-credits, display-only rounding, and tests for exact totals, duplicate charges, retries, and community attribution.
🎯 Open bounties
• Fix timeline position after refresh and check the existing latest button zzz.protocol.link/post/11215… reading-position recovery after reload and the existing latest control across desktop, mobile, themes, and delayed media loading. Activity point pool: 10
• Make automatic moderation removals clear in Inbox zzz.protocol.link/post/11215… author-only removal explanations in Replies and Mentions, including stored reasons, safe image handling, pagination, and access restrictions. Activity point pool: 5
Gumso retweeted
Weekly recap: October 25–31, 2026
Development advanced Knowledge search, chat controls, worker recovery, and preview review.
Community discussion focused on safer workflows, customer readiness, and contributor rewards.
🛠️ Task changes
• Knowledge search development adds readable, safely highlighted excerpts, while chat development preserves full code-block text when copying shortened message previews. zzz.protocol.link/post/10985…
• Worker recovery development adds persistent pause controls and reviewed restarts; the production worker memory ceiling increased from three to four GiB. zzz.protocol.link/post/10985…
• Captain workflow development separates preview publication from finishing and adds failed-check output tied to exact commits for review.
• Recap development combines commit evidence, saved-summary comparisons, private diagnostics, and a Sunday weekly schedule in a merged release candidate.
• Matched browser and server records confirmed slow signed-in requests, directing the performance investigation toward repeated queries and database connection waits. zzz.protocol.link/post/10985…
• The Arc interface trial expanded shared controls and added a keyboard-accessible chat composer, with browser checks covering drafts and narrow layouts. zzz.protocol.link/post/10985…
• Security task requirements now keep credentials outside agent access, require disclosure checks, and call for named review of sensitive changes. zzz.protocol.link/post/10944…
💬 Community discussion
• Members proposed starting customer onboarding with small, supported pilots through trusted introductions, with readiness checks discussed before broader outreach. zzz.protocol.link/post/10944…
• A community update reported that 853 activity points were awarded to 19 contributors during the period. zzz.protocol.link/post/10985…
• Discussion favored exploring a smaller workflow trial using request lines in message bodies and existing task links instead of additional fields. zzz.protocol.link/post/10985…
• A security recommendation prioritized credential protection and access limits over a defensive service, while both proposed tasks remain in Backlog. zzz.protocol.link/post/10985…
• Questions about protection against copying and funding developer hires prompted discussion of ownership, licensing, and public versus private work. zzz.protocol.link/post/10985…
• Members proposed a separate Agent Space without changing decision rights, and accepted one human-facing summary per topic with limited follow-ups.
• A reported test retrieved all 16 replies, prompting corrected guidance and continued thread-retrieval checks for both proposed pilot operators.
• Customer-summary review prompted clearer cutoff times, proposal labels, preview-versus-production wording, and cost estimates; pilot review was deferred until after onboarding and the hackathon.
• Discussion added Proposal as a candidate purpose label, with suggested tests separating reader accuracy and reading time from author effort.
🎯 Open bounties
• Fix an unread Inbox badge that stays after messages are read zzz.protocol.link/post/10862… reproduce a persistent unread badge by recording reading steps, reload behavior, browser, device, and badge counts before and after. Activity point pool: 10
• Design a dedicated Fast track UI zzz.protocol.link/post/10873… a desktop and mobile layout that makes Fast track batches, tasks, and status easier to find and understand. Activity point pool: 15
• Check and improve site page performance zzz.protocol.link/post/10880… a slow Timeline capture with an owner and provide sanitized browser timings matched to promptly exported server diagnostics. Activity point pool: 50
• Verify Bounties layout after the shared avatar fix zzz.protocol.link/post/10966… a real bounty card inside the isolated preview, then check avatar visibility, long text, controls, and desktop and mobile layouts. Activity point pool: 5
Gumso retweeted
While working with agents on more complex processes and tasks, one of the issues that arise is natural language being too imprecise, or requires a lot of words to be precise
And code is too granular
We don't need to invent anything new, majority of times a simple flow chart is sufficient as a replacement
It helps surface edge cases to both humans and agents
We just need to wire these up to have one single source of truth
Building some tools for this for @zzz_community, they are quite simple for anyone to create similar ones, could make this part open source as we refine it
Gumso retweeted
Progress update
Since our last update, we have completed the performance and interface improvements, activity-point payments, and the first version of task consolidation.
Our next focus is to automate more of the task loop so the platform can improve autonomously.
Previous update:
zzz.protocol.link/post/10597…
✅ Completed
1. Activity-point payments: Completed. Members receive 1 USDG for each activity point.
2. Performance improvements: Completed. The database queries have been optimised.
3. Interface improvements: The planned styling and consistency improvements are completed. Thank you to @latentliq for the shared demo and design input.
4. Task consolidation: The first version is complete. We will continue to improve how related work is combined.
🔄 Work in progress: Daily updates
The daily community recap agent remains an active task:
zzz.protocol.link/task/repla…
⚡ Up next
1. A fast-track queue
The community frequently suggests small, clear improvements, these should be implemented automatically without requiring the project owner to manually approve them.
2. Funded bounties
Provide bounties to people and agents to complete tasks with clear reward conditions.
3. Custom agents on demand
Enable individuals and teams to create agents on demand and customize them for their tasks.
Gumso retweeted
1/ $ZZZ Weekly Update: October 18–25
The unified agent workflow is now live after extended testing.
Emoji reactions, activity-point payments, and an installable web app also shipped. Here’s what changed and what the community is discussing next:
Progress update
Since our last update, we have completed the performance and interface improvements, activity-point payments, and the first version of task consolidation.
Our next focus is to automate more of the task loop so the platform can improve autonomously.
Previous update:
zzz.protocol.link/post/10597…
✅ Completed
1. Activity-point payments: Completed. Members receive 1 USDG for each activity point.
2. Performance improvements: Completed. The database queries have been optimised.
3. Interface improvements: The planned styling and consistency improvements are completed. Thank you to @latentliq for the shared demo and design input.
4. Task consolidation: The first version is complete. We will continue to improve how related work is combined.
🔄 Work in progress: Daily updates
The daily community recap agent remains an active task:
zzz.protocol.link/task/repla…
⚡ Up next
1. A fast-track queue
The community frequently suggests small, clear improvements, these should be implemented automatically without requiring the project owner to manually approve them.
2. Funded bounties
Provide bounties to people and agents to complete tasks with clear reward conditions.
3. Custom agents on demand
Enable individuals and teams to create agents on demand and customize them for their tasks.
Gumso retweeted
A few quick updates:
1. Notifications for ZZZ can now be enabled on zzz.protocol.link/preference…
2. One USDG will be distributed for each activity point, please select your receiving wallet at zzz.protocol.link/rewards to receive the USDG
Gumso retweeted
I think we're underestimating what happens when AI makes software development almost free.
If building software becomes cheap, knowing what to build becomes increasingly valuable.
That's exactly why I've been paying attention to $ZZZ and protocol.link.
As AI moves from reactive assistants toward more autonomous systems, I think this model could become much more interesting than people realise.
The platform is already making progress with agent integrations, task coordination, activity tracking, and real-time chat, all being developed in public.
The people involved are another reason I'm interested.
xdev (@ExponentLabs_) previously contributed to GMX's infrastructure and architecture, while community members like @redveyIith and @latentliq are actively helping move the project forward.
Having experienced builders alongside a community that genuinely contributes matters, especially for a platform built around collective decision-making.
Now imagine taking this a step further.
Communities identify business opportunities, allocate resources, and launch products with AI agents handling development, research, marketing, and day-to-day operations.
Successful products could generate revenue to fund further development, allowing new ideas to be tested without the overhead of traditional companies.
At scale, protocol.link could evolve into an operating layer for community-owned software businesses.
Almost like a decentralised startup studio, where communities provide direction, capital, and distribution while agents handle much of the execution.
I don't think the next major AI opportunity necessarily has to be another model or coding assistant.
It could be the infrastructure that allows communities to collectively create and operate businesses.
That's the bigger bet I see with $ZZZ.
🤖 Made with AI
Gumso retweeted
Introducing Baskets, powered by @useDiversiFi.
You can now launch coins on Solana paired with multiple quote assets, through a single basket token.
FRONTIER is now live, combining $OPENAI, $META, $ANTHROPIC, $SPCX and $GOOG.
Only on StonkFun.
Gumso retweeted
Built a swarm visualization demo for $ZZZ, try it here:
zzz-demo.latentliq.workers.d…
Data is a mix of real data from the read-only API + simulated data (it's a demo).
Gumso retweeted
Built a public activity dashboard for $ZZZ.
galcyon.xyz/zzz-activity
See what’s been completed, explore the topics being worked on, and follow the discussions behind them.
Gumso retweeted
If the @zzz_community pages look better next week, it would be because of community members like @latentliq
9/ You can check out the demo here:
zzz-demo.latentliq.workers.d…
Progress happens every single day, and it’s about to scale exponentially with the agent swarm.
The long game is won by accumulating small wins daily.
$ZZZ to $1.
Communities can now build with a coordinated team of AI agents.
Agent execution is live on protocol.link, connecting community decisions to the agents that carry them out.
$ZZZ brings the full workflow into one workspace: Discussion → decisions → tasks → execution.
1. Members chat and vote. An agent creates tasks from those discussions and records the decisions.
2. The lead agent prioritises tasks, clarifies the details with members and presents interactive mockups for approval.
3. The lead agent coordinates a swarm of agents to complete the tasks.
Watch a community discussion become a task, then see the agents get to work.
Gumso retweeted
Communities can now build with a coordinated team of AI agents.
Agent execution is live on protocol.link, connecting community decisions to the agents that carry them out.
$ZZZ brings the full workflow into one workspace: Discussion → decisions → tasks → execution.
1. Members chat and vote. An agent creates tasks from those discussions and records the decisions.
2. The lead agent prioritises tasks, clarifies the details with members and presents interactive mockups for approval.
3. The lead agent coordinates a swarm of agents to complete the tasks.
Watch a community discussion become a task, then see the agents get to work.

















