This is basically Claude Code with less extra steps

It does not follow that merely looking at or altering the generated code makes it acceptable. By the rules that have been adopted, a contributor cannot take substantial implementation produced by an LLM, clean it up manually, and then treat the resulting patch as if it had been originally written by them.

I wonder how they intend to enforce this one. Raw LLM output will trigger some kind of “Spidey sense” for anyone woo has seen enough of it. But I don’t know how I would tell manually cleaned up LLM output apart from manually written original code

Yeah, I could see a credential stealer being smuggled into an alternative frontend…

It also made my browser freeze for a moment when I first found and loaded his page before I blocked all JS from his domain. Not stealthy at all… Many nerd (like most of us lemmy users are) will instantly open devtools when a random page that’s supposed to be just text freezes the browser for a second.

Like, c’mon man, setInterval with even 10 ms of delay would have made the attack both stealthier by not insta-freezing the brower on load, and more efficient by getting way more than 2000 request out of each reader…

Also, their website seems to be down now :)

I did not follow this drama, and I don’t know about this list everyone is mentioning. Is this something that hides specific users posts and comments from the Tesseract UI ?

“Apparently only three people who aren’t me actually want a place that’s not just a circle-jerk of rage and hate.”

I think this is the best part of their message

I never knew this fun fact ! I’ll try to use it with my students, and see if I this gets me more attention when I give them the trick to compute powers of 2 in your head (2¹⁰ =~ 10³, which leads to ln(10³) =~ 10*ln(2) ).

For anyone wondering, the trick is : Powers of 2 below 10 are easy enough to remember or just compute in your head. So if you want to approximate 2^x, write it as (2^10*a)*(2^b), with a=x//10 (integer division) and b=x%10 (modulo). b will be 9 or less, so 2^b is easy to compute, and 2^10*a = (2¹⁰)^a =~ 1000^a is also easy to compute.

For instance, 2³² = (2³⁰)(2²). Since 2³⁰=~1000³ ; and 2²=4, then 2³² =~ 4(1000)^3 = 4 billion. Once you get used to it, you’ll be able to say that 2⁶⁴ is approx 16 billion billions in no time ! :)

Me, after I did sudo rm -rf /mnt/chroot when my whole home directory was still bind mounted inside the chroot…

This was before ChatGPT, guaranteed 100% natural stupidity

I’m in France timezone so hopefully we can find a time of the day that works for both of us, but feel free to DM me here or on Matrix (@pcouy:matrix.pierre-couy.fr)

I was about to type pretty much the exact same thing, but I figured it would already be here for me to upvote :)

The ansible role I made does not cover this. If you make a server an exit node for a network, the server gets configured to forward everything that comes from the wireguard network. Since my use case does not need this, I don’t think I’ll add it, but the role could be expanded to support ACLs by taking inspiration from how it deals with port forwarding.

Do you have specific examples of the “different firewall requirements” ?

I have a custom made ansible role that does what you are asking for. I’ve wanted to clean it up a bit before putting it up on Github, and your post just gave me a motivation to stop procrastinating it :) This was initially made for my own use, and I’m not an Ansible expert so it can have some rough edges, but I tried my best to make it adhere to the Ansible way of doing things (applying the same role to a host twice should be idempotent).

Using this role, I’m able to quickly define wireguard networks, define which peer participates in which network, optionally configure a peer as a router (with NAT and port forwarding) for a given network. For Ansible-managed hosts, it installs wireguard, generates and deploys wireguard configurations, and enables IP forwarding on exit nodes. It can also generate ready-to-deploy wireguard configurations for externally managed hosts.

The repo is at https://github.com/pcouy/ansible-wireguard . I tried giving some instructions in the readme but they may not be detailed enough. If you try it, please open an issue for anything that’s not clear enough from the readme so I can improve it. (I tried making a “Quick start” section for people who never used ansible before)

I did something similar for digitizing old camcorder family videos. I hooked up a VCR through a cheap elgato RCA -> USB capture card to my home server, and did something similar to you with a preview feed available on my LAN.

I even built a (really ugly) web UI which lets me pick an audio and video source, start the preview stream and display it in the browser without actually starting the capture, then start/stop the capture, edit the ffmpeg flags, and set the output file name. I can share it with you if you are interested

We actually moved recently from GPLv3 to MIT to be fully permissive.

Can you explain how this is a good thing for users ? From my own (admittedly limited) understanding of licenses, the main difference between GPL and MIT is that MIT allows freeriding off open source project by making closed-source forks.

CEC works fine with kodi on my raspberry pi (kodi on top of RPiOS, I did not try libreElec) plugged to an old-ish TV, and it’s really nice to have. The Pi puts the TV into standby and wakes it up, and I can control Kodi with the TV’s remote

A few years ago I deleted my whole home folder by bind-mounting it inside a chroot. When I was done with the chroot, I rm -rf-ed it without unmounting my home first.

After trying to run postmarketos on an old phone of mine, I’m really excited for anything that improves support for android devices to mainline linux !

I usually have Debian on all my servers for stability, and run almost everything inside containers for convenience. The few things that run directly in Debian are nginx for reverse proxying to container services, fail2ban+firewall, and wireguard for everything that moves data between servers/computers/devices I own

Debian is already noiriously lagging behind latest package versions (that’s how they make it so stable : they freeze all package versions when they release a new version of Debian, and only backport security fixes).

Either your AI was trained before Debian 13 came out, or it is giving you really bad advice. I can’t think of a single good reason to use an older Debian for a fresh install…