the #Syncthing Android drama is exploding.

GitHub

status · Issue #16 · researchxxl/syncthing-android

Description of the issue status Steps to reproduce invite nel0x here and get help to carry on setup build and release: use old maintainers signing ...

@npub1z2ju...r69f at this point is being used to push out an app with sensitive permissions that's been taken over by an unknown individual who refuses to engage with its large community of users and developers. I STRONGLY recommend disabling updates from Fdroid, if not uninstalling and manually installing 2.0.11.2, or installing the Google Play version which has a different maintainer. this is extremely shady and it's just looking worse as time goes on. I'll link to the Syncthing forum thread from about where I left off last time in a subsequent post. #SyncthingFork #SyncthingAndroid

if anybody has videos and/or text resources which worked really well to burn #IPv6 concepts into your brain which was proving resistant to absorbing them previously, please share. boosts appreciated!

this morning I dreamed I was setting up a low cost wireless deployment for internet sharing & remote sensing on a small archipelago in the tropical sea

my struggles with the intel_pstate driver (and the ability to switch back to the ACPI driver) when trying to get the CPU in this box to clock above 0.8GHz, and my struggles with the box that replaced it spontaneously rebooting seemingly at random only when a display wasn't plugged in until I disabled SATA power saving in the UEFI gave me an idea, along with the recent boom in retrocomputing... this won't happen, couldn't happen... but imagine if somebody built a computer with the raw horsepower of a modern PC, but the absolute minimum amount of abstraction baked into the machine itself. at this point UEFI alone is orders of magnitude more complex than an entire DOS box from the early 90s. your "CPU" has multiple entirely independent CPUs with their own OS and firmware inside it, as does every so-called peripheral attached to it. imagine if you could access the compute power of a Ryzen 3xx, but it was as close to being a DOS box in complexity as possible while still being able to do shit like regulate the CPU clock rate, or talk to USB devices and NVMe sticks. *one* driver for each bit, *one* API for each bit, no nested Turing-complete systems wherever avoidable, no unnecessary layers of abstraction. it'll never happen for many valid reasons, but I'd love to see it.

I'm not sure why I didn't think of it in these terms earlier, but one aspect of how generative AI is ruining the web just occurred to me - my plan with the Surfhosting site is to embargo content behind a paywall, so basically you pay a (very reasonable, and by that I mean like $3 a year or something around there) fee and get to read articles 180 days before open access ... and depending how bad things get, I might also put portions of the documentation hub (the wiki-like portion of the site, rather than the blog-like portion) behind a similar wall. I thought of this just now because of the giant pain in the ass it was for me to work around the Dell CPU throttling behavior in Debian 13. previously I wouldn't have *dreamed* of doing things this way - I'd have just posted the solution somewhere as a public benefit, and not seen search engines which led people to it as violating the social contract, even if they profited by putting ads next to search results. but with scraper-fed #generativeAI, it feels very much like they're violating the social contract at my expense in order to transfer more wealth from my broke ass living an irl cyberpunk existence, to scheming billionaire scumbags like Sam Altman, and fuck every single aspect of that. so the content gets embargoed and everyone loses out to some degree. #genAI

okay, I found where past me got stumped last time with this box: `echo 0 > /sys/devices/system/cpu/intel_pstate/no_turbo` this fails when run as root in Debian 13, even with Secure Boot disabled, Kernel Lockdown disabled, etc. in dmesg there's a message intel_pstate: Turbo disabled by BIOS or unavailable on processor this is because the #Dell BIOS is disabling turbo due to running on a "non-genuine" power adapter. I was able to work around this in Debian 12 but so far the same tricks aren't sufficient in Debian 13.

hardware question: are m.2 E-key wifi slots basically all 2230 size? I don't want to take this machine apart and measure things if there's no chance the slot might be 2242 and thus fit an E-key 2242 to M-key 2230 adapter...

wow, I biked over to where I'm watching the cat and had a near-blackout experience on a busy road, I'm guessing because I was biking with a heavy load in panniers plus a heavy backpack, and the backpack restricted blood flow causing lack of return from my arms? something like that. scary af

the more this project of mine snowballs, the more it validates my decision 6 or 7 years ago to spend a couple weeks brainstorming for ideas that were likely to actually stick given my particular ADHD approach to life. I was in much the same position then as I am now, albeit with less knowledge and fewer resources. but I knew I needed a project that I'd keep coming back to, and that I'd get more invested in if other people found it interesting, in order to keep me coming back to tech when one of my biggest challenges with being able to work consistently has been distraction from life tribulations leading to all the mental spinning plates crashing to the floor over and over again. Surfhosting was born out of that brainstorming session. and I'm still working on it. progress has been slow, but it stuck.

here's some free advice for the MBA sociopath who came up with this bullshit: ingest microplastic and expire. 🖕