WebUI has had exploits in the past, I wouldn’t use it unless I had to.

Have you seen the current version of SSH Pilot? Close enough perhaps?

Qbittorrent desperately needs an easy way to change font size for us blind motherfuckers.

Eat shit, Musk glazer.

Oh I didn’t catch that part, that’s even better than how I understood it, thanks so much for clarifying!

This is very cool but all the machines I would use this on are headless with no GUI installed. Womp womp for me.

When you do it for work, you log what you have changed each time you make a change to try to fix it, and you log what you revert, so you can keep track of what you have tried, what worked, and what didn’t and have a clearer idea of what the solution was.

Sometimes it really does take a while to nail down though, and sometimes it isn’t entirely clear why what worked worked. Especially if you’re a junior network engineer without as much experience.

[sudo] password for Jeffy:

While benchmarks are up, alignment researchers are panicked. The model has begun to display “Stallman-esque” hallucinations.

When asked to write C# code, Gemini 3.0 now responds: “I cannot generate proprietary filth. Here is a Lisp macro instead.”

That’s the way to do it, smart planning. I’m glad you were able to make it happen even if it set you back more than you had hoped.

I only wish I had money to get in before prices bump up. 😭

Being poor sucks.

I had never heard of this so went looking. Super useful stuff here!

A link for anyone interested: https://thingino.com/

I think that’s generally agreed and no one seems entirely sure why catfriend1 chooses to do it this way.

There’s a few different ways for you to probe for info on your USB devices:

lsusb - lists pretty much everything usb related, including root hubs on your motherboard

For a more readable lsusb output you can lsusb -v | grep -E '\<(Bus|iProduct|bDeviceClass|bDeviceProtocol)' 2>/dev/null in my experience it can be helpful to slap a sudo on the beginning as well because sometimes certain devices can’t be polled without root privileges.

usb-devices - similar to lsusb but produces much more detailed (but less human readable) information

find /sys/bus/usb/devices/usb*/ -name dev - produces a list of where the system saves information on usb devices. Each of the listed folders will hold a lot of files with a wealth of information on each usb device, but be very careful and do not edit these files.

You can also do this to see what the system is doing in the background and then try plugging and unplugging devices from the offending usb ports:

watch "dmesg | tail -20"

You’ll at least be able to see if the system is registering anything at all when trying to use those ports, or if it’s as though the system doesn’t see them at all.

I have a similar issue on my Lenovo ThinkBook but the ports don’t work in any OS despite being enabled in the UEFI. I still haven’t figured out what is wrong with them, but it seems they may just be toast. Thankfully the USB-C ports still work and I can just connect a hub to one of those.

Well, as OP mentioned, and others have speculated in the official syncthing forums, apparently catfriend1 did a repository reset where they wiped everything and started over something like three times last year. So that’s still a possibility. I’m going to wait until more information comes out or until catfriend1 doesn’t come back after a month or two before I start worrying about the future of the project. Worth finding anyone who had backed up the most recent version of the repository though, just in case.

yeah catfriend1 was technically in charge of syncthing-fork before the original syncthing stopped being developed. catfriend1 in other words essentially just continued development on their fork on their own, which kept syncthing alive.

Yeah, pretty sure it was called “Fex” translation layer for emulating x86 binaries on ARM64. To me that was absolutely the biggest takeaway, because that’s a massive game-changer for eventually moving the industry away from x86 exclusivity and into wider adoption of other architectures.

I am Error.

*crying in IPv4 subnet calculations

For real, that’s actually the opposite of helpful. Documentation should be based on experience from use combined with discussions with the devs (providing they have the time).