TAP mode is not supported

[NoDaddy]

My point of view is that your application should learn how to do IP packets, that's where it should actually be solved.

NoDaddy I am sure that many users are dont agree with you as I. It is bad approach. How you can learn the device to do it... it sound like we are living in AI world and you expect all app are intelligent. But in real world there are devices which we users are unable to change and "learn" use IP packets and users should have that choice to use bridging in that case.
You explained the difference between TAP and TUN but there is application for use TAP. What if someone just want to connect not an entire networks together but just one device for example phone or some other control panel by client to the network with server launched on router where is a device in local network which dont sends the IP packets like some IoT devices... you dont reach it in TUN mode but in TAP mode you can do it... it is not enough reason it is usable and can be an application for this.

Because this function is not supported in openVPN3 the older application are not available to dawnload on mobile by its stores so you cant manage some of IoT devices remotly.

You're quitting "OpenVPN Inc" here, not NoDaddy. It wasn't my message. I agree with your point though.

[crazifuzzy]

This is a shame, as I utilize TAP relatively often for BACnet based systems - which to much of their discovery via IP broadcasts - which obviously won't traverse a level3 tunnel. There are of course dedicated hardware devices intended to get around this by connecting together over a routed network and repeating the broadcasts as necessary - but a TAP VPN just makes things so much smoother.

Understanding that I can of course still continue to use 2.6 - my concern is if routers start shipping with 3.x only.