@mihael I have this problem as well, and it's because the X11 server doesn't really know what the keyboard height is. The responsive patch for Whatsapp Web/Signal/etc is basically shrinking the window size inside the X server to the standard keyboard height when the keyboard is out. But it would need a configurable option to change that value in the app itself, I think. Unless there is some magic (and preferably confined) way to yoink the keyboard height from the keyboard?

Personally, I think the keyboard height in UT is way too low. But, an adjustable height keyboard Should Just Work once Mir 2.x comes out... right?

Indra 1.2.1 is now available with a laundry list of improvements and fixes. Find it at https://next.open-store.io/app/indra.projectmoon/ or https://git.agnos.is/projectmoon/indra/releases/tag/v1.2.1.

• Feature: Make links clickable in messages.
• Feature: Add the ability to search and filter nodes on the map.
• Feature: De-duplicate messages that are likely rebroadcasts.
• Feature: Show hops away/signal strength on messages.
• Feature: Add/remove favorite nodes.
• Improvement: New message footer layout.
• Improvement: Better node list appearance in dark mode.
• Improvement: Tweaks to the choice of black or white text for messages in dark mode. More readable.
• Improvement: Add node ID to the node info page.
• Improvement: Show node distance on the map, and sort by distance.
• Improvement: New map icon.
• Improvement: Pull to refresh the node list.
• Improvement: Proper status indicators for sending messages.
• Improvement: Show channel/conversation status indicators on main view.
• Improvement: Add a setting to toggle forced Bluetooth reset.
• Improvement: Add a setting to control how long it takes before a node is considered offline.
• Improvement: Add a setting to control the message de-duplication window.
• Improvement: Translation updates.
• Fix: Apply the default channel name to the public channel no matter its index.
• Fix: Fix a UI lockup when reconnecting to the radio.
• Fix: No more UI flickering when disconnecting from the radio.
• Fix: More efficient refreshing of the node list.

@pparent out of curiosity, have you considered attempting to bundle the Qt6 web engine statically? Similar to whatever is going on with Morph Qt6 version.

@mihael so is mine.

@pparent said in Whatslectron: Whatsapp Web with Electron.:

@projectmoon

This is kind of strange that the icon is named Signal, I don't have the same thing.

Maybe localization oversight?

Seems like it works. But for some reason, the icon is named Signal (this is a problem with Min Browser too).

@Averiz very nice to see alternative keyboards. Is there a way to adjust the height of the keyboard?

@pparent said in French ID app interoperability.:

@domubpkm

Well I'm not sure but given what I have published above, It could mean that it can only work by design on an un-compromised google certified devices ( I've read that there exists so-called technologies as "Android hardware-backed keystore" and "Trusted Execution Environment" , could the app possibly rely on that? ). So maybe it's not working with microG because they don't want it to, because they want the app to run only on a so-called "safe envieronement" provided by google.

This kind of stuff is happening more and more. Even apps like the ChatGPT app for Android require "Play Integrity." It's an API that needs to be made illegal, and a lot of national apps are relying on it too. For example, the Icelandic app Auðkenni used to work without it, but now your device has to be "secure" in order to use the app. Thankfully, in that case, there is an alternative method of authentication using SIM Toolkit.

MicroG is able to execute SafetyNet/Play Integrity, but the device has to have the bootloader locked and a bunch of other stuff. And depending on level of attestation required by the app, it may or may not actually run.

@mango Have you tried installing the Snap versions?

@gpatel-fr Another question would be: is there a way to do it without hacking the database table? Like, is there something in the DB that allows it to select a browser without excluding apps from the list by doing a fake domain?

@gpatel-fr said in standard browser:

@kugiigi said in standard browser:

At the moment, it's a bit random which browser will open in every boot of the device

Is not it ruled by the order of rows in the configfiles table of urls-1.db ? It's not changing by itself.

For fun, I tried to hack the urls table with instruction like:

 update urls set domainsuffix='nothing.org' where sourcefile != 27 and protocol='https' and length(domainsuffix)==0;

