That was fixed in the latest version of AntTP. In short, the above URL is an XOR address, not a public archive. The filename on the end is entirely optional. However, the latest AntTP uses the filename to derive the MIME type and assign it as a zip file
I think it depends what the goal is.
Autonomi has a design where clients choose what data to persist and ant nodes validate then persist it. So, the architecture is very much client driven.
While you could use various patterns to create hybrid client/server applications, it side steps some of the goals Autonomi sets out to achieve.
Imo, we can achieve a lot with this model, but adding ownership transfers would help a lot here. Likewise, being able to derive an address from a key would help enormously.
I did a POC on the above with positive results: Separate owner address mutables by traktion · Pull Request #3073 · maidsafe/autonomi · GitHub
I detailed some of the benefits here: Revisiting the initial Safecoin Design for native Token - #35 by Traktion
3 Likes
if it was fixed in the latest version, @Southside you can just do the following:
to be safe you could do something like:
docker compose -f /home/git/safebox-server/docker-compose.yml down
then
docker compose -f /home/git/safebox-server/docker-compose.yml up --build -d
I’ll make the instructions pretty soon:
1 Like
Yes, you are right. As others said, you are running older AntTp version so it does not recognixe the mime typ for that file and loads it as bunch of bytes directly into website. There are 3 options:
- Upgrade your public AntTp gateway to latest version
- download it from commandline using for example wget
wget -O launcher.zip https://anttp.antsnest.site/012873cac6897439fc8dcad81f7be1ea344af0acf8a3dfda3e642208766e3eed/launcher.zip - Use latest AntTp on localhost and download via that.
If you manage to update that public gateway(anttp.antsnest.site), than everyone will be able to download it from browser.
1 Like