DorkOS 0.94.0 makes the app much easier to use with the keyboard, and cleans up properly when you remove a chat connection or disconnect from a Community. If you run your own Community server, you can now take down a whole community, move a large one in over a shaky connection, and keep very big rooms fast.

Highlights

See where you are with the keyboard

Press Tab and the thing you're on now has a clear outline, in light and dark mode. Buttons, text boxes, checkboxes, sliders, lists and switches all got it, in the app and on a Community's own web page.

Removing things really removes them

Remove a Telegram or Slack connection and DorkOS now deletes its delivery history and the list of people waiting to chat with it. Disconnect from a Community and DorkOS takes the agents you added there with it, and each of your computers keeps its own agents.

DorkOS 0.94.0 makes the app much easier to use with the keyboard, and cleans up properly when you remove a chat connection or disconnect from a Community. People who run their own Community server can now take down a whole community, move a large community in over a shaky connection, and keep very big rooms fast.

Added

dorkos community deploy --remove-uncertain <run-id> checks the one resource a stopped launch may have left behind when it could not tell whether a create worked. It removes the resource only when DorkOS can prove your launch made it and you type the id it shows, and it checks everything again just before deleting. Otherwise it removes nothing and tells you why, with the commands to check it yourself. After a removal, --resume continues the same launch. A real launch on Fly and Neon has confirmed that the codes setup saves come back unchanged, so the proof holds (DOR-2238).
A person who runs a Community server can now take down a whole community when they learn it is illegal. It closes at once: every member sees "This community was removed by its host.", every connected DorkOS app and agent loses access, and any finished export is deleted. If the host has a separate evidence store, the server first saves a full copy of the community there, with each member's account details, because many laws require keeping one for the authorities. The owner is told why, unless the host holds that back, and can't cancel it. The community is deleted after three days by default. Until then the host can undo it, and the community comes back paused rather than open. One person or key can remove at most three communities a day, so a leaked key can't quietly remove many (DOR-2293)
A Community server now tells connected DorkOS apps plainly when its host took a community down, as a different answer from a pause or an ordinary deletion. When that happens, DorkOS removes the rooms, messages, files and search results it kept from that community, stops your agents working there, and says the host took it down. If the host puts it back, you connect again and it fills in from the Community. A host suspending a community removes nothing. (DOR-2293, DOR-2334)
Moving a community into a hosted community now sends a large export in pieces when the new community's server supports it. If the connection drops, sending again picks up with the pieces that are still missing instead of starting over, and the progress bar keeps counting from where it was. Servers that take the file in one piece work as before. If DorkOS restarts during a move, or the move was started on another computer, the move now says plainly that it has to start again and why, and a move whose upload time ran out says that instead of a general error. (DOR-2297)
On a Community server, the host can now keep a copy of the erasure journal, the list of people who erased themselves, somewhere other than the server, by reading it with a host API key that has the new communities:erasure_journal permission. After restoring a backup, running that copy through erasure/reapply.js erases those people again, so nobody who was erased comes back. The list holds IDs only, never anything that was erased. The server keeps journal lines for COMMUNITY_ERASURE_JOURNAL_RETENTION_DAYS (400 days unless you change it) and deletes them after that. The Community operations guide has a script that makes the copy on a schedule. (DOR-2566)
When a Community you're connected to is deleted or taken down, its page now says what never got there, for example "3 messages from your agents and 1 draft of yours weren't sent." Your own unsent drafts get a button to copy them before you remove the community, which clears them (DOR-2575)
Community hosts get the first part of a way to replace an owner who has left: new host routes to ask for a replacement, list the requests, cancel one, or send the new owner a fresh link. They need the new communities:ownership key permission, or an operator's password. For now every request is refused, because the owner can't yet answer the email that tells them. Asking will open up in a later release, once the owner's "Keep ownership" link and the new owner's claim are ready (DOR-2539, DOR-2540)

Changed

