version of the URL.
Caused by java.net.MalformedURLException: Not a meshtastic URL
at com.geeksville.mesh.model.Channel$Companion.urlToSettings(Channel.java:43)
at com.geeksville.mesh.model.Channel$Companion.access$urlToSettings(Channel.java:19)
at com.geeksville.mesh.model.Channel.<init>(Channel.java:50)
at com.geeksville.mesh.MainActivity.perhapsChangeChannel(MainActivity.java:631)
at com.geeksville.mesh.MainActivity.handleIntent(MainActivity.java:467)
at com.geeksville.mesh.MainActivity.onNewIntent(MainActivity.java:447)
at android.app.Activity.performNewIntent(Activity.java:7971)
at android.app.Instrumentation.callActivityOnNewIntent(Instrumentation.java:1407)
at android.app.Instrumentation.callActivityOnNewIntent(Instrumentation.java:1420)
at android.app.ActivityThread.deliverNewIntents(ActivityThread.java:3838)
at android.app.ActivityThread.handleNewIntent(ActivityThread.java:3850)
at android.app.servertransaction.NewIntentItem.execute(NewIntentItem.java:53)
at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2261)
at android.os.Handler.dispatchMessage(Handler.java:107)
at android.os.Looper.loop(Looper.java:237)
at android.app.ActivityThread.main(ActivityThread.java:8107)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:496)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1100)
Put the channel options into the URL fragment instead of the URL path.
This ensures that the channel options (including the channel key) is
never accidentally leaked to a remote party. This URL format appears to
be backwards compatible, URLs generated in the new form are properly
parsed by the old version. URLs generated by the old version are _not_
parsed by the new version.
Closes#126.
// FIXME - possible kotlin bug in 1.3.72 - it seems that if we start with the (globally shared) emptyList,
// then adding items are affecting that shared list rather than a copy. This was causing aliasing of
// recentDataPackets with messages.value in the GUI. So if the current list is empty we are careful to make a new list
