Just answered my own question 
4 Likes
Yeah going to have bookmarks so you can organize your collection. Plan to integrate colony search eventually too. As for defaults, perhaps I could just have a default bookmarks file that can be available to import - like a sort of wiki of links.
5 Likes
Is this to superseded the browser extension and client or to work alongside them ?
1 Like
Think of it as more of a stage two. Users are more comfortable installing an extension onto their normal browser.
Once they wish to delve a little deeper they can download the autonomi browser itself, which will have more features (in-built wallet, colony search, etc). Although the plan for this browser is autonomi-centric - no clearweb browsing, although it will still allow autonomi websites to make normal calls to internet web resources if they require them.
5 Likes
I’m not sure about that. I’d rather have separate browser.
4 Likes
If we must have it, please have a toggle for that and disable by default.
Clear net has many security issues that we simply don’t have to be concerned with on Autonomi.
While it may be tempting to offer a hybrid, folks -will get stung by it and there will be blow back.
You will also end up with all sorts of nasty hybrid solutions, which will soon become the norm.
Why not just let folks use their regular browser for regular sites and keep autonomi sites separate?
Fwiw, I considered offering the same when using AntTP as a proxy, but quickly changed my mind. Imo, it is a pandoras box that you want to leave sealed.
8 Likes
So would I, but the vast majority of internet users use chrome. And even getting them onto a more privacy centrist browser is a big puzzle that companies spend millions on trying to solve. So the plan is to target them where they are, show them the benefits, and then entice them to greener pastures.
3 Likes
Agree, I will default not allow internet connections. The first time an internet call is requested, even to an image or js file I will show a bar stating that it was blocked with a link to the settings if they wish to enable external internet calls.
9 Likes
Are you using Servo/Verso or something else? Great to see 
5 Likes
I’m using Tauri v2 
7 Likes
Can you say more. Which webview you’re using and what platforms you plan to support.
When I was looking at this it wasn’t to working well enough (for awe), and there were cross platform issues with different browser views. I forget the details, but the were some killer issues. One I think was being unable to position the webview. I guess that’s working at least!
3 Likes
Tauri v2 uses webkit for mac and linux, and webview2 for windows.
I’ll initially be supporting windows, mac and linux. Later I’ll support android and ios.
4 Likes
Great to see - good luck and thanks for the explanations.
4 Likes
We now have tabs. You can drag to reorganize them, close them and even open new ones. If you close a tab it will jump back to the last active tab.
Each tab keeps track of the content.
More styling to come.
16 Likes
I’m not sure of your vision but if you didn’t follow my browser demo awe this may be of interest.
I was able to demonstrate using meaningful URLs based on a set of schemes that supported loading resources (websites or files) including versioned websites, single version sites (from an Archive), files etc.
These could be referred to using an xor address or using a meaningful name, and names could be registered with the local client. I envisaged being able to share and follow names (similar to @zettawatt’s Colony) but didn’t go that far.
The URL schemes I was working on or had working were as follows:
- awf:// →Autonomi Web File (xor address or name)
- awm:// →Autonomi Web Metadata (Archive address or name)
- awv:// → Autonomi Web Versioned (Archive address or name with optional version)
So for example:
- awm://bd3aa0cb485cf61b1d8a043a916ada9aecc42775d0941a2248535c91561f0c25
- awv://v.awesome-0fde/index.html
- awv://v3.awesome-0fde
The nice thing about this in a custom browser is you can handle these URLs internally without a separate server (so no need for dweb or AntTP). You just need the browser to keep track of any names and versions so that loads from one page/tab don’t get confused with a different page/tab which has opened a different version or (particular Archive).
The code for this was working in awe using a single iframe to demonstrate loading versioned sites using names specified by a user, or directly using xor addresses for a Register, Archive or file. At the time I was planning to use the Tauri webview to build a custom browser, but this wasn’t working. I looked at Servo/Verso but wasn’t able to compile that with my setup (mobile b/b). So I set that aside and eventually decided to build dweb as a separate server to get as close to this as I could, but using standard browsers.
If you are interested in any of these ideas, particularly supporting versioned websites without dweb I’d be happy to help where I can.
8 Likes
Just want to highlight that I’d be glad to see versioned sites supported as widely as possible.
5 Likes
Try
http://localhost:18888/13da4c1417afa184b634ab6446b1bebcac821e0968e19f8ccef6f56a2f9c8fd2/index.html
3 Likes
There was a tarchive bug which was squished in the (to be) release 0.11.1 of AntTP.
In short, the padding at the end of some tar files was too large to find the index. It could possibly lead to missing images, etc.
I will push an official release over the weekend, but master branch includes the changes already.
6 Likes