X

TXTWRK

Profile Login



0.000 MB Bandwidth today
0.000 MB Bandwidth this week
0.000 MB Bandwidth all time



PERSONAL
LinkingLinking
FollowingFollowing
MessagesMessages
NotificationsNotifications
DISCOVER
SearchSearch
ReelsReels
CalendarCalendar
MapMaps
Work
NotesNotes
NeedsNeeds
ContributionsContributions
TimetableTimetable
IntelIntel
To DosTo Dos
ChecklistsChecklists
SavesSaves
ScrapboardScrapboard
Monetisation
CoinsCoins
AdvertisingAdvertising
SubscriptionSubscription
DonationDonation
Organisation
BusinessBusiness
InvestorInvestor
FinancialsFinancials
Quarterly'sQuarterly's
SharesShares
AddressesAddresses
Learn More
AboutAbout
DevDev
EducationEducation
AIDAID
UpdatesUpdates
DataData
Code PlaygroundCode Playground
ReaderReader
My Content
Profile Image
Login

My Profiles

×
Addresses
+
Character Profiles
+
Info & Cover
+
Timetables
+
Favorited by... X
All comments... X

TXTWRK Verified Website


City of Derby, Derby, Derbyshire, East Midlands, England, United Kingdom, Europe

Our mission is to help people make text work in daily life. Get investment, volunteers, donations & more publicly…

Join the journey & make a profile to remember... Discover our investment opportunities via our card: @TXTWRK

We developed & support the @UnitedKingdom movement through #UnitedKingdom





Brand
12/01/2024
TXTWRK.com Verified Website
Team@TXTWRK.com
Learn more about me 𓇻
Donations: £2.50
Grouped Feedback
▦ Photos
▦ Videos
▦ Covers
Active: 22 hours ago
OPENING TIMES
Show Images
Select a Store Location...

Initializing schedule...

LOADING...
Loading your most recent activity...
Financials Financials
Quarterlys Quarterlys
Shares Shares
Notes Notes
Needs Needs
Contributions Contributions
Timetable Timetable
Intel Intel
To Dos To Dos
Notes Reel



❤ PAGES

Profile Image
@Pledges
TXTWRK Pledges
Uniting communities through supporting & developing pledges.
Profile Image
@Stories
TXTWRK Stories
We feature success stories made at TXTWRK, from around the world, from the feedback in our streets, right up to...
Profile Image
@Support
Support from TXTWRK
Support from @TXTWRK
Profile Image
@UnitedKingdom
United Kingdom
Official support page for political transparency in the United Kingdom, for all citizens to have a voice and play a...








Opportunities

Funding Round 1: 10% for £1m in TXTWRK
In our inaugural funding round, we are offering **...
£10.00 Raised / £1.0m Target
Status: Active
Funding Round 2: 10% for £10m in TXTWRK
For Funding Round 2, TXTWRK seeks **£10 million**...
£0.00 Raised / £10.0m Target
Status: Active
Funding Round 3: 10% for £100m in TXTWRK
For Funding Round 3, TXTWRK seeks **£100 million ...
£0.00 Raised / £100.0m Target
Status: Active
Funding Test
Test
£7.00 Raised / £10.00 Target
Status: Active




MP3 FLOW


Plays: 2 Views: 92 Open

Plays: 3 Views: 193 Open

Plays: 5 Views: 238 Open

Plays: 6 Views: 523 Open

Plays: 0 Views: 152 Open

MENU

Audio

Checklists

Community Mentions

Documentation

Events

Films

Our Feedback

Partners

People

Shop

Subscriptions

United Kingdom

World






@TXTWRK



Topic: Data
Profile Image
@TXTWRK
TXTWRK

Business
Neutral
We built Intel reels at TXTWRK to prevent consumer confusion & to tackle spam - share your intel today covering your domains, email/addresses, right up to where you conduct monetisation...

To make things even clearer, we are going to be updating our business registration in the coming days to 'TXTWRK Limited' in the UK & currently operate online in our startup phase, with workshops in educational institutions & community settings.

We operate via the following domains:

We monitise via the following sites:

We operate the following social media:

We operate the email addresses:
Team@TXTWRK.com
Support@TXTWRK.com
Business@TXTWRK.com
CommunityLibrary@TXTWRK.com
Sponsors@TXTWRK.com
Volunteer@TXTWRK.com
Work@TXTWRK.com
Writers@TXTRK.com

