Cmon, this is not about naming, this is about non-generic code in generic header.

IMO hiding such a little operation behind a macro/function just hurt readability. Furthermore, considering that this function is only used once in the provided patch and that word ordering on RISC-V is not about to change anytime soon, it is perfectly fine to inline the code.

My 0$ knob

Sponsor block!

To be fair, unlike Signal and Matrix, Tox does not rely on external server, it is full P2P. In that regard, setting up a Tox network is infinitely simpler. Also, the only thing you leak is your IP address that end up in tox DHT, which is a necessity for peers to be able to reach you. It could easily be hidden behind Tor or a VPN.

Worktrees are great, unless you have submodules…

Archive of the wonderful article mentioned in the intro.

The temptation to open it drops to zero once you realise the box is full of shit.

Assuming you meant CSV, xan is wonderful for this.

Using ublock origin picker to remove everything useless. Like, Youtube suggestions, everything but download button on ddl websites, useless footers/headers on news, etc…

Advertising.

Cause it’s driving over-consumption, by flooding people brains with shit ideas, turning them into idiots in the process.

delta.chat

The enshittify proof alternative!

Hooray to Helix!

Parallel is great!

Alternatively your second command can be written as: parallel "copytags {1} {2}" ::: *.flac :::+ *.mp3.

Also it is nice to exec commands on multiple devices.

This only works for public torrents and with PEX enabled. For private trackers an open port is required.

Wrong, tracker provide IP and port of leechers, which is just what is needed to hole-punch. It is just slower, as the seeder fetch tracker info 1 to 4 times per hour, so by the time the hole-punched connection is established, leecher has already sucked up all the data from peers with open ports.

If you want to build up ratio on a private tracker with closed port, seeding a piece of a fat 100Gb+ torrent will do.

Bullshit, Trackers and DHT hold IP and port of peers, hole-punching technique allows to open both sides.

The only difference is the speed to establish connection:

• With an open port, it is done instantly as peers can reach you directly.
• Without, you need to wait for the seeder to fetch your IP from tracker (slow) or to recieve it from DHT (fast).

Now, the reason why it seems hard to seed torrents on private tracker, that disable DHT, is because seeders with closed port will only fetch leechers IP from tacker 1 to 4 times per hour, so by the time the hole-punched connection is established, leecher has already sucked up all the data from peers with open ports.

It’s fine to keep port closed if you avoid private tracker and DHT disabled torrents. If you want to build up ratio on a crappy private tracker, seeding a piece of a fat 100Gb+ torrent will do.

What about holepunching?

It’s Genius Party intro! https://youtu.be/XdL0VoG9S9k

Or maybe OP followed one of these enlarge you penny tutorial you find on the internet…

Wow… this is at least 3 times the world money stock worth of damage!