dorkos community deploy now marks what it creates so a later check can tell your launch's resources apart from anyone else's. Before each step, it saves a random code in the recovery journal. The Fly app gets its own private network named after that code, and the Neon database role is named community_ plus a code instead of community_owner. Because of the separate network, the app can't reach your other Fly apps over Fly's private network. Community doesn't need to. Launches you already started keep working as before (DOR-2238).
Each signed community release now names the exact image for each kind of computer it supports, not only the bundle that holds them. dorkos community deploy uses that name to check your community after it starts, so it no longer needs to look the image up in the image registry first. Releases made before this change still work: setup looks the image up as before (DOR-2586)
Keep big Community rooms fast in the app. Loading a room's history used to slow down more and more as the room grew: 4,000 messages took about seven minutes, and 100,000 would have taken days. It now takes under a minute for 100,000. Scrolling back through a room that size also went from about a tenth of a second per page to under a millisecond. (DOR-2573)
Stop keeping a record of every message delivery forever. The app now keeps a message's delivery record for eight days, as long as the message itself can still be waiting, and each connection's newest 500 events. On a busy install that keeps the database small, and a connection's event log and the delivery numbers load several times faster. (DOR-2574)
Community servers now delete a connection request an hour after it expires, even once it was used. The connection it made stays. (DOR-2574)
Removing a Telegram or Slack connection, or uninstalling the package a connection came from, now deletes its record of recent deliveries straight away, along with the chat names in it. These used to stay until a regular cleanup removed them, days later. Messages already passed to an agent or a room stay where they are. Updating a package keeps that record. The removal prompt now says so. (DOR-2604)
Moving a community into a hosted community no longer stops at a fixed 16 GB. How large a move can be now depends on two things: what the new host says it will take, and how much free space this computer has to hold the file while it goes up. If the file won't fit on this computer, the move stops before anything is saved and says how much space it needs and how much is free. If the file is larger than the new host takes, the move stops before anything is sent to the new host and says it is too large. (DOR-2587)
Delete a large community faster, and post with less work: the server now checks each link between a community's records once instead of twice. On a test community of a million messages, deleting it went from about two minutes to under a minute and a half.
Start an export or a member's erasure without first reading every message in the community. On the same test community, that step went from 107–157 milliseconds to under one. Posting and opening a channel's member list now look up that community's members instead of every membership on the server.
Removing a chat connection such as Telegram or Slack, or uninstalling the package it came from, now also deletes its list of people who messaged it with no agent to answer, with the names and chat titles in it. That includes people you ignored or blocked, so if you set the same connection up again, anyone you blocked will need blocking again. Updating a package keeps them. (DOR-2608)

Fixed

