Latest binaries here: Release Colony v1.1.2 · zettawatt/colony · GitHub
Latest binaries here: Release Colony v1.1.3 · zettawatt/colony · GitHub
I got this error with the .deb download
willie@gagarin:~/projects/maidsafe/colony$ sudo dpkg -i Colony_1.1.3_amd64.deb
[sudo] password for willie:
Selecting previously unselected package colony.
(Reading database ... 587814 files and directories currently installed.)
Preparing to unpack Colony_1.1.3_amd64.deb ...
Unpacking colony (1.1.3) ...
dpkg: error processing archive Colony_1.1.3_amd64.deb (--install):
trying to overwrite '/usr/bin/dweb', which is also in package safe-box-client 0.1.1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Processing triggers for gnome-menus (3.36.0-1.1ubuntu3) ...
Processing triggers for desktop-file-utils (0.27-2build1) ...
Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Errors were encountered while processing:
Colony_1.1.3_amd64.deb
I blew away the existing colony dir ~/projects/maidsafe/colony
and tried again with a totally clean install – same error 
Ah, yea. I never did fix the issue if an existing dweb binary is encountered. Maybe I can rename it to something other than dweb. I’ll figure something out.
I’ll try the .Appimage meantime
Check Atlas shouts for more questions please.
that indeed is a rather big issue 
It forces people to remove the dweb from original source while enforcing your version on them (and you always need to be up to date instantly..)
I tried installing on Windows and unfortunately get a ‘encountered an error on startup. See logs’ issue.
I’ve uninstalled the previous version, and after it not working, I cleared the colony folder in my users appdata folder.
I have no idea what to check in the log to give a clue as to what the issue is.
Last line in the log is “2025/08/06-12:48:09.839069 35d0 [WARN] [utilities/transactions/pessimistic_transaction_db.cc:269] Transaction write_policy is 0”
I can send the logs if it’d be helpful?
Edit: I already had dweb running separately at the time of installing… not sure if that could cause issues? Sounds like it could be related to the issue Southside posted above. Looking forward to trying again when a solution is found 
@Southside sudo dpkg -i --force-overwrite ? It worked for me (colony or safemedia local client, don’t remeber. )
Thanks for the feedback everyone. I’ll take a look at this tonight. On startup, I’ll check for a running dweb process. If it exists, use that instead. That one is straight forward. For installation, it isn’t as clear to me. I bundle this sidecar binary into the app itself. There might be some kind of “don’t overwrite” option or something I can use.
@Zettawatt What do I need to delete to start Colony from scratch again? I already blew away every thing in ~/.local/share/colony and colony-appp but its still asking for a passwd…
And the original one that begun with ‘e’ fails…
There are 3 directories that it puts stuff in that need to be wiped out to start from scratch:
Minor update to prevent conflicts with an existing dweb install:
This should resolve the issues you guys are seeing. It worked in the limited amount of testing I ran it through this evening.
The good:
It works! You can search for files, download them, and view them with your default system applications. By using the same 12 word see phrase, you can sync with your desktop installation. The backend code is all the same so anything that works on desktop will work here, it is just displayed a little differently to fit on a screen.
The bad:
Autonomi is very SLOW on mobile devices. After the initial install you need to wait several minutes for it to sync the metadata from the genesis pod. The upload dialogs are there, so it should be able upload stuff, but you’ll probably have a pretty bad time trying to get anything larger than a few MB through.
The UX leaves a lot to be desired. Mostly this is a proof of concept to see if I could get it to work so you’ll see the random weird behavior and glitches that I simply haven’t cleaned up yet. Certain things, like the table library I used, don’t map well to mobile. I need to make something from scratch eventually here.
No dweb so no dweb apps. This is a limitation from Tauri itself. I can’t run a separate binary sidecar like I can on the desktop side. What needs to happen is extract the main dweb components into a library that I can pull into Colony natively. It can be done, just requires time and effort, like anything else 
Binaries available here: Release Colony v1.1.5-RC1 · zettawatt/colony · GitHub
Absolutely awesome @zettawatt
Well done.
Thanks! Much appreciated. And sorry ahead of time for the extra work. My guess is @riddim and @anon26713768 are going to start hounding you for that dweb library refactor 
I’m afraid it will be in vein though. I’d love to get up on my board and ride the wave that you @riddim an others are creating but I have far less time for the project and that limits not just how much I can do but how deep I can go. To do the clever stuff I need to spend long stretches deep in that space and I no longer have the time for that.
I’ll be happy to help and support where I can but don’t expect to be able to do anything like as much as I have been. Which is a shame, but that’s life priorities shifting I’m afraid.
I feel bad about that as I’ve lured you folk into the dweb approach and don’t want to pull the rug from under such good projects, but to keep dweb moving and expand its capabilities is going to take more than I can deliver.
I appreciate everything you’ve done to get dweb where it is and bundling it into binaries that ‘just work’. It is one of the first pioneering apps/frameworks on the network. It was no easy feat, I’m sure, especially considering you were working on the network when it was much less stable than it is today. Great stuff.
Does what it says
Installed seamlessly, waited 4-5 mins for sync and then I grabbed a couple of books to have on my phone - thank you
Awesome! Thanks for testing it out!