where 27 is the rowid of the morph browser qt6 for my phone. It worked, I could start the new fangled browser from a link. Restarting the phone did not revert to standard Morph for links. At the moment I don't know if it has bad consequences but I'd say that extending UT to allow for a browser choice can't be impossible.

Sadly you are right for browsers not prepared for that, Min did not start when I used its rowid instead of the Morph Qt6 one. Firefox and Chromium do not even expose http and https handlers. Maybe it could be hacked around but given that Min does not even start I could not be bothered to try.

How did you determine that the row id is 27 for Morph QT6? I want to do this so I can actually open links in the modernized browser.

Edit: is it the row in the configfiles table?

Edit 2: Yep. Got it!

Maybe this should be turned into an app.

@PhAndersson I think any spawning of external processes that are not inside the app's ~/.local/share directory require unconfined. And in this case, unconfined would be required since it's using some system executable.

@Voorstad just so you know, if you have not seen it already, Indra is on the OpenStore. And no, it does not do MeshCore, at least not yet. I have a vague plan of adding at some point this year. I found a Rust MeshCore library.

https://next.open-store.io/app/indra.projectmoon/

Indra is now available on the OpenStore, with all the fixes in Alpha 4 and a few more tweaks! From this point forward, the database will be treated as something that needs to be migrated instead of wiped on every update. (The setting in the menu to wipe the database does not actually do anything, and will be removed).

Alpha 4!

https://git.agnos.is/projectmoon/indra/releases

Next alpha release that focuses on finalization of MVP functionality ahead of OpenStore release. This release also contains the changes in the unreleased alpha 3.

A database wipe is required for this release!

Delete the database by doing rm ~/.local/share/indra.projectmoon/indra.db on your phone, or by deleting indra.db using the file manager.

Changelog

• Support connecting to radios via network/wi-fi.
• Ensure contact info is on radio when sending direct messages.
• Fix channels not showing up if they don't have a name.
• Node list is now one large list off online + offline.
• Actually reliable message queueing system.
• Adhere to firmware-imposed text message rate limits.
• Security indicators on channel/DM list.
• Sortable node list.
• Move more Meshtastic-specific stuff out of app domain.
• Show and enforce character limits on sending text messages.

I think I have finally figured out why some nodes cannot be DMed. The fix for this will likely not be in the initial OpenStore release (undergoing review right now), but it will be part of the first update after.

@Ernst-Jan15 For Android stuff, you can use Waydroid.

@enki so would you say that it was the screen not getting enough power from the hub?

Alpha 2!

https://git.agnos.is/projectmoon/indra/releases/tag/v0.0.2

Next alpha release, focused on dealing with reported bugs and adding features required for MVP user experience. No work was done on Bluetooth connection stability in this release.

A database wipe is required for this release!

Delete the database by doing rm ~/.local/share/indra.projectmoon/indra.db on your phone, or by deleting indra.db using the file manager.

Changelog

• Store and utilize last heard from nodes.
• Update Direct Conversation (Direct Messages in the main list) when a node's long or short name changes.
• Allow deletion of errored or unsent messages.
• Allow resend of errored or unsent messages.
• Color messages gray if they've been unsent for a long time (only on channel view load).
• Alter message sending logic to first queue the message for sending, then send it, then delete the queued message. Theoretically helps with Bluetooth instability.
• Add ability to search the node list.
• Separate nodes into online and offline (not heard for at least 24 hours).
• Catch errors relating to specific messages and mark the message as errored.
• Render non-public encrypted channels as "group chats."

The major problems currently found that need to be fixed for alpha 2:

• PKI errors when trying to send direct messages trying some nodes but not others. Don't know what causes this.
• Node names (and probably other info) not updating correctly when that information changes.
• Handling of unsent messages is very poor. Cannot delete or resend. Cannot tell difference between an unsent vs unacknowledged message.