View Single Post
  #97   Report Post  
Posted to rec.photo.digital,alt.home.repair,comp.mobile.ipad
Tomos Davies Tomos Davies is offline
external usenet poster
 
Posts: 48
Default Is there a single useful Apple iOS camera capability that isn't already on Android?

In , nospam suggested:

actual respectable person, such as jeff lieberman, agreed with what i
said and even called you an idiot for your crazy plan.


You completely misunderstood the question (proved in the prior post) and
now you completely misrepresent what Jeff (and others) said.

What you forget (which was in the original post) is that it was a technical
question asking about why something so simple works so well - so it was
always known from the start that there could be technical issues (to flesh
out being the entire point of the thread).
https://u.cubeupload.com/wboAp1.gif

Dan Purgert responds to the setup explained in the original post:
totally agree this works.

Nospam insists the problem wasn't stated in the original post:
he has not stated the problem he needs to solve and has demonstrated
that he knows very little about networking.

Carlos E.R. corrected nospam:
Yes, he did say it. And it is a legitimate reason.

Nospam finally replied:
eventually, he did, and the reason is valid.

Nospam proves he doesn't understand how Android works:
On Android, the IP address on the phone is set "per access point"!


no it isn't.

Carlos E.R. responds:
Yes it is.
Look it up on your phone.

Jeff Liebermann agreed that it will work, and explained why:
In theory, if one sets a static IP address for some (mobile)
device on a network managed by a router, the router will be able
to detect the presence of that device, it's MAC address, and what
IP address it is using by one of the aforementioned methods.
It will then not assign in use addresses via DHCP.

Jeff Liebermann even explained why nospam's solution could be bad:
Of course, there's a security problem with sequentially assigning
IP addresses via DHCP.

Nospam continues to misunderstand the problem set:
yes, because whatever ip address he picks, it will almost certainly
conflict with something on another network.

Carlos E.R. corrects him time and time again:
The fixed IP setting applies only to a single SSID.
Does not affect other networks.
When he goes out, the phone will connect to a different SSID
and use the configuration for that different SSID, which is "auto",
ie, "DHCP".

Nospam insists:
it's a horrible idea because he'd have to change it every time he
leaves the house and back again when he returns.


Dan Purgert correctly responds:
Bear in mind that for android devices, you can set the IP address
settings on a per-SSID basis. Therefore, unless he connects to a
network with the same SSID, but a different addressing scheme, the
approach will cause him no grief.

Carlos E.R. says (correctly):
Notice that the way it is set currently it is static on his home only,
dynamic elsewhere.

To which nospam replies (incorrectly):
which means changing it every time he leaves/returns.

And to which Whiskers corrects nospam:
Why? He only needs to set the static IP for his home network, not for
any others. Once set, each network will be recognised automatically by
his phone and use the settings created specifically for it

Nospam says (incorrectly):
which means changing it every time he leaves/returns.

Carlos E.R. responds (correctly):
He doesn't have to change anything.
Just move and continue using the phone normally.

Nospam continues to say (incorrectly):
except when it doesn't.

Carlos E.R. (exaperated) simply replies:
Your wrong opinion noted.