For my own Rust project I require myself to have a comment for every unwrap call that explains why that unwrap will never panic. For everything else I let the function return an error, with help of the anyhow crate and error contexts.

Perhaps someone on your inatance was last subscribed to it 2 years ago. When you subscribe, your instance doesn’t tend to fetch older posts, only posts made after subscribing.

Your Lemmy instance only fetches posts from an other instance’s community if at least 1 person on your instance is subscribed to it.

unsafe {
   <the whole codebase>
}

Nice, thanks!

Also 4180 is not a standard (it says on the first page)

Probably pewdiepie. He was very popular before the incident, after which noone wanted to touch him. His Scare Pewdiepie show also got canceled. He has regained popularity again though.

This is an article fron 2006 btw.

Be careful, the actual logging can happen at a later time, and because the log function may take a reference to the value, if you modify r it may show the modified version of r in the logging instead of the original r.

Using -F with tail is even better than -f because it handles files getting truncated or getting created.

Exactly! This is why the server should just send a clear error message. 99% of the time the client just wants to show the error message to the end user, and not have to wrangle all kinds of normalized data into one.

This looks so over-engineered. Most of the time you only need an error message. Make the message clear enough so that it can be shown to the end user.

There is no investing in crypto; that’s called speculation or gambling.

Good article.

The article clearly states that some of the toxics were in the e-liquid.

Everyone in this thread: PHP sucks because it was bad when I last used it 20 years ago.

Those haven’t existed in PHP anymore for a very long time.

Well better late than never.

Thats what the firewall rules do too, don’t allow internet connection if there’s no vpn connection.

Firewall is a system-wide solution that always works, while qbt config relies heavily on the application implementing interface binding properly. Which it doesn’t fully btw.

Better to just configure a firewall properly so that no packets can go outside of the vpn tunnel.