petterroea
4 hours ago
It is sad that it takes a Meta developer having some fun to realize they should open up ADB.
This isn't the repairability and reuseability of old devices mindset people have been begging for. This is some guy using internal privileges to having some fun, and deciding the rest of us should get a piece of the fun as well.
This is a "happy story" in the same way it is a "happy story" when some kid successfully fundraises a classmate's cancer treatment because the healthcare system neglects them.
KaiserPro
17 minutes ago
> It is sad that it takes a Meta developer having some fun to realize they should open up ADB.
Former facebook research lab twat here. It wasn't one dev.
We asked when they shitcanned portal (which was a great product, badly managed) to open it up. Infact one of the kernel devs made a very direct plea to allow the community to adopt the hardware so that we could avoid Ewaste.
It was denied because there are keys on the device that would leak if meta opened it up. (I'm not an android dev so I don't know the ins and outs of that)
However, portal was a casualty of the dash to VR. They scaled up the team briefly, which meant that lots of weird stuff was tried, but the roadmap was diluted. The idea was that they portal would be the "portal" to horizon worlds. this meant that they pushed back the plan for thirdparty app stores that would have meant you had something to actually do on the device.
neglect and stupidity from zuck meant that the portal was killed, even though the next gen device was actually a really great media device (wireless, removable charging stand, excellent speakers, but nothing to run on it.)
mft_
a minute ago
> It was denied because there are keys on the device that would leak if meta opened it up. (I'm not an android dev so I don't know the ins and outs of that)
Any idea what changed?
> neglect and stupidity from zuck meant that the portal was killed
Is Facebook really set up such that one person's whim is the single point of failure? Is there really no way for teams to progress projects with value somewhat independently?
jenders
3 hours ago
boz is the CTO
petterroea
3 hours ago
Even sadder. Turns out all we needed to not have our old devices locked down was the CTO having some fun
ashdksnndck
an hour ago
Why is this sad? I’m having a hard time understanding the thought you are communicating. It seems cool that a CTO had fun and that motivated him to enable ADB for everyone?
jazzyjackson
40 minutes ago
Just that the default reality is the hardware you buy belonging to someone else, who only really sold you a license to use the hardware on limited terms until the manufacturer drops support
mock-possum
6 minutes ago
It shouldn’t be left to the whim of a C-suite denizen.
gnfargbl
2 minutes ago
If the leadership of a company aren't the right people to make decisions about what that company does, who is?
Are you advocating for legislation? How would that work?
saagarjha
an hour ago
Why didn’t it occur to someone that this would be fun to do within the CTO having to realize this
l23k4
35 minutes ago
Why didn't it occur to someone without occurring to someone first?
saagarjha
33 minutes ago
Because the idea that something this obvious occurred to the CTO first is very, very unlikely. What is more probable was that leadership ignored people who disagreed until the CTO convinced himself it was a good idea and went ahead with it.
Forgeties79
34 minutes ago
Because it could’ve just as easily never happened despite how simple of a feature it is to enable. That happens all the time. Tons of “useless” tech out there that can be made useful with 5min of effort but the incentives aren’t there, so they end up in landfills.
The default position should be trying to make devices useful as long as possible, even if they want to qualify it with “so long as it’s sufficiently reasonable to do so.”
wfme
2 hours ago
*all we needed was the technical leader of the company that produced the product to...
the same could be said for pretty much any change or update rolled out by any of these companies.
petterroea
an hour ago
I feel like this is reducing the problem to a simpler one. Of course you'd expert larger product decisions to be made by a technical leader. The problem here is that devices being locked down is something being fought against, repairability is a big topic for discussion, and some companies even try to play into it pretty hard, like Framework and seemingly Valve.
Yet, to this Meta CTO, this wasn't really a concern until he vibecoded something and decided everyone should be able to have this fun. It say's something about his (and probably other people in his position) awareness of public opinion and discussion.