@abranson I don’t know what kind of hackery is needed, but it would be amazing for new comer and Jolla store perspective if those posts could be opened in Tooter that is installed from Harbour. Surely quite a few will get also additional stores, even for Pure maps, but still I would love to see way to Jolla store host these stunning apps with these functionalities 
It depends on the url that the account plugin produces. Tooter handles urls like
https://mastodon.social/@danstowell/117155658857098580
But should also handle: /users/username/statuses/123456789
redirect to the conversation tab and of the form
https://mastodon.social/@danstowell
to redirect to the user search but should also handle: /users/username
I have not been able to get the event view account plugin to work since first installing it, so I’m not sure what it’s producing as links.
1 Like
What would be good is a download/save indication. Now there’s no status of a picture/photo/video being downloaded or when the save/download is ready.
1 Like
Good point! The having faith and waiting bit a somewhat old fashioned 
Add progress feedback on downloads. · Issue #90 · poetaster/harbour-tooter · GitHub
1 Like
While I do enjoy the sound of the old and faithful 56kbps modem as a nostalgic trip, my faith in tech has since diminished, and I’ve grown tired of waiting. 
1 Like
Sorry I’m not sure if this is a bug or a feature… tapping multiple times on the “root” toot in a Conversation opens a new Conversation page with the same toot, rather than either ignoring the second tap or staying in the same page.
e.g. I see a toot on my Home feed. Tap on it. A Conversation page with that toot loads. I tap again on the same toot, a new Conversation page loads. You can repeat this process multiple times. Swiping back takes you to the previous page, not to home. So if you tapped on it 10 times on the same toot, you swipe through 10 Conversation pages.
So what I would expect is that once in a Conversation, tapping on the “root” toot again does nothing (or tapping is somehow disabled, so it cannot be tapped again by accident).
It mostly happens to me by accident, scrolling or wanting to long-press.
2 Likes
I think you can already include URL handling and such in harbour apps? There was something in a community newsletter about it a while ago…
1 Like
That one is already on the todo list (Same toot can be opened multiple times · Issue #37 · poetaster/harbour-tooter · GitHub)
2 Likes
Hmmm, I know that including url open .desktop files is still not allowed, but perhaps it can be dealt with via the main .desktop file. Hmmmm. @abranson what kind of links are you creating for notifications (status)?
2 Likes
You can add the mime type line to the launcher desktop file. Afaik there’s no need for an extra one. All the Jolla apps got rid of their special opener files a while ago.
I generally create an authorize_interaction link when posts are tapped, so that the user can interact with the post on their own instance without having to provide that to the foreign server. But notifications are just normal post links afaik. Are you having trouble with them?
I’m still getting around to detecting installed activitypub scheme handlers and handing those links out instead when found. But it won’t be until at least 5.3, maybe later.
4 Likes
Ok, I’ll try reducing the url opening to the main desktop file and see how that goes. That should remove the need for DBUS handling as well …
As for auth, since opening tooter automatically logs you in on your instance, there is no need for authentication and I would need to parse out any parts of the url that are not directly related to tag/user/status…
1 Like
I know it’s a little off-topic, but how? Do you have an example? I just looked into some of those files but found nothing that seems to be mime type related.
Would that be an option to force android apps too to handle specific files?
(As I don’t want to spam this thread I’d also be fine with a dm reply… But perhaps it’s useful for others too.)
Here’s one:
It’s a good idea to keep the D-Bus, as that means the system can send links when the app is already open.
Android apps used to use desktop file MIME type declarations, but it’s not granular enough for some of the weird associations that those apps do, so now Lipstick queries AppSupport directly per file for handlers. It’s automatic.
3 Likes
The links are like this:
https://mastodon.example/authorize_interaction?uri=<percent-encoded-absolute-target-url>
So decoding them should be as simple as decoding that argument. The future activitypub URLs should be more direct:
ap://remote.example/@alice/123456
1 Like
So I just transfer:
MimeType=text/html;x-scheme-handler/https;
X-Maemo-Service=de.poetaster.harbour.tooterb
X-Maemo-Object-Path=/de/poetaster/harbour/tooterb
X-Maemo-Method=de.poetaster.harbour.tooterb.openUrl
EDIT: yeah, I know the method doesn’t have to be declared with a full object path, etc. War damage, 1990s, java developer.
From the openurl desktop. That way i have dbus configured appears to be broken, since I get a new instance of tooter launched when opening.
1 Like
I think your D-Bus methods don’t match what’s implemented. In here: harbour-tooter/src/dbusAdaptor.cpp at master · poetaster/harbour-tooter · GitHub you have an openapp and showtoot, not openUrl? And your registered object is just ‘/’ here harbour-tooter/src/dbus.cpp at master · poetaster/harbour-tooter · GitHub
But I think if you put:
X-Maemo-Service=de.poetaster.harbour.tooterb
X-Maemo-Object-Path=/
X-Maemo-Method=de.poetaster.harbour.tooterb.openUrl
and implement openUrl in your dbus interface then it should work from the main launcher.
But! Recently you can put X-DBusActivatable=true and implement the org.freedesktop.Application.Open interface, which is much simpler. See here: Launchers | Sailfish OS Documentation
2 Likes
Thanks! I knew that the old methods were not in sync with the naming I had chosen, but just got taken over by other developments. Will get to this asap.
2 Likes
Can this simply be done with , for instance:
DBusAdaptor {
in QML .. that would really simplify everything …
Hi, I became a SFOS user after receiving the new Jolla phone (I’m writing from there!) and I’m trying to use Tooter to access my account, so I can migrate from my old Android phone eventually.
However for some reason the login process does not reach completion and the application stays on the screen asking for the instance name.
I’m using GoToSocial, not Mastodon, but other applications (e.g. on Android) are able to access the account just fine, including the built-in SFOS account that can be set up from the system’s settings.
When I ask Tooter to connect to my instance it properly opens the web browser to the instance’s login form, but after giving permission to Tooter all I get is a white page with large text saying I can close the browser. I do that, but Tooter does not advance the log in process.
Am I doing something wrong? GoToSocial’s log in process is exactly the same as Mastodon’s, so the application shouldn’t notice anything. Is there anything I can do to diagnose this error?
Many thanks.
1 Like
It’s possible that GoToSocial uses an anti-bot like linux.social which interferes with the token based auth after login. In those cases there seems to be a ‘real browser’ dependency, which will need some work-a-rounds.