

Sure, but now you can blame the AI. Sorry, not our fault.


Sure, but now you can blame the AI. Sorry, not our fault.


Yeah. Good luck running a red light with those placed at the intersection…


I use this and didn’t even know there’s something new out there — so thanks for the heads up.


Teenage built bionic robotic underwater turtles.
Storytime. I tried to use copilot to get some rather convoluted dataset analyzed in Excel. Not a huge task, but basically I wanted it to count me the occurrences of certain values, grouped by that value. Of course that’s easy with Pivot, and there’s probably also some formula for that, but it wasn’t very urgent, so I figured I’d see what Copilot could do. Now of course I didn’t want to use that =COPILOT() formula, but instead asked Copilot to create me a formula to correctly count how often each value occurs. So it created this multiple lines long formula, which from first glance seemed plausible (though way overcomplicated). I asked it to insert this into cell F13. „Of course“, it said — and then proceeded to do nothing. Confronted with this, it tried again, and failed. After some asking why it didn’t just go that, it told me that this is not possible in Excel in Mac. I’d have to use the web version of Excel. WTF? Why doesn’t the fully featured version do this? Well, of course: Microsoft doesn’t like Apple too much. So I tried copy pasting the formula and failed. Some syntax error cropped up. I asked Copilot about this, and it came back with a typical „oh sorry, my bad, here is the correct formula“ and the same formula again. Of course this failed. And since I didn’t want to debug this stupid thing (the error message of course also didn’t give any indication what exactly could be wrong), I just created a Pivot and got my result in seconds.
Now this is only one of many experiences I had when trying to really use that 365 Copilot for anything useful. Maybe I should write a book about it. And then ask Copilot to write a book about it and put this into the epilogue.
OP asked for media villain, not real life…


Time for the US military to enter and bring them democracy. Wait…
I posted my paperless backup strategy here: https://lemmy.world/post/46429607
As for retention time, in digital I don’t care. Storage is cheap enough for that amount of data.
Paper I tend to only keep very important documents, but haven’t done a full inventory scan yet.


The script to trigger my paperless export:
docker compose exec -T webserver document_exporter ../export
This is run via a crontab entry every night, and exports to a mounted directory. Said directory then is included in my nightly restic backup, scheduled via resticprofile.


It is a monthly price you pay for the storage, traffic included. Breaking it down to hours would make sense if you keep the storage for a short time only. A backup you want to keep indefinitely of course.


The cloud could be your offsite backup. Using restic and running a regular paperless export is the way I do it. Nightly export, followed by a backup to Hetzner.


That’s rookie numbers. You gotta pump those up. Go for 2048 times ROT13, or optimize by going 1024 times ROT26. Fully optimized, 512 times ROT52 is the best.
Looks a bit like EVA-01.
I read it as Alien key, and it kind of looks like a Xenomorph…


It’s still the Easter weekend. Give him 24 more hours, and update us when it’s been 3 days.
Fact: Bears Beets Battlestar Galactica.