> … > The updated software, used to run Tor nodes, now supports a proof-of-work challenge called EquiX. Designed by Tevador, who developed Monero's proof-of-work algorithm, it is "a CPU-friendly client puzzle with fast verification and small solution size (16 bytes)." > > It appears this computation will not go toward cryptomining, which some may feel is a lost revenue opportunity and others may welcome as an ethical necessity. > …
@accretionist@torproject I donated to Tor just last week at DEF CON and I've run guard nodes out of my own living room as well as multiple exits. I believe Tor is absolutely essential.
That does not excuse promoting the use of cryptocurrencies and blockchains.
Each commit is a node that builds on its predecessor and branches are, well, branches. When you check out a branch and run git log, you're seeing the linear history of that particular branch from the most recent node to the root of the tree, often your "initial commit". HEAD is a pointer to whatever node you're currently at; when you git checkout an old commit, you're moving HEAD so it points to that older node. When you checkout main, you're moving HEAD so it points to whatever node is furthest down that branch.
Removing secrets from a repo is not feasible for large projects because it requires finding the commit introducing that secret and changing it. Because all child commits contain a hash of its parent commit, changing a parent invalidates every single one of its children and grandchildren and great grandchildren and so on. The parent has changed, so its hash changed, so its child needs to be updated to include the new hash of its parent. That cascades through the rest of the tree. You then have to force-push to your remote because your local tree has wildly diverged from the remote tree; you're telling the remote to throw whatever tree it has away (the one containing your secrets) and just accept the tree you're sending it (the one without your secrets). Your local tree and your remote tree are now the same … but your other contributors might have pulled the commit with your secrets. Now their tree is wildly diverged from the remote tree and they have two options: save their work somewhere else, rm -rf their local repo, and re-clone the new tree or do a git reset <commit preceding the one with secrets> and git pull.
Git reset <commit> discards all of the nodes on your branch up to and _not_ including <commit>. It's like pruning a branch that's grown too long; you cut it back then let it re-grow differently.
RustDesk is genuinely one of the most useful services I self-host. I just started rendering the Blender video for the next Linux Lads episode on my desktop on the other side of the US from a car driving to Las Vegas for DEF CON :cirno_UwU:
@lanodan now that's a fantastic idea; I literally added tracking the date earlier tonight because I knew it would be useful for something later on even though I had no idea what :meowLul:
I will still need to parse the tag names and treat rc, alpha, etc. differently though.
Preferably on platforms *other than* GitHub, Gitea, and Forgejo. Those three have RSS feeds that I intend to take advantage of. Gitlab, Bitbucket, cgit, custom git frontends, etc. would all be great. I'm looking for a variety of platforms to test against.
I’ve recently noticed that many of my peers are sometimes overwhelmed by the internet; they feel as if they’re stretched too thin and that their attention is constantly shifting between too many different platforms. I think a portion of that feeling comes from systems that bombard them with push notifications. Reducing that barrage — on all systems, not just phones — could be a great way to start building a healthier relationship with technology.
Dedicated Linux user, professional musician, sysadmin, and founder of NixNet, a collection of open source and privacy-focused services I make available to anyone for freeThis is my more professional account; I'll post about my blog, streams, NixNet announcements, etc. here. If you'd rather interact with me on a more personal level, that account is over on Misskey: @amolith@mk.nixnet.social I guess I'm finsexual :flagfinsexual: :akkowoozy:https://www.lgbtqia.wiki/wiki/Finsexual"Darling of the fediverse"— @nebunez@fosstodon.org amolith good admin— @alexandra@mk.nixnet.social#fedi22 #linux #musician #sysadmin #developer #technology #vim #emacs #doublebass #bluegrass #pipesmoking