StarGeezer

It took me some figuring out too - I thought that our azimuth in location would orientate the orbs as well. When I realised it was fixed I rotated the...

Absolutely! Or a defined(!) list of error codes that frontends can use for e.g. translation purposes. E.g. building on @erwin-willems's suggestion ``` { "error": "SubmitTransaction: Problem processing transaction: ...", "errorCode":...

@superzordon @diamondhands0 notice this failed on build, but (apologies) - I'm not familiar with go and there's no debug return to indicate the cause - could be as simple as...

Update: build now succeeds. Syntax corrected for: - comments (use of /* ... */ in additional node comments at end) - *string replaced with standard string for the optional URL...

Thanks @carry2web. Simple example of why and how this would be useful: - live listing of active API services (e.g. monitoring tools) - catalogue/live listing of apps/front-ends on the deso...

Further thought: Might be more logical for URL to represent the front-end location (as most currently are as such) - dropping "FrontendURL" Instead, add a "BackendURL" key for the API/backend...

@lazynina thank you for reviewing and I agree completely that an on-chain, decentralised, solution would be much better... but, in the meantime the front-ends still need to be able to...

@lazynina thanks - appreciate that. I think (in fairness) he needed to get going and hadn't received any update on the PR (but can't speak on his behalf). While, I'd...

Thanks @lazynina, I'll investigate further. This is a new docker container arrangement. Previously archival w/ pg was consuming >38gb ram continually (just syncing), but this time it's down in the...

Just to support @carry2web's PR - it'd be great to get the first of the SafetyNet nodes included in the official list. EDIT: I'll post the suggested changes as a...