you’re killing it 
4 Likes
Great work Traction 
I see you’re using Pointers as well and wonder if you’ve seen them updating ok on mainnet?
I’m only seeing the counters stuck at zero but they work fine for me locally so I’m still assuming it’s a mainnet issue.
4 Likes
I’ll point out again that for me pointers do update on main through python
But possibly it’s just working so well in python because the language is awesome 
6 Likes
Yes, they seem to be updating fine. I’ve not stress tested it, but each time I’ve tried, it’s worked.
Iirc, 1 register update got a bit confused and it took another to remedy it (as the client library log suggested it would), but it seemed pretty smooth.
maybe it’s not only that python is so awesome
AntTP does use the pointer_update function while the history datatype in dweb uses explicit state management and pointer_put
so slightly different mechanics
4 Likes
Good spot!
pointer_put Only use this when you know what you are doing. Else use pointer_create and pointer_update. Manually uploads a pointer to the network for a payment. Returns the total cost and the pointer’s address.
I read the first bit above and figured I’d use pointer_update instead! 
The pointer_update is free too, which is an interesting difference vs registers (and maybe pointer_put? 
).
1 Like
Good detective work, thanks. My code is modelled on Registers so I expect they have the same issue.
1 Like
funnily I dug a bit further and remembered that you mentioned this … registers interestingly (by now?) are using only pointer_update and don’t do puts anymore 
… after some circles I’m now pretty sure there is a bug in state management (that is pretty irrelevant for the dweb publish use case) but still don’t understand why it would fail xD … I wrote you a wall of text on discord xD
2 Likes
They charge for the version that doesn’t work 
Thanks fellas, I was closing in on this but @riddim to the rescue 
I’ll fix this today and everything should be working to at lest reasonable level.
4 Likes
Time for a little teaser!
Yes, that’s right - adding and updating new blog articles is almost with us!
There is a bit more plumbing to be done, but I successfully created a new blog with an article through the app today, without a CLI in sight.
Hopefully, I’ll get something to play with uploaded this weekend.
16 Likes
I’m not prepared to leave terminal land yet 
wohoooow!
5 Likes
After fighting and winning a parameter war with ant file upload (--max-fee-per-gas 40000000 is special, hot, sauce!), I’m pleased to usher in web based article publishing an IMIM!
You will need the latest version of AntTP, but other than that, you should be good to go - the pointer to IMIM now points at the latest code base, so you will automatically see the new app version.
Moreover, there is a default ‘imim’ bookmark set in AntTP, which whisks you straight to IMIM, without any long XOR/pointer URLs.
So, if you have your Autonomi / AntTP browser ready (i.e. browser with AntTP as a proxy), you can go straight to this URL and see my blog and the new publishing tab: http://imim/blog/traktion-blog
So, the perfect opportunity to munch on some dog food too! I’ll let IMIM tell you more about it…
http://imim/blog/traktion-blog/article/say-goodbye-to-the-cli.md#article
It still has a few rough edges, but it’s starting to come together nicely!
EDIT: Just to note, it looks like some of the CSS wrapping is a bit abrupt on the new article. I think it is the bullet lists, but I’ll tweak it into shape tomorrow !
9 Likes
I typically use 10 million which is currently the lowest possible. Unless the GAS fee is high this works and ensures no load when fees are high
3 Likes
I’ve pushed another release due to a breaking change in API URLs with AntTP (to align with dweb naming).
I would have liked to spend some more time refining ahead of the IF finals, but tbh, I’m out of the running there! I also wanted to spend some more time working on AntTP, especially the ownership transfer POC.
So, publishing works as posted previously, with a few rough edges. Viewing blogs and pages still just work as well as they have done for months too (with some speed regressions to use pointers/registers to keep the same URL).
http://imim/ will take you to the latest version, if you have your browser with the AntTP proxy setup. To view an example blog, see mine here: http://imim/blog/traktion-blog/
8 Likes
With the recent updates to AntTP and with Ant’s Nest providing a gateway, I thought IMIM was due a bit of love too.
The latest release includes 2 key features:
- It can be accessed via a gateway, as well as a proxy. This is done by creating 2 different builds, each with a different doc root. From a user perspective, it makes little difference (at least for read only, anyway).
- The video player has been upgraded to video.js, instead of the standard browser version. This should give a more smooth experience, but we will see how it goes.
How do I access these changes? Well, you can just follow the Ant’s Nest link right to the new endpoint: https://anttp.antsnest.site/gimim/blog/traktion-blog
You can’t currently create blog pages (as gateway payment support needs to be added), but you can browser just fine. I hope you will be impressed by the performance, with all the optimisations and caching kicking in!
If you’re hungry for more gateway compatible links, here is a page with a few more too: https://anttp.antsnest.site/gindex
4 Likes
I’m trying out IMIM, and successfully published a blog by uploading via ANT client in the command line, then opened it using the Browser Extension to access AntTP, and by running AntTP directly 
I tried making a new blog using the web app, but pressing ‘Publish’ didn’t seem to do anything. I had a funded wallet set up, but didn’t have any luck.
When attempting to publish a new article to the existing test blog, the ‘Publish’ button worked, but the following error was given:
Message: task 19907 panicked with message “called `Result::unwrap()` on an `Err` value: PutError(PayError(EvmWalletError(InsufficientTokensForQuotes(0, 873193130555))))”
Immutable Address:
I’ve tried a bunch of things, but nothing seems to work. I guess there’s an issue connecting the wallet. I tried using 2 funded wallets on SafeBox, but the error was the same.
On AntTP directly, I get the following error when trying to enter a private key after typing (on Windows): ./anttp -w --wallet-private-key (private key)
a value is required for ‘–wallet-private-key <WALLET_PRIVATE_KEY>’ but none was supplied
Any idea why it won’t let me supply a private key? I paste it after –wallet-private-key with a space but it seems to not see it.
5 Likes
Try this:
./anttp -w <your 64 char hex code here> -a <your other 64 char hex code here>
There is a long or short format for the argument. You don’t need both. Blame the clap library for not making that clear!
I actually created a blog page to test the above out this morning: https://anttp.antsnest.site/gimim/blog/07045bac77fd0474ac2c2d6040056739fa350cd6abc28eee1e5040fed726dad2/article/setup-anttp-for-writing-data.md#article
The publish page is a bit finicky, though. You can only use it in proxy mode atm. It needs some love! Just been too busy with anttp and life!
Glad you got ant CLI working with it too though! That shows the separation of data and app nicely!
3 Likes
Thanks for the rapid help!
I’ve now added the private key successfully, and created the 2nd blog entry using the publish page
Good work on IMIM and AntTP of course 
5 Likes
Is anttp.antsnest.site working correctly for you?
1 Like
Nicely done, sir!
I’ll return to IMIM again and add another layer of polish to it, but it’s getting there!
4 Likes