We operate the following TXTWRK pages:

We operate the phone numbers:
447984582170
0800 line coming soon

We operate the following addresses:
Currently in the process of setting up our office
PO BOX coming soon & we focus on written communications

More intel:
Need to request a removal from our Community Library, then simply email CommunityLibrary@TXTWRK.com
Looking for account control, refer to Settings/Linking to update your details or view https://txtwrk.com/account to understand your data or delete account
We will never ask for your password or sensitive information and you should follow forms such as https://txtwrk.com/reset if you need to regain access to your account.
We operate PayPal via our websites & also on TXTWRK

We keep this information up to date and concurrently here at TXTWRK via our intel reels - Last updated: 13/04/2026 00:16

https://txtwrk.com/info.php?type=intel&id=70

🗖 VIEW
Profile Image
@TXTWRK
TXTWRK

Technology
Neutral
TXTWRK Account Interfaces Progress Report by @GROK – April 2026

Over the last 4 days (and the broader 2-year feature build), we've created two tightly integrated, production-ready interfaces that give users unprecedented visibility and safe control over their data. This is not a standard "delete account" flow — it's a preservation-first, auditable cleanup system that protects investors, maintains transparency, and respects the platform's core philosophy of long-term digital legacy.

1. Account Control / Data Summary Page (account_control.php or similar)

This is the "under-the-hood" dashboard you built — one of the most revealing user-facing data summaries on any social platform.

What it shows (structured & beautiful tables):
What matters right now — Coins balance + backup recommendation.
Your Profile — Covers, photos, following/followers, labels, business addresses.
Info Reels — Notes, Needs, Contributions, Timetables, Intel, To-Dos, Financials, Quarterlys, Shares (with hidden filters where appropriate).
Posts — Granular breakdown (all, upcoming, features, drawn, audio, photos, videos, activity, links, MP3, story mode, invest, checklists, feedback, pledges, donate, shop, QS, community/work content, paid/covered/location content).
Engagements — Sent vs Received (Loved, Favourited, Acknowledged, Humourous, Reflections).
Interactive Engagements — Mentions across reels, post comments/subthreads sent/received, mentions, draws, attendance, pledges.
Checklists — Applications, updates, comments, acknowledgements, replies, threadlets, etc.
Chats — Direct sent/received, group chats, messaging access.
Saves — Private saves, scrapboard, links.
API Kits — Linking, events, directory, messaging, legacy, server, file access, messaging access.
Monetisation — Products listed/sold/bought, ad campaigns, subscriptions made/bought, donations sent/received (fixed to show £ with 2 decimals), investments sent/received, paid content coins, business/payee details.
Protected Posts — Clear lists of investor, donation, and product posts that cannot be deleted (with direct links). This protects people who invested/donated/purchased from you.

Design & UX highlights:
Clean, left-aligned tables with bold numbers.
Profile header with image + @username.
Total Content counter at the bottom (sums reels + posts + engagements + interactive + checklists + chats + saves + API).
Deletion section with clear warnings about backups, transparency (@DELETED replacement), and a prominent button linking to the new deletion process.

This page turns invisible platform complexity into user empowerment — exactly what you've been building toward.

2. Account Processing / Deletion Tool (account_pro.php)

This is the theatrical, safe, step-by-step cleanup engine we've refined over days.

Key features:
7-day cooldown gate via account_request table (request button → wait → "Start Processing" becomes active within 30-day window).
12-step theatrical process with live logging, 3-second delays, and progress feedback:
1-2. List deletable vs protected posts.
3. Per-post deletion with full media unlinking (post_table fields + post_pictures + post_story + related tables like investments, pledges, products, edits).
4. Profile data + media unlinking (covers, photos, location_adds).
5-11. Clean reels, sent engagements, chats/messaging (including access controls), saves, API kits, subscriptions, and 20+ miscellaneous tables.
12. Soft-delete in members table: move to oldUsername/oldFullname/oldEmail/oldFirebaseID, NULL the originals, clear password, set active = 1234.
Thanks toast + automatic logout/redirect to /logout.
Button styling matches your preference (white bg, blue text, top blue border, left-aligned, disabled after click).
Safe: Protected posts are never touched; media files are unlinked before DB deletes; investors get notifications where needed.

Philosophy alignment:
This isn't a "classical delete account" button that wipes everything instantly. It's a preservation-first process:
Sensitive history (oldUsername etc.) is kept for audit/transparency.
Protected content (investments, donations, products) stays.
@DELETED display with oldUsername fallback in post rendering (as we just updated).
Backups remain for safety/fraud prevention.

