So something like:

 sh

    
nft -f newrules.nft; sleep 2m; nft destroy table ip newrules


  

 undefined

    
# newrules.nft
table ip newrules {
  # …
}

  

As long as you run this in tmux, your new firewall rules will be dropped if you don’t cancel this in 2 minutes.

That sucks, good to know.

Looks like creating a VPN is the only option for securing jellyfin.

Not unless the reverse proxy adds some layer of authentication as well. Something like HTTP basic auth, or mTLS (AKA 2-way TLS AKA client certificates)

For nginx: https://docs.nginx.com/nginx/admin-guide/security-controls/configuring-http-basic-authentication/

so if I add a user ”john” with password “mypassword” to video.example.com, you can try adding the login as: “https://john:[email protected]/

Most HTTP clients (e.g. browsers) support adding login like that. I don’t know what other jellyfin clients do that.

The other option is to set up a VPN (I recommend wireguard)

Good luck UK comrades.

Don’t forget to protect yourself from surveillance!

Surveillance Self Defence: Attending a Protest (EFF)

Exactly. The same goes for implementing social welfare in the face of the Soviet Union and local communist movements.

It’s also very Liberal propaganda.

Martin Luther King Jr. protested and he won so peaceful protest works!

While of course barely mentioning the Black Panthers and how MLK was suddenly a reasonable alternative to their violent resistance.

The mods from 196@blahaj suddenly wanted to migrate to lemmy.world

https://lemmy.blahaj.zone/post/20937206

And not everyone agreed.

Ada also made a post about it: https://lemmy.blahaj.zone/post/20968775

You could at least mention the European Citizens’ Initiative…

Calvin? Calvin Klein?

No, you don’t need to do that.

All the source code of your dependencies are stored in ~/.cargo/registry^1. Which doesn’t lead to conflicts.

And the compiled versions are stored in the target/ directory in your project directory^2, so there’s no conflict there.

1: that is configurable with CARGO_HOME, I have that set to ~/.cache/cargo

2: That is configurable with the build.target-dir option. I have that set to ~/.cache/cargo/target so that build artifacts don’t end up in my backups :)

Thanks!

I did not expect this great a read…

It took me a while to finish, but I am impressed by both the style and substance, and the way so many disparate subjects are combined so well in a cohesive whole.

Thanks for posting.

Ootl, what happened?

Is that an interrobang‽

More like killedbygoogle.com