Mobile #Diaspora client for Android and iOS needs testers
Jonne Haß has created a mobile client quite more comfortable than Dandelion. It was on f-droid, now he has also put it on the Play Store. Right now he needs testers to get the app approved, so if you'd like to have a really well functioning mobile client, drop him a PM, because he may need to put your email manually into the tester list.
Written on Insporation, the client I wrote about.
like this
N. E. Felibata 👽 reshared this.
HernanLG
•Benjamin likes this.
Monkeymind
•Jonne Haß
•GitHub - jhass/insporation: Flutter based client for diaspora*
GitHublike this
eeepee, Aladár Mézga, Monkeymind and Benedikt Bauer like this.
Bonobo
•insporation* App - App Store
App StoreAladár Mézga likes this.
Benjamin
•Monkeymind
•Got it.
Do you take feature requests? 😃
GitHub - jhass/insporation: Flutter based client for diaspora*
GitHubBenedikt Bauer likes this.
Jonne Haß
•@Monkeymind What's on your mind? 😁
@Benjamin not sure I'll really care with that anymore, the app's released on the appstore in its latest version.
like this
Benjamin and Aladár Mézga like this.
Aladár Mézga
•I'm not monkeymind, but... The text input is a bit weird. The window doesn't tell the keyboard when a new sentence starts, so it's always lowercase. Modifying text is a bit tricky, because instead of just placing the cursor somewhere, a lot of text gets selected and it's not easy to deselect everything. Context (after selection) could use a "translate" like Dandelion had. 🫣
like this
eeepee, Benedikt Bauer, Benjamin and HernanLG like this.
🧊 freezr 🥶
•Monkeymind likes this.
eeepee
•As @Aladár Mézga said, text selection behaves on my phone also sometimes strange. From time to time it isn't possible to get a "standard" cursor for text input without any selections.
But I'm not sure, if this is a more Android specific problem or if the app is causing the problem.
like this
Benedikt Bauer, Benjamin and HernanLG like this.
Jonne Haß
•Monkeymind
•First of all, I love the app!
These feature requests are just that, and don't detract from my appreciation. I know some of these are hard and haven't been implemented in the web client either.
like this
Benjamin, Benedikt Bauer and HernanLG like this.
Benjamin
•Love this idea
Monkeymind likes this.
Aladár Mézga
•Yeah, that one sounds good. But...
I think that would be a Diaspora feature and it should be implemented there. Sounds like a Frequently Requested Feature...
Benedikt Bauer likes this.
Wolfgang Strobl
•Monkeymind
•@Aladár Mézga:
It's been requested for ages. The common thread in answers has been "use a greasemonkey/user script in yourbrowswr", which makes me believe it is a client-side implementation topic.
But I seriously don't know. Just formulating a wishlist here.
Aladár Mézga likes this.
Aladár Mézga
•Benjamin likes this.
Jonne Haß
•Yap, blocking logic I would prefer server side. The client currently only stores sessions and that's easily recoverable if lost. The other thing it stores are post/comment drafts, something that can be argued as best effort and not too bad to be lost. So essentially it's fairly stateless so far. So I see introducing things like client side filtering as lot of potential complexity growth, as you then probably will also want a migration/backup path, multi-device syncing of the client configuration etc.
The API currently does not return anything about the post/comment on the notifications endpoint, so previewing that would mean N+1 queries over the network, not sure it's worth the feature to be honest.
Mention autocomplete is difficult since especially for commenting, between the comment input being in a bottom sheet at the moment and the on-screen keyboard there's no real space to display anything. Not sure how you imagine this exactly. -> https://github.com/jha
... show moreYap, blocking logic I would prefer server side. The client currently only stores sessions and that's easily recoverable if lost. The other thing it stores are post/comment drafts, something that can be argued as best effort and not too bad to be lost. So essentially it's fairly stateless so far. So I see introducing things like client side filtering as lot of potential complexity growth, as you then probably will also want a migration/backup path, multi-device syncing of the client configuration etc.
The API currently does not return anything about the post/comment on the notifications endpoint, so previewing that would mean N+1 queries over the network, not sure it's worth the feature to be honest.
Mention autocomplete is difficult since especially for commenting, between the comment input being in a bottom sheet at the moment and the on-screen keyboard there's no real space to display anything. Not sure how you imagine this exactly. -> https://github.com/jhass/insporation/issues/109
Will include a first version of message preview in the next release, not very happy about the UI in the end, glad for any suggestions how to improve it.
Will include comment reply in the next release, looks good.
Better mention integration
jhass (GitHub)like this
Benjamin, eeepee and Monkeymind like this.
Aladár Mézga
•Ah, btw: Dandelion had a link in shared posts to the original post. Would that be difficult to add?
And a question: I think once upon a time I could mention people (meaning with link created and notification sent) from Dandelion, but that's only possible in the web version now, not mobile. Do you perhaps know the reason for that?
Benedikt Bauer likes this.
Benjamin
•