…the Blurt logo looks like this…
When after hours of testing you come to the conclusion that your code does not contain a bug but a fallacy ... and you have to rewrite a whole part ... then you look exactly the same ...
So I suppose the designer of the Blurt logo is also a programmer 😉
It's not easy, you have to build everything yourself, even the full node. the public one isn't reliable.
Yeah, that's what I found out...
Although, rpc.blurt.world is pretty stable... as long as you don't use api.streamTransactions...
yah, it sets the limit on number of requests.
I have absolutely no experience in setting up a full node...maybe something to investigate later...
Is it difficult to maintain? What skills do one need?
You have 2 running I believe...
Setting up a full node is no difference than setting up a witness node, besides that you have to enable more plugins.
Here is document about how to run a witness node: https://gitlab.com/blurt/blurt/-/tree/dev/doc/witnesses
Here is the config with a really nice detail about the plugins
https://github.com/Someguy123/blurt-docker/blob/master/data/witness_node_data_dir/config.ini.example
Full node might be a little bit difficult to maintain, some UNIX knowledge needed since you have to investigate you own if your node has some issue.