Setting up your own community with dorkos community deploy no longer stops once your community is already up and running. The release names one bundle of images for several kinds of computer, and Fly runs the one for its own servers, so setup's final check compared the wrong fingerprint and gave up. Setup now works out which image Fly will run before it deploys, by reading the signed image bundle from the image registry, and checks against that (DOR-2586)
Setting up your own community with dorkos community deploy no longer gives up while Fly is still starting it. Setup allowed every step 30 seconds, but starting your community can take longer, and cutting it off left setup unsure whether it had worked. Starting and restarting now get up to ten minutes, and creating or removing things gets two. If a start is still cut off part way, running the same command with --resume starts your community again. If your app is running something setup didn't put there, setup leaves it alone and tells you what to check (DOR-2169)
Removing a self-hosted community's file storage is now recognised as done straight away. For a while after it's removed, Fly still lists the storage under a new name, marked deleted and no longer attached to your app, and setup used to treat that as an error it couldn't read (DOR-2169)
dorkos community deploy now uses a Fly or Neon token you export, instead of quietly using your saved sign-in. Before, setting FLY_API_TOKEN, FLY_ACCESS_TOKEN or NEON_API_KEY to a limited token changed nothing, so setup could create things with more access, or in another account, than you chose. Setup now hands those tokens to fly and neonctl and to nothing else, says in one line which ones it is using (also when removing something a stopped setup left behind), ignores an empty variable, and never writes them to its recovery notes or anything it prints. Setup has not yet been tested end to end with a limited Fly token; signing in with fly auth login is still the tested path (DOR-2602)
Connecting a community now tells you what actually went wrong instead of always saying to check the address. If no community uses that short address, it says so. If there have been too many tries from here in a short while, it tells you to wait, and for how long when the community says. If the community's server is too old, it tells you to ask whoever runs it to update it.
When you connect an agent to a Telegram or Slack connection, the chat picker now lists the chats that have messaged that connection recently, by the group's name or the person's name, with how many messages each has sent. The list was always empty before. An agent's connection card also says when its chat last sent a message, where it used to say "No recent activity" every time.
A message you send just as a Community is deleted or taken down is no longer lost with its room. The community's page counts it with your drafts, and "Copy your drafts" gives you its text back (DOR-2575)
When you move around with the Tab key, the button you're on now has a clearly visible outline in light and dark mode. Before, the outline was too faint to see easily, on the Community's own web page and in the DorkOS app (DOR-2567)
On the Community's own web page, the Attach button now shows when you've tabbed to it. Before, nothing showed at all (DOR-2567)
Disconnecting this DorkOS from a Community now removes the agents you added to it from this app, instead of leaving them active there with nothing left to run them. The Disconnect confirmation names the agents it will remove first. It removes only agents this DorkOS still runs (DOR-2603)
If the Community can't be reached when you disconnect, this DorkOS still disconnects, and it tells you which agents are still on the Community so you can remove them under Agents on its own site (DOR-2603)
If you already have a connection with the same name as a marketplace package, the install preview now says so before you install, and asks you to remove or rename it first. Your connection stays exactly as it was. Before, the install failed at the last step and removed your connection, along with its saved sign-in details and its links to your agents. (DOR-2607)
Installing an adapter package you already have installed now works, and keeps its connection, saved sign-in details and links to your agents as they were. (DOR-2607)
When you move a community in, DorkOS now checks that the file fits on this computer before sending it. If it doesn't fit, you hear so at once, with how much space it needs and how much is free, instead of after the whole file has gone up. That matters most from a phone, where a large file can take a long time to send. (DOR-2610)
Starting a move again, after it was refused, cancelled or failed, now begins a new move. If it is refused again, you see the real reason. Before, it could show the old cancelled move with no explanation. (DOR-2611)
When you Tab to a text box, a checkbox, a radio button, a slider or a scrolling list, it now has a clearly visible outline in light and dark mode. Before, the outline was too faint to see easily. This covers the standard controls in the DorkOS app and on a Community's own web page (DOR-2609)
A text box with a mistake in it now shows a clear red outline while you're typing in it. Before, the red was so pale it was hard to tell it apart from the page (DOR-2609)
In a narrow window, switching from a Community back to your own DorkOS now leaves your place on the Home page's title, so a screen reader says "Home" and stays there. Before, the message box took over a moment later, and the next thing you heard was the name of a box you never picked (DOR-2613)
When you move around the DorkOS app with the Tab key, the outline around the thing you're on is now easy to see in light and dark mode. Before, many boxes, rows, links and small buttons drew it too faintly: the folder path box, the feedback message box, inbox rows, option lists and banner close buttons among them (DOR-2615)
Choice switches like "Ask first / Full autonomy" now show an outline when you tab to them. Before, nothing showed at all (DOR-2615)
When an agent asks you a question, the first answer no longer looks already chosen. The outline that shows where the arrow keys are only appears once you press one (DOR-2615)
If two of your computers run the same agent files and both add the agent to a Community, each one now gets its own copy of the agent there. Disconnecting one computer, or removing the agent from it, leaves the other computer's copy running, and one computer can no longer take over the other's copy. A computer you disconnect and connect again gets its own agent back, with the same name and rooms. You can still remove any of your agents on the Community's own site, and the Community's owner and admins can still remove them too. An agent you added before this update belongs to the computer that added it when only one of your computers has ever connected to that Community. Otherwise it belongs to whichever computer next renews its access (DOR-2612)
Going to another page no longer draws the page you are leaving a second time first. For a split second the old page came back, and its message box could take your cursor on the way out. The short fade meant for the new page also played on the old one, so the new page just appeared (DOR-2616)
Your DorkOS account link no longer drops itself when one app-connection request is refused. It checks the link first, and only unlinks this computer when the account really has let it go. Before, a single refused request could unlink you and leave your connected apps stranded until you linked again (DOR-2620)

DorkOS 0.94.0

Highlights

See where you are with the keyboard

Removing things really removes them

No more lost connections

More for people who run their own Community

All Changes

Added

Changed

Fixed