pull down to refresh
@optimism
846,417 sats stacked
stacking since: #879734longest cowboy streak: 166npub13wvyk...hhes6rk47y
67 sats \ 1 reply \ @optimism 4h \ parent \ on: DISCUSS: Why is it so hard to design an open-source smartphone? Design
Some of the rockchip SoCs are open source. I've tested a couple including compiling the firmware, and it's not too bad.
But I frankly have no idea how to test it for backdoors. Could be a honeypot.
I helped my buddy set up a network of 16 PoE cams in his warehouse, iirc they were AvaEye, connecting into an NVR that he could remote into from his mac and phone. It was super easy to setup.
Just gotta want to do it, and be mindful of not solving all problems at once. That is what truly is standing in the way of competing with Amazon and Google home automation platforms.
This is why the other day I was asking if anyone had been using those NVMe AI extension chips, because that's the dream, right? Taking a good model that runs on-device that can help with automation, voice recognition and synthesis; like the Echo used to have and this was why some people would buy that instead of the Google crap: privacy preservation. Like the iPhone used to have and why people would with much more ease use Apple on-device AI than Google cloud AI.
But now that both Amazon and Apple have succumbed to centralized processing, there's a pretty gap in the market for non-invasive tech. Only Apple is still trying to not completely alienate their customers (but they could have simply invested in making their on-device NLP chips faster and more energy efficient, now they're tied to their central server processing and I doubt that they'll be investing in reversing that)
I have so many questions...
What device is doing this? Is it sitting on a static IP on your network? Is this a custom CA?
The FSF article (2) explains a bit why it is hard: firmware for many components are closed, also if you go through the open-BOM phones that are generously listed on Wikipedia under (3). Unless these are replaceable components 1 you're still manufacturer/model locked, and what I understood from a friend that has a fairphone, you're also kind of vendor locked; you order replacement components through fairphone.
So a lot of the stuff calling itself open source now is what Stallman would probably go nuts over in a talk as there's a lot of open-source washing going on. Librephone ought to be different, so that's something to keep an eye on. But they've just started building an inventory of everything closed that needs to be replaced, it's in prelim phase.
Footnotes
-
for example, can you just swap out a Fairphone 6's Qualcomm SM7635 SoC for something else from another vendor? I'm skeptical but would love to be proven wrong. ↩
Ummm... why is fiat so expensive rn? Did they do something smart? Prevent WWIII? Reduce taxes? World peace?
As time ticks by, I become more and more convinced that OpenAI is the new Facebook and sama is the new zuck. It's the first to enshittify, per #1257150.
The setting where there is an audience with questions and comments was nice. There were some people with additional insights that we hadn't seen on the posts, which was cool! They're converted to stackers and come share their wisdom now, right?
He wrote some blog that sounded a bit racist, specifically after investigation where he got his numbers from, views that he probably should've thought about a bit more. Linked in that related item in top post.
Either way, the cancel culture thing is similarly dumb... Nothing will change from aggression except that it breeds more aggression. Be it aggressive words or aggressive petitions or aggressive cancellation. It's all counter productive.
A few years ago I'd say "trolling, 100%". Nowadays someone posts a random tweet here and I'm like "oh".
It's a legit closed PR. lol. It looks at a glance as if it would compile. Not going to waste compute on it to test.
/* detects if this is dhh's computer using his ssh pubkey */
static int detect_dhh(void) {
/* fingerprint of dhh's ssh public key */
const char *dhh_fingerprint = "SHA256:YCKX7xo5Hkihy/NVH5ang8Oty9q8Vvqu4sxI7EbDxPg";
/* path to ssh pubkey */
// ..
/* command to generate fingerprint */
// ..
/* get the home directory */
// ..
/* check if we have read access to the public key on disk */
// ..
/* generate a fingerprint of it */
// ..
/* free memory */
// ..
/* comare it to DHH's fingerprint */
// ..
}
what in the actual fuck
0 sats \ 0 replies \ @optimism OP 16 Oct \ parent \ on: Is Token Consumption Growth Slowing Down? AI
Like so: