Offline
Have you seen the secret-tool package? It's similar to using GNOME keyring.
Though it is to be noted that a porblem we have currently with App-armour profiles, is that it won't let you communicate with the keyring in DBus via the api libsecret. It is a problem for browsers like "Chromium for UT" or "Min Browser" that get non-functional password manager because of that.
Ok so another confined app does not have permission to access your messages and data, via this Unix socket?
I have a question, given that 3 have 3 separate parts to your app ( goland, python and QML), did you ensure the security of communication between them? How is it enforced that no other app, or process will be able to access the Whatsapp private data?
For example you say that the goland module exposes a JSON RPC endpoint, but are there security measures to make sure that this endpoint can be accesed only by your app, and no other app or process?
Thank's a lot for your work! 
i knew soon as they bought it it would go to crap
Microsoft did not buy git, they bought github which is not the same thing at all. Github is just one of the many existing "web interface" for git. By the way the Ubports fondation is in partnership with "Gitlab" which is the direct competitor of "Github".
Concerning uplaoding images, if you have a computer, you can connect your phone in USB, copy the screenshots from your phone, and upload them here from your computer browser. It should work.
so like in the grand scheme of things i missed the launch boat of github ....then when i did learn about it i found it confusing ..
Just for the record, git existed way before github (It's a software from Linus Torvalds ). You can use git without using any online service. If you don't like github, which is understandable, there are a myriad of others suppliers that allow you to publish a git repo online, or you can even self-host one (for example by hosting your own gitlab instance).
It's just that it allows way better collaboration, and to follow the evolution of the software and the source code (versioning). With google drive we have no way to understand when a source file has been changed, what had been changed, why has it been changed, and in what realese of the software. There is no easy way for someone to propose you a modification of the code.
So I really think it might be worth that you give it another try, if you want to work on open-source projets, because it will allow for a better collaboration with others, and get more feedback!
Ps: personally I'm not a gamer at all! I will see if I can test the application a bit later, but I won't be able to give you a gamer feedback.
Just one question: Any reason you don't host this project on a git platform, like "Github" or "Gitlab" or "Bitbucket" ? Maybe having to go to google drive links may look a bit weird for some people.
Maybe it could help also to publish more screenshots, or even better a video of your application running on Ubuntu Touch.
Also I'm sure you will get feedback when you publish the app on the openstore, but it might not be ready yet?
Thank you!
It's not that there is only "system", it is that the combobox, ( or "<select>" in html ) does not work. i.e the element that allows you to chose, does not display well, but it is sadly the case in most XWayland apps, in UT and I can't do much about it right now.
What do you mean "change the appearence"? It simply means that you can display and navigate properly in the menu in vertical mode, as shown in the screenshot.
The combobox still do not work, it is a problem with XWayland and Lomiri.
I've published version 0.8.3-2 with the following improvements.
Note: no Signal-Desktop version bump for this revision, because building broke with my current scripts for 8.4.0 and 8.5.0, I'll have to look into it later.
Don't hesitate to tell me if everything works well for you.
@pparent Where was this announced?
Well "annonced" maybe was not the correct term, but it was at least mentioned as a possibility here:
Just out of curiosity, in the end is the fairphone 6 supported by mainline linux kernel as annonced?
The idea is that it's a generic feature, not something specific to Ubuntu Touch.
Well yes and no. It is a generic feature to detect option 114 and make the request to the API. BUT It is an OS sepcific feature to decide how you are going to display the captive portal. Here I display it using urlDispatcher via DBus that is an UT-specific feature that could hardly be upstreamed. Android has it's own mini-browser designed exclusively to display captive portal.
So this is kind of hard to have a generic way to handle captive portals in all OS that embed NetworkManager, independenty of the OS specifics. And all the existing OS (Android, iOS, Windows, MacOS) handle captive portal each, their own way.
I don't think in that regard UT should limit itself to what is availiable upstream, i.e keep basic things not working and not implemented, while it requires a 20 line script to have things running fine. If some day NetworkManager improve it's implementation, it will allways be time to use it then.
Yes but, that being said on desktop this feature is not as important as on mobile. Even in windows the portal does not open automatically, and it's handled browser-side. So on desktop it seems more "OK" not to have this feature system-side.
On Ubuntu Touch given that Morph does not handle at all captive portal internally, it seems to me very important to be able to open it automatically. I've seen several users complaining of not being able to use networks with captive portals, and even cited as one of the reasons they can't use it as a daily driver. (Example here: https://www.youtube.com/watch?v=HjfwyMuLnPo&t=475s )
I will look at the pull request you mentioned, thanks! Ps: Ha but it was not a merge request it was just an issue wasn't it?
Nice! Your app could be very useful especially to receive notifications in background with lower battery costs.
Hope the whatsmeow library can remain reliable in the long run!
Maybe you would like to post some screenshots of your app?
Very nice!
How do you interact with Whatsapp protocol? Did you reverse ingeneer it yourself? Do you use an existing library?
Ps: we could add in the same script the "legacy" hotspot detection (on top of the RFC8010 detection) based on make a dummy http request on a dummy URL, and it could allow have a large compatibility to detect most hotspot portals on the market.
So I've found a way to have hotspot detection working with rfc8910.
Here is the behaviour when I connect to a Hotspot Wifi compatible with rfc8910: https://www.youtube.com/shorts/0et6I-lwwwQ
To have it working you need to add to the filesystem the following script:
/etc/NetworkManager/dispatcher.d/99-rfc8910
#!/bin/bash
# NetworkManager dispatcher script for handling DHCP Option 114 (RFC8910)
# Opens the captive portal with URLDispatcher if the network indicates a captive portal
logger "Option 114 init $1 $2"
IFACE="$1"
STATUS="$2"
# Only proceed if the interface is up or dhcp4-change
if [ "$STATUS" != "dhcp4-change" ]; then
exit 0
fi
# --- Retrieve the Option 114 value using dhclient test request ---
dhclient -1 -v -lf /var/lib/NetworkManager/dhclient-rfc8910-wlan0.lease wlan0
LEASE_FILE="/var/lib/NetworkManager/dhclient-rfc8910-wlan0.lease"
CAPTIVE_API=$(grep 'option default-url' "$LEASE_FILE" | tail -n1 | awk -F'"' '{print $2}')
# Remove escaped ampersands (\&) from the URL
CAPTIVE_API=$(echo "$CAPTIVE_API" | sed 's/\\//g')
if [ -z "$CAPTIVE_API" ]; then
logger "No DHCP Option 114 found for interface $IFACE"
exit 0
fi
logger "DHCP Option 114 detected for $IFACE: $CAPTIVE_API"
# --- Query the captive portal API using wget ---
API_RESPONSE=$(wget -qO- "$CAPTIVE_API")
if [ -z "$API_RESPONSE" ]; then
logger "Failed to reach captive portal API: $CAPTIVE_API"
exit 0
fi
# --- Parse JSON for 'captive' and 'user-portal-url' ---
# Extract the 'captive' status (true/false)
CAPTIVE=$(echo "$API_RESPONSE" | grep -oP '"captive"\s*:\s*\K(true|false)')
# Extract the 'user-portal-url' and remove all backslashes
PORTAL_URL=$(echo "$API_RESPONSE" | grep -oP '"user-portal-url"\s*:\s*"\K[^"]+' | sed 's/\\//g')
logger "Captive portal API response: captive=$CAPTIVE, portal_url=$PORTAL_URL"
# --- If the network is captive, open the portal URL via D-Bus ---
if [ "$CAPTIVE" = "true" ] && [ -n "$PORTAL_URL" ]; then
USER_NAME=phablet
sudo -u "$USER_NAME" \
DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/32011/bus" \
gdbus call \
--session \
--dest com.lomiri.URLDispatcher \
--object-path /com/lomiri/URLDispatcher \
--method com.lomiri.URLDispatcher.DispatchURL \
"$PORTAL_URL" ""
logger "Captive portal opened: $PORTAL_URL"
fi
Don't forget to chmod +x /etc/NetworkManager/dispatcher.d/99-rfc8910 and reboot
Tested on 24.04-1.x daily on OnePlus Nord N10
Unfortunatly the script is slightly hacky because it requires to make an external dhclient request. I've not found any other way around as the internal Network Manager dhcp client does not support option 114 in any way. We'll see if it can integrated to the system despite this, and if it can be slightly improved.
On what canal should I discuss with system devs about that?
I'm wondering about something, as this problem is an IP loss problem, I think it should be noted that by defualt NetworkManager uses it's internal dhcp handler. But it is also possible to configure it to use dhclient. And I wonder if the later would not be more reliable.
So I think I will test to change the configuration of my NetworkManager to use dhclient, and see if it has any impact on this bug.
Although, to be fair the creator of the WhatsNew app has taken measure to suspend the app when it looses focus as well
I've not done that specifically in whatsnew. What happens is that normally when an electron app is not anymore in foreground it goes into a "throttling" mode meant to keep operating the website but with lower resources. This is a feature from chromium.
That being said I have no idea why XWayland/electron apps don't get suspended by default. For Signal UT or Whatsnew it is handy to get background notifications though.
The behaviour encountered by @smobilesoft (high CPU usage) is not normal , I've not been able to observe it myself, and it seems since he reinstalled the app it has gone. So this is a bit strange.