Downside is each device will differ and has to be trained separately. See e.g. face recognition in Apple Photos.
-
-
-
Not necessarily. Devices can sync data in peer-to-peer fashion.
-
Only when they are online at the same time. Apple Photos and iMessage show the downsides of not having a central cloud component.
-
This is where having your own always on, easily addressable node comes in: https://ar.al/notes/encouraging-individual-sovereignty-and-a-healthy-commons/ …
-
That's a great idea. In the meantime I would like Apple to improve their cloud component while still protecting my data and privacy.
-
Because we currently still need companies to provide always on and available nodes.
-
Indeed. And we will in the interoperable model I propose also. But companies that solely compete on quality of service.
- 1 more reply
New conversation -
-
-
.
@aral#140tooshort Depends. Apple has shown that certain personalisation can be feasibly be done by company code on my device. However,… -
.
@aral for some services this would mean pushing excessive data onto the device for filtering. E.g. Flipboard or Amazon recommendations. … -
.
@aral and if device chooses what data to pull from the host, the host could still profile. So nothing gained. Need more than 140. ;)
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.