thanks for illustrating the corpo speak

I hope the bug is fine

def possible, cloudflare DDoS their own dashboard a few months ago with some react code

https://blog.cloudflare.com/deep-dive-into-cloudflares-sept-12-dashboard-and-api-outage/

tbh, with those hips I might eventually join the robots

Lunar lake is x86-64 https://en.wikipedia.org/wiki/Lunar_Lake

Intel said that with Lunar Lake, it aimed to “bust the myth that [x86] can’t be as efficient” as ARM.[3] Analysis of tests performed on Lunar Lake CPUs available at market launch indicated that, although their multi-core performance was not particularly good under full load, their efficiency under everyday use was good, even if the ARM competition still has its advantages.[4]

“amazon leo” is distinctive enough

I cracked down on amazon, I highly recommend it

thanks, I had to restart to see the change. Why is a “text color” being used as background though

definitely doesn’t look as good as the GTK did, but I hope they simplify the interface at some point There’s no reason to keep these 3 menu areas, just bundle them together in tabs or one side menu to keep the hierarchy of players and effects under output/input.

edit: it’s actually 4 areas counting the preferences at the top right

mine has this brown color in some places and idk where I could change it in the KDE theme/settings

That’s the neat part: you don’t. If their idea of anti cheat means taking over my machine to scan everything that runs on it, it’s a lost battle. Either find a way to do it server side based on behavioral heuristics, or don’t bother.

sir, this is a wendy’s

this might be the best github fork atm

https://github.com/nel0x/syncthing-android-gplay

wth

parallel thread https://forum.syncthing.net/t/does-anyone-know-why-syncthing-fork-is-no-longer-available-on-github/25661/6

I don’t know for sure, but probably another repository reset in progress by @Catfriend1.

There was a temporary similar “outage” back in July with rewritten history, apparently something inappropriate was recorded in the repo history they wanted cleaned out. The repo came back after that. I have no idea if this is the same thing, or if they just got tired of maintaining it. Could be an opportunity for someone else to step up with a mirror, if they wished to. (Maintaining open source software is a largely thankless chore, FYI :wink: )

“never trust the client” is pretty much a motto of infosec, idk what the hell game devs expect

I think you need something like restic with a retention policy

https://restic.readthedocs.io/en/stable/060_forget.html#removing-snapshots-according-to-a-policy

--keep-{hourly,daily,weekly,monthly,yearly}

other solutions that implement similar policies are kopia and rustic

the advantage of using an off the shelf solution is that it’s almost certainly more reliable than what anyone can come up with in a few hours, and, it works with incremental backups, so your space requirements are drastically reduced depending how often you run it.

see Ivan? Dead code cannot have bugs

in other news: software has bugs

No, people have different needs. By all means, stay on x11. Just don’t pretend Wayland is a fad that’s going away in a couple years or that a re-architectured window manager for the 21st century has no value.

ah that was so annoying, and nowadays using tiled windows, that’s something I don’t see myself doing anymore

nuke it, you (probably) won’t miss it