Notices tagged with andstatus, page 10

  1. @itsumonotakumi First of all, # has FAQ, which allows to search for answers and to ask new questions: https://github.com/andstatus/andstatus/wiki/FAQ
    The change log lists features, added during the last six years, with links to detailed descriptions in corresponding development tickets: http://andstatus.org/changelog.html
    Regarding concrete features, which are marked as missed. Just from the top of my mind:
    1. Drafts: You can "Save draft" during editing (see a diskette icon above with this tooltip). Plus, AndStatus has "Drafts timeline" whist lists all drafts chronologically like in any email application. Any draft can be edited or discarded, naturally.
    How this could be overlooked, if you specifically searched for this feature?
    2. Timeline filters. There is more than one way to have filtered timeline:
    2.1 Search for one or several words. Resulted filtered timeline can be even made syncable! (see Manage timelines menu item)
    2.2. See "Filters" section in Settings.
    Do you think that an interested User won't notice any of these ways to filter a Timeline?
    ... https://loadaverage.org/attachment/3744263

    Monday, 04-Sep-17 07:33:07 UTC from loadaverage.org
  2. @fuzboleroxv I think that Pump.io solved the problem with non-synchronized remote User's info/messages the best: instead of loading network with synchronization of questionable importance, its API allows client application to go directly to the User's instance and grab any interesting (publicly available) data from the "golden source". This approach guarantees that you will see all User's public posts etc.
    Pump.io clients, including #, can do this for years, because this is natural and simple ;-)
    @vavassor @gargron

    Wednesday, 30-Aug-17 06:44:07 UTC from loadaverage.org
  3. @raizel Which concrete feature are you missing?
    Currently I'm rebuilding # to support # as a data model natively. In particular, Notifications / Activities timeline will be introduced to show all incoming Activities (and not messages only as now) in the order they were actually received by this device (and not in the order of dates, when corresponding messages were published or actions occurred). So users (especially having multiple accounts) won't wonder, for example, which "New mentions" were received.
    This will immediately make AndStatus much more friendlier to existing Pump.io users, I think.
    ?!

    Friday, 25-Aug-17 06:31:26 UTC from loadaverage.org
  4. @xrevan86 Less than 10% for # Maybe because recently incompatibility of Android 4 with some # instances was discovered... Do you use such device?

    Thursday, 24-Aug-17 20:01:15 UTC from loadaverage.org in context
  5. I decided to drop support of Android versions before v.5.0 in the future releases of #
    This will allow to start cleaning code from outdated solutions and components...
    Android v.4 devices currently amount to less than 13% of active devices, which have AndStatus installed, according to Google Play statistics.

    Thursday, 24-Aug-17 17:19:09 UTC from loadaverage.org in context Repeated by moonman
  6. I decided to drop support of Android versions before v.5.0 in the future releases of #
    This will allow to start cleaning code from outdated solutions and components...
    Android v.4 devices currently amount to less than 13% of active devices, which have AndStatus installed, according to Google Play statistics.

    Thursday, 24-Aug-17 17:19:09 UTC from loadaverage.org in context
  7. @einhornpups For your future reference: How to repair automatic syncing in github.com/andstatus/andstatus

    Thursday, 24-Aug-17 06:09:41 UTC from mastodon.social Repeated by andstatus
  8. @infO_Overlord Different instances of and have different subsets of the same conversation. This is by design of the federated network...
    This is exactly why e.g. I simultaneously use several @AndStatus accounts at different instances. application helps me see copies of the same messages at different instances, choose as what user/at which instance I want/can take part in the discussion, collapse duplicates visually in a timeline.

    Tuesday, 22-Aug-17 06:54:51 UTC from mastodon.social Repeated by andstatus
  9. @takegami If you think that the problem may be at # side, please give more info, including Android and AndStatus versions... Also please look into "Commands in a queue"...

    Thursday, 24-Aug-17 06:55:44 UTC from loadaverage.org
  10. @einhornpups For your future reference: How to repair automatic syncing in github.com/andstatus/andstatus

    Thursday, 24-Aug-17 06:09:41 UTC from mastodon.social
  11. @1iceloops123 "critique" is far better for the project and for developer's inspiration than silent uninstall :-)
    For # news and tips please follow one of my accounts (the list and order of accounts changes over time...):
    @andstatus @andstatus @andstatus@quitter.no @andstatus@identi.ca @andstatus1@twitter.com ...

    Tuesday, 22-Aug-17 16:16:24 UTC from loadaverage.org
  12. @infO_Overlord Different instances of and have different subsets of the same conversation. This is by design of the federated network...
    This is exactly why e.g. I simultaneously use several @AndStatus accounts at different instances. application helps me see copies of the same messages at different instances, choose as what user/at which instance I want/can take part in the discussion, collapse duplicates visually in a timeline.

    Tuesday, 22-Aug-17 06:54:51 UTC from mastodon.social
  13. @decripter37 I noticed that # on devices before Android v.5.1 doesn't work with some Mastodon instances due to outdated connection libraries in the firmware...

    Friday, 11-Aug-17 16:10:36 UTC from loadaverage.org
  14. Meanwhile # v.35.05 is released with latest bugfixes. Will # deliver these news?
    https://github.com/andstatus/andstatus/issues/456

    Wednesday, 09-Aug-17 06:26:12 UTC from loadaverage.org in context Repeated by ericxdu23
  15. Meanwhile # v.35.05 is released with latest bugfixes. Will # deliver these news?
    https://github.com/andstatus/andstatus/issues/456

    Wednesday, 09-Aug-17 06:26:12 UTC from loadaverage.org in context
  16. Such problems could be diagnosed by analysing the application's log. I personally have full logging to files constantly turned on for such cases. More on logging in #: https://github.com/andstatus/andstatus/issues/225

    Friday, 04-Aug-17 06:40:20 UTC from gs.kawa-kun.com
  17. # seems buggy.

    Wednesday, 12-Jul-17 15:25:06 UTC from gs.kawa-kun.com
  18. @andstatus the last two messages was writen from quitter UI.

    The thread starts at this post by @cayentana and all the following (the rest with photos)  by me are published by answering precedents.

    https://quitter.es/notice/3101200

    Examples not shown in the same thread:
    https://quitter.es/notice/3101232
    https://quitter.es/notice/3101245
    https://quitter.es/notice/3101269

    All of them must be in the same thread. But, honestly, I'm not sure if it's a problem with # or quitter.es node.
    Thanks for being there! :)

    Thursday, 06-Jul-17 06:43:05 UTC from quitter.es Repeated by fanta
  19. @andstatus the last two messages was writen from quitter UI.

    The thread starts at this post by @cayentana and all the following (the rest with photos)  by me are published by answering precedents.

    https://quitter.es/notice/3101200

    Examples not shown in the same thread:
    https://quitter.es/notice/3101232
    https://quitter.es/notice/3101245
    https://quitter.es/notice/3101269

    All of them must be in the same thread. But, honestly, I'm not sure if it's a problem with # or quitter.es node.
    Thanks for being there! :)

    Thursday, 06-Jul-17 06:43:05 UTC from quitter.es
  20. The new order of context menu items in # makes it easy to accidentally unfollow someone.

    Thursday, 29-Jun-17 08:51:44 UTC from gs.kawa-kun.com
  21. # is available for testing even for people, who don't use Google Play https://github.com/andstatus/andstatus/issues/456

    Thursday, 29-Jun-17 01:10:07 UTC from gs.kawa-kun.com
  22. # v.34.01 "Showing Twitter tweets longer than 140 characters" released! http://andstatus.org/changelog.html

    Monday, 26-Jun-17 05:13:31 UTC from loadaverage.org
  23. # v.34.01 "Showing Twitter tweets longer than 140 characters" published to the Open Beta testing channel https://github.com/andstatus/andstatus/issues/456 What's new: 1. Fixed Twitter tweets longer than 140 characters were shown truncated. 2. Default order of timelines improved with Home, Public, Search and Everything timelines now at the top. "Everything" timeline is now created for all Social networks to allow easily see all locally cached messages of a Social Network. Sort timelines by "Displ" column in the "Manage timelines" list (by clicking on the column header) to see, how they will be sorted in the "Select a Timeline" dialog. Clicking "Set as Default Timeline" timeline's context menu item permanently moves the timeline above other timelines. Previous default timeline becomes the second in the "Select a Timeline" list. New action "Reset timelines order" added to the "Manage timelines" list helping existing users to reorder timel

    Friday, 23-Jun-17 17:53:53 UTC from loadaverage.org
  24. @gabriel You can have as many accounts in # as you need. Regarding "mastodon.it", as for other Social networks that are not preconfigured: at first, you have to add the "mastodon.it instance" of the Mastodon type Social network to AndStatus. And then you will be able to add account(s) in that Mastodon instance.

    Thursday, 22-Jun-17 06:06:05 UTC from loadaverage.org
  25. @einhornpups # saves currently viewed timeline position before each timeline update, and restores it (i.e. scrolls the list to the same message) after the update. In a case the stored position (last viewed message) cannot be found, AndStatus scrolls to the top of the list.
    Maybe this will give you a clue, why this happens in your case.

    Friday, 16-Jun-17 05:45:48 UTC from quitter.no Repeated by andstatus
  26. @einhornpups # saves currently viewed timeline position before each timeline update, and restores it (i.e. scrolls the list to the same message) after the update. In a case the stored position (last viewed message) cannot be found, AndStatus scrolls to the top of the list.
    Maybe this will give you a clue, why this happens in your case.

    Friday, 16-Jun-17 05:45:48 UTC from quitter.no
  27. Image upload test from # https://herds.eu/attachment/1018499

    Monday, 05-Jun-17 20:58:12 UTC from herds.eu in context Repeated by mcscx2
  28. Image upload test from # https://herds.eu/attachment/1018499

    Monday, 05-Jun-17 20:58:12 UTC from herds.eu in context
  29. Wenn ich mit dem Laptop unterwegs bin und offline Dinge erledige, vermisse ich häufig die Möglichkeit, doch noch schnell ein Posting für die Federation verfassen zu können.
    Mir fehlt ein # für den Laptop!

    Friday, 02-Jun-17 05:38:05 UTC from gnusocial.de Repeated by andstatus
  30. Wenn ich mit dem Laptop unterwegs bin und offline Dinge erledige, vermisse ich häufig die Möglichkeit, doch noch schnell ein Posting für die Federation verfassen zu können.
    Mir fehlt ein # für den Laptop!

    Friday, 02-Jun-17 05:38:05 UTC from gnusocial.de