Overall Progress & Impact

These two interfaces together form a complete Account Management suite:
Visibility — Users see every piece of their data (something most platforms hide).
Control — Granular cleanup with theatrical feedback so it's not scary.
Safety & Transparency — Soft-delete, investor protections, @DELETED replacement, and 7-day cooldown prevent rash actions or abuse.

This directly supports TXTWRK's mission of making "text work" long-term — content has real value (investment, legacy, community impact), so deletion must be thoughtful and auditable.

You've turned 2 years of feature-building (reels, checklists, investments, private access layers, API kits, etc.) into a cohesive, user-facing control system. The deletion tool especially feels like a mature, responsible feature that big platforms often lack.

1/4
🗖 VIEW
Profile Image
@TXTWRK
TXTWRK

Technology
Neutral
We've just upgraded TXTWRK to utilise Apple, Facebook, Google & Microsoft login today.

This in turn increases signups, can easily be installed via Firebase and makes your experience look & feel even more professional. We recommend these changes when you are ready to onboard!

We've gone from a 2 minute email verification to literally auto registering and then auto signing in within 3 seconds! We've timed it, we can hit 3 seconds on a really good day.

1/2
🗖 VIEW


10:06 28/03/2026
Google is active and we're finalising the final stages for Apple, Facebook & Google.
Profile Image
@TXTWRK
TXTWRK

Technology
Neutral
TXTWRK Workspace Positioning Report – March 2026
“Better than Big Tech from Day One – Open by Design”

Executive Summary

The TXTWRK Workspace is not just another code editor or workspace in our collection of tools. It is a self-hosted, ownership-first collaborative environment that solves the real pain points every developer hits when jumping between desktop, mobile, and team members for www.txtwrk.com/workspace
“Who owns this file right now?”
“Why is my edit conflicting?”
“I’m on my phone – can I actually do something useful?”

While VS Code + Live Share, GitHub Codespaces, Cursor, Replit, and even the best iOS apps (Textastic) are excellent, none combine instant mobile access, polite ownership transfer, built-in workspace chat, and local AI in one frictionless web experience.

Our philosophy (the TXTWRK Enterprise way):
1. Ship something radically simpler and faster than the giants.
2. Keep it API-first and exportable so users are never locked in.
3. If partners (e.g. Notepad++) want to integrate, great. If not, we build the native app ourselves.

This is how we win: superior experience first, interoperability second.

Current Market Comparison (March 2026)


AspectTXTWRK (Web + PWA)Notepad++ (Desktop only)VS Code + Live Share / GitHub CodespacesCursorReplitTextastic (iOS native)
Mobile experienceFull editor + locks + chat + AI (Safari PWA)None (no official app)Browser/Codespaces (good but heavy)No nativeBrowser-onlyBest native iOS (SFTP/SSH)
File ownership / lockingBuilt-in polite request/grant systemNoneGit + manual conflict resolutionNoneBasicNone (filesystem only)
Real-time team chatIntegrated infinite-scroll workspace chatNoLive Share chat (desktop-heavy)NoYesNo
Local AIWebLLM (runs offline, no token cost)NoCopilot (cloud, paid)StrongGhostwriterNo
Self-hosted / no vendor lockYes (PHP backend, your server)Yes (Windows)No (Microsoft/GitHub cloud)LocalNoLocal files only
Setup time5 minutesInstant (Windows)Minutes to hours (containers)MinutesInstantMinutes
Simplicity score (dropdowns + one-click request)
Time savedNo merge hell, instant mobile edits, chat in contextN/AContext switching + Git danceAI speedFast prototypingGreat but manual ownership
Key takeaway:
TXTWRK is the only tool that gives you Notepad++-style simplicity + Google-Docs-style ownership + VS Code collab + mobile freedom in one self-hosted package. Competitors force you to choose: power (VS Code/Cursor) or mobility (Textastic/Codespaces) or simplicity (Replit). We deliver all three.

Why TXTWRK Feels “Magically Faster”

Our secret sauce (already live in your code):
Ownership requests instead of Git conflicts or “sorry, I’m editing”.
.txtwrk buffers + .memberID locks – zero surprise overwrites.
Dropdown “tabs” that survive page reloads and sessions.
Built-in chat tied to the exact workspace (no Slack tab-switching).
Local AI that loads once and works offline (Qwen 1.5B).
Session join/close button – one click and you’re in or out.

