ben

joined 1 year ago
[–] ben@lef.li 2 points 7 months ago

Debian Sarge which was testing back then. Woody was stable.

[–] ben@lef.li 6 points 8 months ago

Ahh yes. Good ol' Michael Reeves. Awesome.

[–] ben@lef.li 3 points 9 months ago

Oh dang, I need to rebuild that one as well by chance. Still running on Buster...

[–] ben@lef.li 47 points 9 months ago (1 children)

With that logic they should sue the creators of the AV1 codec as well. Lots of pirated movies will be encoded with it....

[–] ben@lef.li 1 points 9 months ago

My best guess: Ignorance is bliss.

(As for me I deleted my Twitter account that moment Elon bought the platform).

[–] ben@lef.li 6 points 10 months ago
[–] ben@lef.li 11 points 10 months ago (4 children)

So.... Bentoo? Bintoo?

[–] ben@lef.li 5 points 11 months ago

Better mainline support for RK3588 SoC

[–] ben@lef.li 4 points 11 months ago

Indeed. Immich is the way to go. While stating heavy development I find it quite stable. Did not have major issues with it. However I don't use their interface much. I just use it as 2nd backup location to automatically upload stuff from my phone to something else than the big G.

Obviously this need some sort of server but a VPS will do.

[–] ben@lef.li 8 points 11 months ago* (last edited 11 months ago)

Use a firewall to block all outgoing packages through all interfaces but lo and tun (or wg for Wireguard). Like this for iptables:

-A FORWARD -j REJECT --reject-with icmp-port-unreachable
-A OUTPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
-A OUTPUT -d 1.2.3.4/32 -p udp -j ACCEPT #replace with public IP of your VPN you try to connect
-A OUTPUT -p icmp -j ACCEPT
-A OUTPUT -o tun+ -j ACCEPT #replace with wg+ for Wireguard
-A OUTPUT -j REJECT --reject-with icmp-port-unreachable

If you are paranoid you could mess with INPUT table as well but if OUTPUT is configured properly nobody well ever know your real IP address.

Not sure how well this works with Docker and such, I use LXC containers.

The funny thing is that I am actually seeding Linux ISOs (yes, real ones). The reason I am using a VPN to seed those is because the ISP is complaining about random peers hitting (non-existing obviously) addresses in private IPv4 ranges (like 172.16.1.1) and instead if simply dropping those packages at the switch ... oh well. I guess some people have multiple peers connected to each other via private networks but external peers don't know about these connections and simply try to reach them on their private addresses over public internet.

Anyway yeah I could mess with routing table on my server and null-route those ranges but I have an active VPN contract already so why not using it?

[–] ben@lef.li 7 points 1 year ago

Leslie Nielsen would be perfect.

[–] ben@lef.li 1 points 1 year ago

Might be a bit too early to be the judge of balancing since it has been just a few days. But for now all I can say is it looks promising.

view more: next ›