Gridcoin-Tasks VS left-pad

Anyone interested should also look into Gridcoin, you can get some crypto back in addition to doing some good science.

https://gridcoin.us/

Gridcoin. Support science. https://gridcoin.us

Been around longer than Eth has. You can check out the mining/crunching guides at gridcoin.us. If you run into any questions hop on the discord people are happy to help

Generally in terms of best to run for earning GRC it's math > physics > health augmented by CPU/GPU. You can get an idea of which those are by looking at the whitelist on gridcoin.us. I would avoid sidock for pis, iirc their workunits are very read/write heavy which isn't great for an SD-card based system.

Gridcoin - This cryptocurrency rewards users for participating in BOINC, a platform for distributed computing that supports a variety of scientific research projects.

I run BOINC with Gridcoin… but you’re likely not going to make much, if anything, after electricity. It’s for science tho :)

And there's rewards for doing it - https://gridcoin.us/

https://gridcoin.us. It’s a project that incentivizes distributive computing.

I noticed Universe@home is no longer showing in my wallet whitelist, but cannot find anything on it being removed from GRC. This might be a dumb question, but can anyone give me a link to what happened? I don't see anything on this sub and https://gridcoin.us/ still shows it whitelisted, but I know that's slow to update at times.

Link to Github issue: https://github.com/gridcoin-community/Gridcoin-Tasks/issues/260

It's pretty easy to find that the example I gave isn't gamed... A cursory search on GitHub can find a couple examples like dotenv [1] and npm's cli [2] both use it via an older version of nodejs/readable-stream [3].

There's also the classic left-pad debacle - https://github.com/left-pad/left-pad/issues/4

[1] - https://github.com/motdotla/dotenv/blob/master/package-lock....

when using some other modern libraries like tailwind, you have to update the Next.js version carefully or you may have some errors following the Next.js update. Nothing new in javascript world, if something is working it's not guaranteed it will last :) It is important to really read the Next.js release notes as the base configuration may change in between the releases.

It's OK, it's reddit, it happens. I will say however that unless you are deploying to a windows server on premise somewhere you are using open source. (And soon even that won't be true because eventually Windows is going to be based on Linux.) I'm not asking people to give up their weekends or anything, but IMO if you consume open source, you have an obligation to contribute back something. Even if it's just reporting a bug on some library that you use.

Funny story, on the day that they unpublished it, the package.json states the license to be "WTFPL", which allows NPM to Do What The Fuck You Want To

It had been optimized (and deprecated) since then. See https://github.com/left-pad/left-pad/blob/master/index.js