Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
the functional difference is that this does it once. you could just as well accuse git of being a major contributor to global warming.
hash algorithms are useful. running billions of them to make monopoly money is not.
Which party of git performs proof-of-work? Specifically, intentionally inefficient algorithms whose output is thrown away?
the hashing part? it's the same algo as here.
That's not proof of work, though.
git is performing hashes to generate identifiers for versions of files so it can tell when they changed. It's like moving rocks to build a house.
Proof of work is moving rocks from one pile to another and back again, for the only purpose of taking up your time all day.
Proof of work is just that, proof that it did work. What work it's doing isn't defined by that definition. Git doesn't ask for proof, but it does do work. Presumably the proof part isn't the thing you have an issue with. I agree it sucks that this isn't being used to do something constructive, but as long as it's kept to a minimum in user time scales, it shouldn't be a big deal.
Crypto currencies are an issue because they do the work continuously, 24/7. This is a one-time operation per view (I assume per view and not once ever), which with human input times isn't going to be much. AI garbage does consume massive amounts of power though, so damaging those is beneficial.
okay, git using the same algorithm may have been a bad example. let's go with video games then. the energy usage for the fraction of a second it takes for the anubis challenge-response dance to complete, even on phones, is literally nothing compared to playing minecraft for a minute.
if you're mining, you do billions of cycles of sha256 calculations a second for hours every day. anubis does maybe 1000, once, if you're unlucky. the method of "verification" is the wrong thing to be upset at, especially since it can be changed