dalvrosa

;)

That approach forwards everyrhing so can be used for multiple things (ftp, web, email, etc)

Thank you for the compliment <3

Thanks!

Agreed, it can be quite painful

How are captchas done?

Thanks for sharing

Agreed yeah. Mine has been up with no issues so far for ~half a year.

(There are solutions for CGNAT - https://david.alvarezrosa.com/posts/self-hosting-behind-cgna...)

Done now https://github.com/david-alvarez-rosa/homelab/commit/b495cbe...

Good call, I'd missed that. Adding it now, thanks.

That'd be an exit relay, not doing that atm, just in case

Fair point. Very small things like RSS, canonical link or og:url or microformats use absolute URL

To make sure once in the .onion, you never leave the .onion

Thanks for sharing! Happy to get feedback :)

Pinning the frequency is great for reproducibility yeah

For squeezing perf in prod better to overclock (with good cooling)

My Spanish ISP does not allow to use IPv6 unfortunately..

Thanks for sharing! Happy to get feedback :)

There is nothing more satisfying than owning, end to end, the software and the hardware you use without relying on abusive cloud corporations. Internet is us, not them. Break free from censorship. Learn how to self-host at home, and be truly /libre/.

Nice!

Fair enough yeah. IMO microbenchmarks are useful for trying to gain intuition and propose the next incremental improvement. In real world measuring is mandatory, if you don't want to risk pessimizing the code

Very good point, should add this

Yeah that's quite right, you shouldn't be using spinlock without pinned threads

Thanks for sharing! Happy to get feedback :)

Note that I don't recommend spinlock for most cases, only when there is a 1:1 mapping between threads and phsycal CPU cores, and only after measuring

Thanks for sharing! Happy to get feedback :)

Note that I don't recommend spinlock for most cases, only when there is a 1:1 mapping between threads and phsycal CPU cores, and only after measuring

Thanks for sharing! Happy to get feedback :)

Note that I don't recommend spinlock for most cases, only when there is a 1:1 mapping between threads and phsycal CPU cores, and only after measuring

Thanks for sharing! Happy to get feedback :)

Note that I don't recommend spinlock for most cases, only when there is a 1:1 mapping between threads and phsycal CPU cores, and only after measuring

Yep

Love it

Thanks!

A spin-lock is a lock that never sleeps. Instead of yielding to the scheduler, the thread stays on the CPU and spins. No syscalls. No context switches. In this post, we’ll build a version, step by step, that is 5.7x faster while drawing 5.4x less energy.

Not sure what you mean, but std::move is one of the greatest tools in C++