Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Don Y <blockedofcourse@foo.invalid>
Newsgroups: sci.electronics.design
Subject: Re: Win11 explorer bug?
Date: Thu, 12 Dec 2024 10:34:44 -0700
Organization: A noiseless patient Spider
Lines: 38
Message-ID: <vjf6rs$2rvlf$1@dont-email.me>
References: <qieclj5ca2dsc2fnpufpg51fn7qt0u2peh@4ax.com>
 <vj6im4$cf7f$1@dont-email.me> <dcselj96kvngr6gid7mje3phabj2sp876t@4ax.com>
 <vj91de$t4hr$2@dont-email.me> <jcoglj5c0cmprqek68tah1euht1amhu9ko@4ax.com>
 <vj9q8g$11i0t$2@dont-email.me> <13vgljdqp79a2onuijph2om08fk99u2fdm@4ax.com>
 <vjablv$14se5$1@dont-email.me> <addhljp8i0d5t42lavnd37a8e883ijhsqt@4ax.com>
 <vjaeii$14se5$2@dont-email.me> <gquhljd83745shtckfjgtd5u6iphkprprc@4ax.com>
 <vjblle$1fd6a$1@dont-email.me> <gsnjljdvnhu7m25ops26ek9lvca5eqvk2n@4ax.com>
 <vjec62$22pn8$1@dont-email.me> <vjefoe$23fh4$1@dont-email.me>
 <uj2r2lxum3.ln2@Telcontar.valinor> <vjennd$24vi6$1@dont-email.me>
 <vjeu9v$1k7v$1@nnrp.usenet.blueworldhosting.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 12 Dec 2024 18:34:53 +0100 (CET)
Injection-Info: dont-email.me; posting-host="ee6d8dc472cd575fee80a2b357a49690";
	logging-data="3014319"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19muTZPqRHD1/FMYj6XzVE8"
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:102.0) Gecko/20100101
 Thunderbird/102.2.2
Cancel-Lock: sha1:dq6dsnFpcKLang9MYe0Joi7kIN8=
Content-Language: en-US
In-Reply-To: <vjeu9v$1k7v$1@nnrp.usenet.blueworldhosting.com>
Bytes: 3387

On 12/12/2024 8:08 AM, Edward Rawde wrote:
> "Don Y" <blockedofcourse@foo.invalid> wrote in message news:vjennd$24vi6$1@dont-email.me...
>> On 12/12/2024 5:47 AM, Carlos E.R. wrote:
>>> On 2024-12-12 12:00, Don Y wrote:
>>>> Yeah, I'm REALLY eager to turn on the factory's WiFi interface
>>>> for the stove/oven... NOT!
>>>
>>> There are devices that put the actual interface on the phone, via WiFi. The physical interface has a reduced set of features.
>>
>> Yes.  Via a server located at the manufacturer's facility!
>>
>> So, you have the application layer in the appliance, the network stack in the
>> appliance, all of the network infrastructure from your AP to the manufacturer's
>> server, then, back through the phone network, up through the stack in your
>> phone and, finally, through the app to the display.
> 
> I hate this too.
> I'm resistant to cameras which bounce off the manufacturer's server, which could be anywhere.

Also meaning subject to the laws of different countries (based on its
siting).

Is there any reason the camera can't talk to a phone that is also
hosted by the customer's access point?

If you want to let the camera access a phone that is NOT "local",
then let the user subscribe to a DynDNS service -- provided by
any number of competing firms (even the manufacturer -- via a nice
clean OPEN interface).

E.g., that data, passing through the server, is no longer under
YOUR control.  And, can be monetized without your compensation.

This is possible with ANY device that passes through an unnecessary
server.  (Your smart thermostat knows when you are home, when
you are "active", etc.)