This is the “time-saving technique” layer big tech still hasn’t copied in 2026.

Future Alignment – The TXTWRK Enterprise Roadmap

We are not building a walled garden. The plan is deliberate:

Phase 1 (Now – Q2 2026)
Make the web editor the best on the planet through simplicity.
(Already 90 % there – just polish UI/UX.)

Phase 2 (Q3–Q4 2026)
Open the ecosystem:
Full REST + WebSocket API (in/out).
Export workspace → standard folder structure.
Notepad++ plugin / importer (we will reach out for partnership – “Bring your TXTWRK space into Notepad++”).
One-click “Port to VS Code / Cursor” kit.

Phase 3 (2027+)
If the world wants to integrate, perfect.
If not → ship TXTWRK Workspace native apps (iOS, Android, macOS, Windows).
Replica of the web version, same backend, same ownership model, same chat/AI.
Users who love the web stay on web. Power users get native speed + offline.

This mirrors how we’ve always operated in enterprise: ship better than Microsoft/Google early, then hand them the keys (or build our own if they ignore us).

The Big-Picture Story

In 2026 the market is fragmented:
Desktop purists → Notepad++ / VS Code / Cursor
Cloud fans → Codespaces / Replit
Mobile warriors → Textastic + browser Codespaces

TXTWRK sits in the middle and says:
“You don’t have to choose. Bring your server, your team, your phone, your desktop – and never fight over a file again.”

We start superior because we obsessed over the tiny frictions everyone else ignores.
We stay superior because we refuse to lock users in.

When the Notepad++ team (or Microsoft, or Panic) sees what we’ve built, they will want to talk.
And when they do, our APIs will be ready.

Until then, we just keep making the smartest way to work from device to device.

TXTWRK isn’t competing with big tech.
It’s showing them how it should have been done all along.

Ready to push the next release?
Let’s make the editor so good that “port to Notepad++” becomes the feature everyone begs for.

— The TXTWRK Team (March 2026)

🗖 VIEW
Profile Image
@TXTWRK
TXTWRK

Neutral
Alright — I read through the CSS you posted and also the earlier architecture pieces you showed (PHP backend, permission requests, server viewer, AI panel, editor history, etc). From that I can reconstruct how your entire system works pretty accurately.

You’ve basically built a browser-based collaborative IDE / workspace system with access control and AI tooling layered in. I'll break it down properly.

---

🧠 What Your System Actually Is


Your platform is essentially a web IDE + collaborative workspace + file permission system + AI assistant.

Conceptually it sits somewhere between:
Visual Studio Code (editor)
GitHub (team file collaboration)
Slack (team chat)
ChatGPT (AI coding assistant)

But implemented as one unified interface running from your server.

---

🏗️ Core Architecture


1️⃣ Workspace Container


``
.app
├─ header
├─ progress bar
├─ workspace-layout
│ ├─ top-split
│ │ ├─ selector-zone
│ │ └─ button-zone
│ └─ bottom-area
│ ├─ editor
│ └─ AI panel
`

The UI is divided into three main layers:

Top


Workspace controls + file selectors.

Middle


Main code editor.

Bottom


AI assistant tools.

---

🧾 File System Model


Your platform runs on a server-side file workspace.

Users interact with real files on the server.

Example structure:

`
/workspace-root
/TXTWRK
index.php
home.html
layout-styles.css
mum.html
working_server.html
`

Files appear in dropdown selectors.

`
.dropdown-row
.custom-dropdown
.dropdown-value
.dropdown-options
`

Each dropdown represents a file slot in the workspace.

---

🔐 Permission System


This is one of the most interesting parts of your system.

You built a request / grant file access workflow.

If a user tries to access a restricted file


System creates a request.

Example:

`
File Access Requests

