@hfaust Looking at Twidere's Timeline view I see: 1. Two timelines (Home and Interactions. Trends and Messages don't work in GNU Social) vs 10+ timelines in AndStatus (any may be hidden in the Manage timelines view). But these two are accessible from Action Bar, swiping between them. AndStatus has one click switch to Detail timeline (click on a Timeline title). It could be a one click switch between two timelines... Both apps have ”Drafts” hidden under the Drawer/additional selection. 2. Not clickable links in a Timeline vs clickable in AndStatus. 3. Same three Reblog/Reply/ Like buttons for each message. Plus ”overflow” button for the Context menu. In AndStatus context menu is opened on a message click. 4. Conversation view is much like in AndStatus. No explicit "threads” though. ... What else is important? What AndStatus should improve in the UI? 1. We discussed Action Bar changes e.g. here https://github.com/andstatus/andstatus/issues/364 but didn't come to any real improvement... Please add your insight! 3. Message context buttons, maybe, work not as good as expected, see https://github.com/andstatus/andstatus/issues/410 Do we need to add the ”overflow” button also? What else? In general, such changes are hard to implement not because developers cannon program them, but because telling ”do like this” is too far from what is needed to know/ to consider about how this change should / will influence existing features and their users... I.e. more analytical work and consideration is needed. Otherwise such changes will actually cause degradation, and not an improvement...
I wrote to Twitter Support and almost immediately restrictions were lifted (to be confirmed by users...) This is not the end of the story yet: we need to figure out how to avoid repetition of the restriction in the future...
@maiyannah The reason is not explained. Currently we noticed only that posting to Twitter is "Forbidden”. I will contact with Twitter support to find out the best way to fix this.
"Edit message” feature for Pump.io is in Beta testing. Messages with and without attachments can be edited. A User can change both text and an attached image. What is not supported (and will fail on an attempt to send an update): adding an attachment to a message that didn't have one. Or removing an attachment. This is because messages with and without attachments are two different types of objects in Pump.io. "Edit" context menu item appears, when a Sender is my account and it is successfully verified (i.e. the account can actually post the update). https://github.com/andstatus/andstatus/issues/221
@hannes2peer I tested now: Twitter's behavior is different and is User friendly: It allows to attach an image to a tweet, which has 140 characters of text and it shows it completely on a web site, see https://mobile.twitter.com/AndStatus1/status/778446073333374976 ...but for a mobile client it truncates the tweet ending it with ... in order to insert a Web link to the attached image. Not so bad.
So in order to be Twitter's User friendly, Quitter.se needs to change this also?!
@hannes2peer @blp @maiyannah@community.highlandarrow.com @lnxw48 I just tried sending a message with an attachment to this conversation from my quitter.se account: 1. First attempt failed with the reason: REQUEST_ENTITY_TOO_LARGE - this is a known problem of message length counting on this server: it counts a length of attachment URL with a length of a message itself... 2. I had to remove most of the conversation participants from that already short message - and upload succeeded, see the notice: https://quitter.se/notice/7191588 But here we got another problem: attachment URL, generated by the server, is broken: no file is on that URL... @hannes2peer could you check , why is this?
@hannes2peer @blp @maiyannah@community.highlandarrow.com @lnxw48 I just tried sending a message with an attachment to this conversation from my quitter.se account: 1. First attempt failed with the reason: REQUEST_ENTITY_TOO_LARGE - this is a known problem of message length counting on this server: it counts a length of attachment URL with a length of a message itself... 2. I had to remove most of the conversation participants from that already short message - and upload succeeded, see the notice: https://quitter.se/notice/7191588 But here we got another problem: attachment URL, generated by the server, is broken: no file is on that URL... @hannes2peer could you check , why is this?
@jankusanagi@identi.ca I just implemented in AndStatus HTMLifying of a content, sent to Pump.io, as as per your request https://github.com/andstatus/andstatus/issues/375 Now testing it... Actual transformation was done in literary 3 lines of code using Android system libraries. This gives an advantage of using better algorithm at each subsequent version of Android libraries. -- andstatus@identi.ca URL: https://identi.ca/andstatus/comment/hrTT3Mt4TT-y_7Rs_WwMDw
@gargron Please lookup how automatic client registration using OAuth is implemented in Pump.io. It allows a User, who has an account in one Pump.io instance, to access data (e.g. remote User's timeline) at another instance without manual steps. GNU Social is far behind here... Furthermore in the API design I would recommend to base it on ActivityStreams, now a w3c document (as pump.io, see https://identi.ca/cwebber/note/dqzGLzjRQdGw7TNutig4qw ) @lnxw48 @lambadalambda @1iceloops123
@gargron Yes, code for different APIs lives in different classes, so it shouldn't be too hard to add another one. Actually, usually authentication appears to be the hardest part (due to absence of documentation and examples...) @lnxw48