View Single Post
  #19  
Old May 3rd 17, 12:12 AM posted to rec.photo.digital,alt.home.repair,comp.mobile.ipad
nospam
external usenet poster
 
Posts: 24,165
Default Is there a single useful Apple iOS camera capability that isn't already on Android?

In article , Tomos Davies
wrote:

don't forget needing to set a static ip so that he can find the device.


The record will show that the Linux people had to tell you *multiple* times
that you were dead wrong in almost everything you said.

Do you want me to prove my statements with the cites to the thread?


the question is do *you* want to make a bigger fool of yourself than
you already have.

You know I only speak verifiable facts.


it looks like that answer to that is yes.

i also know that you continue to lie.

Nospam says (clueless):
he never said what the problem is, so nobody, including you, has any
idea.

Frank Slootweg replies (correctly)
He *has* said what the problem is.
Sofar the only one having no idea is you.


all frank does is argue.

he's the one who said that it's illegal to have an unswitched 12v power
outlet in a car.

Nospam says (incorrectly):
You don't want a fixed IP address on a phone.

Carlos replies (correctly):
Not true, he does.


carlos is wrong. you don't.

a fixed ip on a phone is very bad.

Nospam says (incorrectly):
his *guess* is that a static ip is the solution without realizing all
the problems it will cause for both himself and others.

Frank Slootweg replies:
There's no 'guessing' involved. A static IP *is* the solution.


he's wrong. there is no need for a static ip, and not only is it *not*
the solution, but it *creates* many problems.

the solution is to either use reserved dhcp or better yet, let dns
handle everything.

ftp myandroidphone (or whatever name you want). done. nothing to
configure, other than deciding what to name your phone.

Nospam says (incorrectly):
You want it in DHCP so it will work anywhere.

Carlos replies (correctly):
It will work everywhere perfectly as it is.


nope. it definitely won't everywhere. he's wrong, as are you.

the moment that phone with its fixed ip associates with a network other
than your own (i.e., *any* public hotspot) problems can (and likely
will) occur because there's no guarantee that its ip won't conflict
with one that is already in use. common sense.

Nospam says (incorrectly):
he might think he does, but he doesn't.

Carlos replies (giving up on nospam's idiocy):
Your opinion noted.


translated "i don't actually understand any of this stuff, so i'll just
call it an opinion and pretend i do."

carlos refuses to learn anything. he insists that it costs money to use
google voice. it doesn't.

This goes on for days on end, where nospam is dead wrong, doesn't
understand the question, doesn't like the solution, until the Linux people
just five up on him.


except for everyone who agreed with me, including jeff lieberman, who
can configure a network while blindfolded.

his reply (which was *very* long and detailed, as his posts often are)
went into gory detail why your idea is stupid and why reserved dhcp is
the way to go.

tl;dr reserved dhcp and/or dns. *not* static ip.