ANT Token - Price & Trading topic

[Traktion]

@Herodotos

The current problem with websites I have seen on autonomi is speed. Someone just copy&past uploaded wrong examples. But what actually needs to be done is to compress websites, this means connect all GUI images and css files into a single css file. Images can be encoded like that.

Tools like gulp do that easily. And this needs to be done for JS files too. So the actual website will just load very few big files. This is what autonomi does the best, deliver large files fast, but fails at delivering many small files, since latency is the main issue.

But this is already solved problem, we just need someone who actually upload them in that correct format, to show the world that the speed is not an issue.

Once we have this requirement well documented, there are many such website builders available. I think this is important topic, we need to upload some fast loading websites, make them default to watch on welcome page in browser when launched to prevent bad first experience.

Yes, agreed. IMIM does a lot of this, as Angular build minify most of the files in the build process.

Moreover, making extensive use of immutable types, as these can be cached forever. For CSS, JS, fonts, etc, that seldom change, it especially provides a huge benefit between page requests. Mutable heavy pages/apps will under perform relative to immutables.

Sites should also endeavour to download files in parallel too, where possible. Sequentially downloading small files is the worst possible experience.

I’d also like to implement this: Proposal: Tarchive

In short, much like a ‘public archive’ but with the content squished into a single file. This would optimise the downloads from the Autonomi network to AntTP, but allowing AntTP to deliver the small files quickly (as tarchive only needs downloading once).

There is lots more we can do.