If possible and not make other properties significantly worse, then, of course it is needed.
For me the opposite looks like scam - work for us for month and you will get something. Maybe. Or, more likely, something will change and you will need to work 11 months more or you will get no money for that 1 month.
If you can test all steps in hours or days, then there will be much less opportunities for something like that to happen. Or you will loose days or hours of work and not months or years.
maybe split it in three scripts and the parent script calls the other two in succession so that 1st script installs safe and second script runs safe commands?
when running the command to install safe it adds to PATH safe. well you need to refresh the PATH that is available so that it can then run the next safe command!
use hash -r after the safe install script
also hostname -I (thats a i uppercase) gives you the local ip address
edit: hostname -I gives the ipv6 in my linode so scratch that
Tell me about it - thats why Scotcoin is just another shitcoin now with nothing special to distinguish it from any other ERC-20 token. /me fails to be Lambo driver again
Not saying I agree with this necessarily but even a number counter on the nano scale or smaller that is ticking quickly from the get go will make people stick around for an eventual payout.
Some exchanges do this to appeal to peoples instant gratification to keep them staking through them and you have to wait for the payout period before you can run off with it but by the time they are back to check the released rewards they have new rewards building that they won’t get till a future release time so at some level it seems like it’s always working for you and they are more likely to stay.
Maybe that feels tricky but if a certain amount of reward is earned and you can give some kind of goal post or finish line that doesn’t move too much, you can make building up to that look like a steady stream of income, even if it is small.
The main benefits are that it could
increase participation
keep users from feeling rejected
do some small non consensus work for the network
include smaller, less (adult or elder worthy) capable devices
give people with capable enough machines such as desktops a sense of accomplishment as they work closer to joining as an official node and be rewarded more handsomely
If payout amount is known for sure, then why not pay frequently?
If not, then counter aka progress bar will be fake/scam.
Did you encountered progress bars stuck at 99%?
I wonder if a client could, maybe with some help from the network, provide an estimate of the remaining time to join the network? Like a progress bar but ideally based on something statistical.
Actually this might be an app that attempts to estimate various metrics, one of which could be used to provide a kind of countdown. A question for bigger brains, @mav?
Obviously with blockchains it’s different. There are calculated rewards based off blocks and some only distribute rewards after so many cycles so even if you stop at some point you still would be paid but not until a set time still. The way it’s displayed in these exchanges isn’t dishonest it’s just appealing to peoples instant gratification by showing smaller increments building up fast. That is my main point.
I don’t know whether SN could release them instantly or not but if there is no reward up until a certain point then perhaps displaying it another way would be better. Getting paid for work you did makes sense but so does not getting paid if you didn’t complete a job, imo. So really could go either way.
Maybe this could be made into a variable as well, so the number can be easily edited up top along with the others. Does the number stand for seconds or what?
willie@gagarin:~/wof$ safe cat safe://hy8ayqyyb1jiokniu9oou954rra7msjxxus9yg1zwytf3py4eh1xyt1ifch5y > Superfly_1972.mp4
Error:
0: NetDataError: Failed to GET file: NoResponse
Location:
/rustc/02072b482a8b5357f7fb5e5637444ae30e423c40/library/core/src/result.rs:1911
Backtrace omitted.
Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
