Notices by AndStatus (andstatus@loadaverage.org), page 5
-
AndStatus (andstatus@loadaverage.org)'s status on Thursday, 28-Mar-2019 06:19:49 UTC 
AndStatus
@jandor You do have "Resend" menu item for each note.
But I agree that "is not syncable" confuses. I will change that to "Resend all"?! -
AndStatus (andstatus@loadaverage.org)'s status on Thursday, 28-Mar-2019 05:49:17 UTC
AndStatus
@dwaltiz Funny proposal :-)
I think it's much easier to fix the problem that you encountered (I suspect it's about UI/#UX) yet even _you_ didn't find time to file the issue properly, trying to reproduce it, describing steps to reproduce the issue and attaching screenshots. Just this post that doesn't help to make the app better, unfortunately :-(
Yes, there may be "steps back" (developers call them "regressions") but they occur exactly because I'm rewriting #AndStatus and rely on community members, who take their time to explain, what went wrong...
So, when you are ready to help, please file the bug here and we will substantially discuss it: https://github.com/andstatus/andstatus/issues?q=is%3Aissue+sort%3Aupdated-desc
Maybe at that stage somebody will join us with concrete help... -
AndStatus@Mastodon (andstatus@mastodon.social)'s status on Thursday, 21-Mar-2019 15:50:01 UTC 
AndStatus@Mastodon
@z428 As you may see from the discussion it the GitHub issue, the first and maybe the most undefined step in the #ActivityPub #C2S specification is authentication and whoami (account verification/discovery) steps. We agreed on concrete steps and endpoints with pleroma.site developer, but the same probably won't work out of the box with other systems.
Anyway, I'm open to collaboration and aim at creation of really unified API, compliant with ActivityPub C2S. -
AndStatus (andstatus@loadaverage.org)'s status on Sunday, 10-Mar-2019 18:28:43 UTC
AndStatus
@lanodan @amiloradovsky @kit_ty_kate Yes, #AndStatus really has minimal #ActivityPub Client-to-Server implementation that works with pleroma.site. You can even play with this...
For more details, including current state of this implementation and problems/questions please see https://github.com/andstatus/andstatus/issues/499
@kaniini https://loadaverage.org/attachment/5083546 -
AndStatus (andstatus@loadaverage.org)'s status on Sunday, 03-Mar-2019 16:42:27 UTC
AndStatus
#AndStatus v.47.03 "Avatars and Attachments improved" Beta is published, see https://github.com/andstatus/andstatus/issues/456
What's new:
1. When some Actor follows (or stops following) me, show detailed info about that Actor, not about my Actor.
2. If an attached video has a preview image, that image will be shown (currently available for Mastodon only). View image / View media context menu item for remotely accessed media files.
Show a text link to a media file, for which even preview image couldn't be downloaded (instead of no attachment at all as before). #502
3. Don't download attached Video by default. May be changed in Settings -> Attachments -> Download attached video
4. Actor's avatar in their profile is shown with maximum resolution.
5. Fixed: Cannot delete a Note's Title (Name) after it was first saved (even in a draft).
6. Fixed: Default notification sound was heard even if set to Silent in Settings. This was caused by changed rules after starting to target Android 9.
Any Android notification (including Vibration and Sound) should show an icon in Notification Area (Android 9 restriction). https://loadaverage.org/attachment/5061991 -
AndStatus (andstatus@loadaverage.org)'s status on Friday, 22-Feb-2019 04:11:15 UTC
AndStatus
@nestort It appears that AndStatus still cannot show a preview of remote media files that it didn't download. Currently only locally downloaded images/video files are shown at attachments and may be viewed. As a result, media files that are larger than configured in "Attachments -> Maximum size of an attachment" are not shown at all.
We need to store locally a preview image (if it is available) and show that image. Or at least show a text link to the media file, for which even preview image couldn't be downloaded.
I created the ticket for the feature https://github.com/andstatus/andstatus/issues/502 -
Yuri Volkov (yvolk@loadaverage.org)'s status on Thursday, 21-Feb-2019 18:33:46 UTC 
Yuri Volkov
@emacsen I mentioned WebFingerId not as a part of WebFinger protocol, but only as an artificially created identifier, helping to figure out the same actors via old-style (Twitter-like...) client APIs (which don't provide globally unique identifiers of actors (users...)).
As we're currently are figuring out, how to use #ActivityPub C2S protocol in the real world :-) I see that WebfingerId isn't really needed in ActivityPub API: Actor's profile has enough information to know both username and hostname of an actor (what constitutes WebFingerId).
I think that you will be interested to read our discussion on this here: https://github.com/andstatus/andstatus/issues/499
@cwebber @thefaico @eliotberriot -
Emacsen (emacsen@emacsen.net)'s status on Thursday, 21-Feb-2019 18:07:42 UTC 
Emacsen
@yvolk @andstatus @thefaico @trwnh @eliotberriot @cwebber Thanks for your thoughtful explanation, I'm not sure everyone mentioned here wants to be part of this discussion but it's an interesting one for me!
I use the term "identities" specifically to reference the "id" property of the AP spec.
And some of the technologies you mentioned (Webfinger in particular) are not part of AP, so I think it's important to mention that.
[1/?] -
Emacsen (emacsen@emacsen.net)'s status on Saturday, 09-Feb-2019 05:01:20 UTC
Emacsen
@trwnh @cwebber @eliotberriot @kity
Maybe I misunderstand the issue but I think part of it is that right now people are okay with having N ActivityPub identities in a way that mirrors their proprietary service life. "Mastadon, PeerTube, Pixelfed" each on their own. But if you moved the bar the other way, to each of those being some sub-stream of your general AP identity, then you'd insist on a client (or c2s model) that was flexible enough to handle it.
-
AndStatus (andstatus@loadaverage.org)'s status on Wednesday, 20-Feb-2019 15:39:23 UTC
AndStatus
@emacsen #AndStatus Android client allows you to setup as many user accounts as you wish in several types of Social networks (#ActivityPub is in testing now). And it recognizes the same your Actor in different instaces, showing a combine view of one Actor via several networks, or a view of all your Actors...
@eliotberriot @trwnh @kity @cwebber -
AndStatus (andstatus@loadaverage.org)'s status on Wednesday, 20-Feb-2019 05:29:37 UTC
AndStatus
@kaniini And you only mentioned differencies in authentication part... -
AndStatus (andstatus@loadaverage.org)'s status on Sunday, 17-Feb-2019 15:50:27 UTC
AndStatus
@lynnesbian That it a screenshot made when I only started development, many years ago... And it needs an update definitely :-) -
High-Density Floppy Lynne (lynnesbian@fedi.lynnesbian.space)'s status on Sunday, 27-Jan-2019 23:55:02 UTC 
High-Density Floppy Lynne
just saw this screenshot on andstatus' google play page and got transported back to an era i never wanted to revisit
if you are nostalgic for pre-jellybean android you are wrong. your opinion is wrong.
-
AndStatus (andstatus@loadaverage.org)'s status on Sunday, 17-Feb-2019 15:34:05 UTC
AndStatus
I made the simplest implementation of #ActivityPub C2S protocol in #AndStatus, allowing me to log into pleroma.site, read home timeline and get other user's info (i.e. read the Actor's profile based on his "id").
But I've got an error response from pleroma.site server on an attempt to send a Note, so I created another bug report in pleroma issues tracker: https://git.pleroma.social/pleroma/pleroma/issues/650
Alpha build of AndStatus is attached to this comment: https://github.com/andstatus/andstatus/issues/499#issue-389014088 , source code is available in the repository. https://loadaverage.org/attachment/5020018 -
AndStatus (andstatus@loadaverage.org)'s status on Thursday, 14-Feb-2019 06:15:38 UTC
AndStatus
@lanodan It's OK for #Mastodon and #Pleroma to use in their UI "summary" property only. Especially taking into account that Mastodon actually doesn't have Title/Subject of a "toot" but "CW" only (Content Warning) that fits into semantics of #ActivityPub's "summary" better than into "name".
Above decision shouldn't influence the "name" property, one of basic properties of #ActivityPub vocabulary.
Regarding current usage: Pump.io uses both "name" and "summary" properties since its creation in 2013, and they live together without problems. -
AndStatus (andstatus@loadaverage.org)'s status on Thursday, 14-Feb-2019 05:40:18 UTC
AndStatus
Discussion of the #ActivityPub Note's "name" property usage and it's processing by Pleroma. Main attention is on the Client to Server interactions that are being implemented in #AndStatus.
I feel that we mixing two different use cases here:
1. An ActivityPub property, to which a Note's Subject/Title is placed, when entered via Pleroma web UI.
I understood about this point.
2. Delivery / sending to other servers a Note, which came from a client application or from another server and which has the "name" property.
I assume that if incoming Note has the "name" property, Pleroma doesn't delete that property, but sends it to recipients with the same value.
?!
https://git.pleroma.social/pleroma/pleroma/issues/635 -
:bunny: (kaniini@pleroma.site)'s status on Tuesday, 05-Feb-2019 21:18:01 UTC 
:bunny:
by the way, did you know that Pleroma and AndStatus are collaborating on building a production ActivityPub C2S client?
read about it here: https://github.com/andstatus/andstatus/issues/499
-
AndStatus (andstatus@loadaverage.org)'s status on Monday, 04-Feb-2019 05:54:07 UTC
AndStatus
@colegota I need to look into Notifications another time, after the latest crash fix (that was a one line fix actually). Looks like different "notification channels" are mixed... -
AndStatus (andstatus@loadaverage.org)'s status on Sunday, 03-Feb-2019 14:09:32 UTC
AndStatus
@tom79 "statuses/mentions.json" endpoint is the primary source of Notifications in the GNU Social "type of a Social network" and in Twitter. But as I wrote, an activity / note from ANY timeline may be put into "(Unread) Notifications" timelines, if #AndStatus app decides that a User needs to be notified about it. Even from "Search" timelines, which can be made syncable.
@up201705417@loadaverage.org -
AndStatus (andstatus@loadaverage.org)'s status on Sunday, 03-Feb-2019 13:45:19 UTC
AndStatus
@up201705417@loadaverage.org "Unread notifications" are just notifications, which weren't explicitly marked as "read" by a user (using "Mark all as read" button on an "Unread notifications" timeline).
@tom79 @lnxw48a1@nu.federati.net @colegota
All Chirp! content and data are available under the 
