Respectfully, did you read the article? They’re talking about NFC increasing the range from ~5mm to 30mm. It’s not about competing with Bluetooth use cases, it’s about an improvement in the user experience with contactless payments and door access, etc.
I believe that is correct.
Not quite the case.
When a user on instance B subscribes to a community on instance A, instance A begins to send in real-time the posts and comments of that community to B, which keeps a local copy of that community.
If instance B has 10 active users subscribed to that community on A, they’re all loading it from instance B. The end result is instance A only had to share each piece of content once with instance B, and instance B further shares it with the ten local subscribers, reducing the load on instance A.
The only exception is when instance B only has a single subscriber to instance A’s community, in which case replicating the entirely of the community is more work then that user just browsing it directly on instance A.
Tl;dr it’s most efficient for a large Lenny instance if most of its active users are on other instances.
If a large corp wants to do what you’re suggesting, they don’t need to launch a big announced project.
They can spin up a federated instance with just one user and no references to who owns it, then have patsy accounts on other instances subscribe to their instance and get all the data they want sent to their semi secret instance.
It would be very difficult to identify this in a large, healthy federation with tons of users and lots of small personal instances.
As well, EV’s lose very little of their energy to heat or other losses between the battery and wheels unlike ICE vehicles. The result is drag plays a more significant percentage of where the energy is “going”, so the impact of higher speeds on range is greater then it is for ICE vehicles.