So apparently Android got Mesh network capability with Oreo but no one noticed or cared

So apparently Android got Mesh network capability with Oreo but no one noticed or cared...

developers.google.com/nearby/

Attached: mesh-mesh-scenario.gif (390x290, 37K)

Other urls found in this thread:

developers.google.com/nearby/connections/overview
play.google.com/store/apps/details?id=com.exsubstantia.phait.thought
developers.google.com/nearby/messages/overview
twitter.com/SFWRedditImages

windows 10 update also uses mesh network

Imagine Microsoft and Google flipping a switch and telling ISPs to go fuck themselves nationwide overnight

I don't even want to imagine the latencies

we can dream.

This actually looks really promising.

>n Google Play services version 11.0, the Nearby Connections API was updated with a number of significant changes, including the following new features:

Offline support. Nearby Connections now works fully offline, no network connectivity required. Devices no longer need to be connected to the same multicast-enabled wifi network to discover or connect to each other.
Encrypted connections. Connections established between devices are now fully encrypted, ensuring that only the intended partipicants can read exchanged data.
Large payload support. Nearby Connections now supports large Payload objects, which may be messages (up to 32kb), files, and even streaming data. The API also provides realtime progress updates about in-flight payloads.
Simplified, symmetric API. The API has been simplified to be easy to use and more symmetric between advertiser and discoverer devices.
Learn more about the new functionality in the updated documentation.

>Exchanging Data
After a connection is established, further API usage is symmetrical, so there’s no longer a distinction between Advertiser and Discoverer.

Both sides can now exchange data as Payload objects. There are 3 types of supported Payloads:

BYTES Byte arrays limited to 32k; these are good for sending things such as metadata or control messages.
FILE Files of any size; these are transferred from the app to the network interface with minimal copying across process boundaries.
STREAM A stream of data that is generated on the fly, as in the case of recorded audio/video, with no final size known beforehand.

developers.google.com/nearby/connections/overview

what about ad-hoc wifi? How hard can it be to implement in andoid

Great news. Now we gotta solve the latency issue

Does this stuff work?

Everything in Android uses API's. So if google wanted to they could create an API for the 802.11s (mesh wifi) protocol already included in the Linux kernel.

Theres a few apps that use it. Very few.

Heres one. play.google.com/store/apps/details?id=com.exsubstantia.phait.thought

Anything on F-Droid?

developers.google.com/nearby/messages/overview
>The Nearby Messages API is a publish-subscribe API that lets you pass small binary payloads between internet-connected Android and iOS devices. The devices don't have to be on the same network, but they do have to be connected to the Internet.

This is nothing and for sure not mesh networking. It's basically and easier way to send messages/files between nearby devices and, of course, there is some google server mediating the thing.

That's the messages API. The nearby API has 3 different sub API's

whoops, that's right, found it.

Wow cool more remote exploits for the NSA

Attached: file_0.png (298x750, 169K)

All the drivers on your phone and the base band software are already closed source. They are already in your phone.

>advertiser and discoverer
Fuckin hell their noses grew so damn big they can't turn off their schlock even in the documentation

Apples airplay/airdrop has used adhoc WiFi and Bluetooth for years.
Yawn

What the fuck are you talking about? Android Nearby has been around for at least 3 years now