- 2 Posts
- 21 Comments
For those wondering who he is: https://en.m.wikipedia.org/wiki/Gary_Marcus#Artificial_intelligence
5·5 days agoGoogle’s instructions are generally good: https://source.android.com/docs/setup
But if you want something a little gentler: https://www.androidauthority.com/build-custom-android-rom-720453/
23·6 days agoNTP is one of those fundamental working parts of the internet that nobody has to think much about, because it works so smoothly.
It’s taken for granted, like the lights will come on when you flip a switch. But there’s SO much more to make that happen.
Came across this a few weeks ago. ATProto plugin for Wordpress: https://wordpress.com/plugins/neznam-atproto-share
Combined with the existing https://wordpress.org/plugins/activitypub/ ActivityPub and RSS/Atom support, it should be possible to post once / share everywhere.
I was one of those. Happily discovered Voyager. I go back, usually when a search link takes me there.
The mobile app is designed by people who I only imagine get paid by the bulk number of raw clicks/taps on UI elements.
Signal could improve its user interface around groups and people with duplicate display names.
Nah, they really shouldn’t. Way more fun this way.
10·13 days agoAt one point in my life I was working on a massive Android AOSP fork that itself had lots of variants for different downstream devices. Custom drivers, specialty services, etc. Thousands of people were actively working on all parts of it, and it had been around for at least a decade.
There was incredible tooling around onboarding, local dev, testing, PR management, CI/CD, and post-release telemetry. Almost everything was automated. All code was reviewed at least once, and sometimes more for critical components. It was an immediate rejection if there wasn’t sufficient test coverage. Big subsystems took months to architect, build, and deploy.
Nobody got to cowboy things and just push to release. It was much slower than a solo or a few people at a startup. The whole point was consistency and predictability, and you could see why.
So this showed up last week: https://github.com/raminf/RoboNope-nginx
Similar vibe, minus the AI.
Github actions and docker containers. A match made in heck.
Say it isn’t so…
26·19 days agoRFC 2549: https://www.rfc-editor.org/rfc/rfc2549
This problem was solved years ago: https://spectrum.ieee.org/pigeonbased-feathernet-still-wingsdown-fastest-way-of-transferring-lots-of-data
“Think of how stupid the average person is, and realize half of them are stupider than that.” ― George Carlin
There’s a very simple solution to autonomous driving vehicles plowing into walls, cars, or people:
Congress will pass a law that makes NOBODY liable – as long as a human wasn’t involved in the decision making process during the incident.
This will be backed by car makers, software providers, and insurance companies, who will lobby hard for it. After all, no SINGLE person or company made the decision to swerve into oncoming traffic. Surely they can’t be held liable. 🤷🏻♂️
Once that happens, Level 4 driving will come standard and likely be the default mode on most cars. Best of luck everyone else!
deleted by creator
So… if you own an inexpensive Alexa device, it just doesn’t have the horsepower to process your requests on-device. Your basic $35 device is just a microphone and a wifi streamer (ok, it also handles buttons and fun LED light effects). The Alexa device SDK can run on a $5 ESP-32. That’s how little it needs to work on-site.
Everything you say is getting sent to the cloud where it is NLP processed, parsed, then turned into command intents and matched against the devices and services you’ve installed. It does a match against the phrase ‘slots’ and returns results which are then turned into voice and played back on the speaker.
With the new LLM-based Alexa+ services, it’s all on the cloud. Very little of the processing can happen on-device. If you want to use the service, don’t be surprised the voice commands end up on the cloud. In most cases, it already was.
If you don’t like it, look into Home Assistant. But last I checked, to keep everything local and not too laggy, you’ll need a super beefy (expensive) local home server. Otherwise, it’s shipping your audio bits out to the cloud as well. There’s no free lunch.
This shows how one company (li-cycle) that claims they recycle 95% of the lithium does it: https://youtu.be/s2xrarUWVRQ
99.99% doesn’t seem too far-fetched.
USB hubs.
Plain old splitters will almost certainly damage the port, and if this is with a machine where USB-C is part of the motherboard, it could cause even more damage and be really expensive to repair.
The power-only ones are not too pricey. But if you also need high speed data transfer (like drives) those cost a bit more. Be careful that even the ones that claim data exchange may not support drive speeds. It took me three tries to finally find one that worked.