IME the longer I wait, the higher the chances of an update break something, so I update my main desktop multiple times a day.
IME the longer I wait, the higher the chances of an update break something, so I update my main desktop multiple times a day.


yeah, and I’d say that discord is even more harmful than github as information goes there to die. It’s a waste of everyone’s time: people helping need to repeat the same things all the time, and people seeking help can’t find shit.
Every time I read something like this it comes to mind that we’re more likely to remember the good bits of the past than the struggles. People use containers because the “works on my machine” problem was a constant pain.
You can still ship code into production quickly if you pair program and commit to trunk to bypass the code review process, and have a CI/CD pipeline set up to automatically build and publish the package.
And I’d much rather have a cloud env pull my code and automatically deploy something than manually transfer files over FTP.


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
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.
TL;DR: the original fork of Syncthing under the GitHub user
Catfriend1vanished without any clarifications from them to the community. Recently, another GitHub userresearchxxlacquired the release keys and published a new versionv2.0.12.1:The new version
v2.0.12.1underresearchxxlseems to be free of malicious code, and the repo has reproducible builds.Since the whole situation is a bit sketchy, some are advocating for the F-droid account to be locked and any release after
v2.0.11.2to be purged.Update: it seems that as of a few hours ago,
Catfriend1broke the silence and confirmed the transfer toresearchxxl:https://forum.syncthing.net/t/does-anyone-know-why-syncthing-fork-is-no-longer-available-on-github/25661/165