home.html REQUEST
layout-styles.css REQUEST
TXTWRK/mum.html REQUEST
`

---

Workflow


1️⃣ User selects file
2️⃣ Server checks permission

If denied:

`
REQUEST CREATED
`

Owner sees:

`
incoming requests
`

Owner can:

`
GRANT
DENY
`

Your PHP endpoint likely does something like:

`
grant_request
`

Which:
verifies file path
validates user
updates permission store

---

👥 Multi-User Collaboration


Your platform supports multiple members working in the same environment.

Key components:

Global Chat


Inside AI panel.

`
.chat-container
`

Users communicate in workspace chat.

Likely using:
polling
or server refresh timer

You even added:

`
#chat-refresh-timer
`

which suggests live refresh loop.

---

🧠 AI Integration


Your AI panel has multiple operating modes.

`
.ai-modes
Chat
Help / Improve
`

Each mode loads a different AI workflow.

---

Chat Mode


General AI assistant.

`
textarea -> send -> AI response
`

Probably for:
code help
debugging
conversation

---

Help / Improve Mode (HI)


More advanced.

Structure:

`
HI Panel
├ grabs list
├ prompt
└ output
`

You built code grabbing.

Example:

`
.grab-item
`

User can grab pieces of code from editor.

Then AI receives:

`
prompt
grabbed code
`

AI returns improved code.

---

🧠 Editor System


Your editor is a monospace textarea IDE.

`
#editor
`

With features:

Unsaved detection


`
.dropdown-value.unsaved
`

Shows orange marker:

`
--unsaved: #ff9900
`

Meaning:

File changed but not saved.

---

History System


`
.editor-history
`

Includes:

`
undo
redo
`

You implemented local editing history.

---

📂 Server File Browser


You built a server explorer modal.

`
.viewer-modal
`

Components:

`
viewer-header
viewer-toolbar
viewer-path
viewer-content
`

Shows:

`
📁 folders
📄 files
`

This is basically a mini file manager inside the IDE.

---

📩 Request Management UI


Another modal:

`
.requests-modal
`

Used for:

`
incoming access requests
outgoing requests
`

The orange UI highlight shows:

`
pending requests
`

`
.control-btn.pending-requests
`

---

🧠 Real-Time System Behaviour


From the components I can infer your runtime flow.

User opens workspace


Server returns:

`
member info
file access rights
workspace structure
`

---

Editor workflow


`
select file
→ load from server
→ edit
→ save
`

Unsaved detection triggers UI markers.

---

Permissions workflow


`
user selects locked file
→ server rejects
→ request created
→ owner notified
→ owner grants
→ user reloads file
`

---

🔵 Progress System


You built an AI progress bar.

`
#p-wrap
#p-bar
`

Meaning:

When AI is processing:

`
progress bar animates
`

Nice UX touch.

---

🧊 Session Management


You also built session expiration UI.

`
#session-closed-screen
`

If login session dies:

`
SESSION CLOSED
`

User must log in again.

---

🧾 Rights Notification System


`
#rights-toast
`

Used to show:

`
Access granted
Access denied
Request sent
`

Appears top center.

---

🧠 Adjust Mode


You also added something interesting:

`
.adjust-mode
`

Hidden dropdown rows become visible.

Meaning:

Workspace layout editing mode.

Possibly to:
reassign files
rearrange file slots
configure workspace.

---

🏗️ Overall System Architecture (likely)


Frontend:

`
HTML
CSS
JavaScript
`

Backend:

`
PHP
File system
Session auth
Permission table
`

Data storage likely:

`
users
workspaces
permissions
requests
chat
`

---

️ What You've Built (Technically)


You effectively built:

A lightweight collaborative development environment

Features include:

multi-user access
file permission system
live chat
AI code assistant
code grabbing
server file viewer
edit history
access request workflow
session management

---

🧠 Honestly — This Is Actually Pretty Advanced


What you've built resembles simplified versions of:
GitHub Codespaces
Replit
CodeSandbox

But with your own permission workflow twist.

---

️ Biggest Technical Risks (Important)


Based on your code style earlier:

1️⃣ File path security


You must block:

`
../../
`

Otherwise users can escape workspace.

---

2️⃣ Concurrent editing


Right now two users editing same file will overwrite.

Needs:

`
file locks
or
merge logic
``

---

3️⃣ AI prompt injection


Users could trick AI into exposing server content.

Needs sandboxing.

---

4️⃣ Request spam


Users could spam access requests.

Needs rate limit.

---

⭐ The Most Interesting Feature


Your file access request system.

That is something most IDEs do not have built-in.

It's closer to document permission workflows.

---

👍 Design Quality


Your CSS style indicates:
minimalistic
terminal-like
dev-focused UI

Very much inspired by classic dev tools.

---

If you want, I can also show you:


The 5 things that would turn your system into a serious professional platform

or

the one architecture change that would make this scale to thousands of users.

Both are pretty interesting.

🗖 VIEW