On the bright side, maybe someone can get Claude or some other LLM to figure out how to crack it; and perhaps even vibe-code an alternative app.
On the bright side, maybe someone can get Claude or some other LLM to figure out how to crack it; and perhaps even vibe-code an alternative app.
LLMs are great for this, though the more people use it for blackhat style things, the more I fear they will lockdown LLMs which are useful for reversing things that are legacy as heck and abandonware.
Also, thanks for mentioning! I wasn't aware of this
At least nothing tipped me off for that specific text. What did you see?
I'm really hoping these new tools will empower a new generation of people. It's sad that there even needs to be a term 'citizen scientist'.
And at least for connected devices at home, a dedicated app can have lower friction for initial setup for the "I'm not a computer person" crowd than other alternatives do.
(I know, I know. It's terrible. It even feels something like betrayal sometimes. But that's how it be, anyway -- and you and I are powerless to do anything about it.)
Strong doubt. What's lower friction, "visit this address in your browser and login to start configuring" vs. "go download this app, open it, possibly log in and register an account, add 'your' device, and only then start to configure it"?
Let's also not forget the possible chicken-and-egg situation of needing the Internet to download an app to setup your new router to access the Internet...
Point your phone at the QR sticker on the router, click open, boom you’re on the config page!
That’s a faster experience, doesn’t require any searching, doesn’t require wondering if you downloaded the right app, doesn’t require you sign up, etc.
Your claim people prefer apps to QR codes is highly doubtful.
I claimed what?
Ie, what normal people use regularly every day.
On the other hand: A thing that requires a web browser for setup does not necessarily allow strictly-local configuration; it often gets shaped that way, but it does not have to be that way.
There's no rule or law that says that these things have to be one way or another. It's a moot distinction.
> Hard requiring app setup for a router is a play to sell usage and location data,
Speaking of moot points: It's a router. And by "router," I mean: It's a whole-ass black-box computer with some Ethernet ports, a collection of radios, and an Internet connection. If/when companies decide to be in the business of selling usage and location data, they don't need an app to do that. They can just package it up and send it forth. (Location? From wifi? Yeah, that's been a solved problem for a long time now. It was first demonstrated to me in 2008 with the OG iPod Touch, which lacked both GPS and Bluetooth, but did an amazingly-good job of delivering the beholder's location using a combination of observed wifi signals and a central database.)
---
Moving on:
I guess we can talk about things like web browsers, IP addresses, QR codes, and SSIDs, and setting up routers using our pocket supercomputers.
Old way: Fire up router, manually connect to its SSID (it used to be wide-open; these days, there's usually a password printed on a label instead), set it up with a browser, and then at the right points manually connect to the newly-configured SSID instead, and [optionally] manually go to the new address (if chosen) to continue configuration (if necessary). Manually remove the old factory SSID for cleanliness. (I cut my teeth on this method and I like it just fine, but I'm one of those computer people.)
QR+browser way: Fire up router. Connect to its SSID with a QR code. Connect to its web interface by scanning another QR code. Configure the thing. Connect to the new SSID manually (or perhaps invent a workflow to scan and use a QR code using only 1 pocket supercomputer). Optionally continue configuration by remembering the name/IP of the device, or maybe printing a QR code or something. Manually remove the old factory SSID for cleanliness. (Login to third-party server at some stage? Yeah, maybe. See above.)
App way: Fire up router. Download app using familiar processes (perhaps including a QR code). App temporarily connects to router's default SSID. User uses app to configure router. At the right times, the app automatically disconnects from the old SSID, adds the new SSID to the network list, and reconnects using the new address (if selected). Optionally, continue configuring the device using the app. (Login to third party server at some point? Yeah, maybe. Again, see above.)
A Cisco 2501 is a router.
But words can mean more than one thing. Both in the common vernacular and in the context of these Motorola-branded devices: A router is a thing that routes, and also includes radios, and SSIDs, and switching.
What is this FUD?
For whatever it's worth, I associate the term FUD with crypto bros. Both of you simply stated an assertion at fact and then flipped out when someone deigned to defy that. Maybe argue your points properly?
That's two things they ruined.
While we're at it, I think them claiming the term Web 3.0 is very self-aggrandizing.
Yup. But as a broad signal, is the person getting uppity about FUD usually making a valid point or safe to ignore?
For a router? This is the device that you will often not have internet access with which to download an app until after it's configured. Many people have wired internet specifically because they live somewhere with poor cellular reception. Meanwhile the device can give out DHCP and use the standard captive portal mechanisms to automatically direct any client device to its configuration page.
I didn't say that I thought it was right, or fair, or just. I didn't say I liked it, or that I agree with it.
In fact, I think it's a pretty ugly state of affairs when a person in an area of poor connectivity needs to climb the hill/go into town/otherwise make plans before they can get their shiny new router to work.
I can accept that things are the way they are, or I can pretend that they're different.
Acceptance seems to be a lot more honest.
The implication that there is nothing anyone can do to improve the existing state of affairs is also incorrect.
I did not.
> That claim is in error.
My motivation to further discuss a hallucination is insignificant.
This is the exact quote:
> And at least for connected devices at home, a dedicated app can have lower friction for initial setup for the "I'm not a computer person" crowd than other alternatives do.
What good does it do you to dispute that you implied it as a justification for the status quo when your error is contained in the part you're not disputing?
> implied
Any implied meanings are your own creations, not mine.
I assure you that if I had meant something different than what I wrote, then I would have written something different instead.
I'm not shy.
Be well.
Unfortunately the only tech stack that can do this is the web, (serial/remote shell comes close).
In fact I regard this as the major failure of the app method of program deliverance. Why do you need to install them at all? It should be like the web, hit an address load the app. It is why I am thankful that the web was not developed as a commercial project. No for-profit entity would have let it escape their control like that. It would have been designed exactly like the app system for phones is. enforced central blessed "app-stores" and manual install processes.
If the default was something else I suspect people would accept that too, especially if it was lower friction.
I'd say typing a few characters into an address bar (or scanning a QR code) is, at the least, not higher friction than downloading an app and creating an account.