Notices tagged with pleroma, page 2
-
@strypey Please see this thread https://github.com/andstatus/andstatus/issues/499 and references to #Pleroma in particular. I don't know better #ActivityPup #C2S implementations...
@darius
-
https://lain.com/objects/e7aaeff8-7dc4-43b9-96f9-7308371d63d8
If you're having #PostgreSQL db performance issues in #Pleroma, this may be what you need to hear.
-
@coolboymew I heard recently that #AndStatus doesn't work properly with Pleroma as with "Mastodon type" social network. Didn't investigate this...
But since last year #Pleroma is adding #ActivityPub #C2S (Client to Server) interface, and AndStatus has basic support for this type, checked and tested with Pleroma team! See https://github.com/andstatus/andstatus/issues/499
@dielan @thefaico@quitter.se
-
I don't know the full dev list for #Pleroma, but as far as I know, no Russians. Maybe you meant #Mastodon (the lead dev is of Russian ancestry, but lives in Germany).
-
@dude Hmm. This complicates the plan to add a #Pleroma instance for !FNetworks before we upgrade to !gnusocial 2.0. I'm not really interested in hosting incompatible services (one reason why planned #Diaspora and #Pump.io instances were abandoned).
-
@dansup Last summer I hoped that #ActivityPub Client to Server API for GGU Social will be created. But this didn't happen, unfortunately...
BTW The work on the #AndStatus client side is going on, testing with #Pleroma only so far, see https://github.com/andstatus/andstatus/issues/499
@up201705417@loadaverage.org @sim @dude @lnxw37a2 @alcinnz @lain @xrevan86
-
@dansup Last summer I hoped that #ActivityPub Client to Server API for GG& Social will be created. But this didn't happen, unfortunately...
BTW The work on the #AndStatus client side is going on, testing with #Pleroma only so far, see https://github.com/andstatus/andstatus/issues/499
@up201705417@loadaverage.org @sim @dude @lnxw37a2 @alcinnz @lain @xrevan86
-
@tom79 I think user's confusion is caused by widely advertised "#ActivityPub support", which in reality for almost all servers (except for #Pleroma, as I know) means server to server communication only. Pleroma is the first Social Network that implemented at least minimal set of features, allowing ActivityPub Client applications to connect to it.
@z428 @thefaico
-
@dansup @tom79 there is also https://fediverse.joinout.de/ with !gnusocial and #pleroma nodes. And a few form #Mastodon.
-
@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 #Acti…
-
@kaniini I'm testing client to server #ActivityPub implementation of #Pleroma So far I cannot even complete user authorization step and get the authenticated Actor's endpoints (whoami / verify credentials...) at #Pleroma , because I don't know URL of the API point, see https://github.com/andstatus/andstatus/issues/499#issuecomment-457942709
Could anybody help me?
@mmn
-
After some work, ActivityPub support will be merged into the develop branch of #Pleroma in the next days
https://pleroma.soykaf.com/notice/6722322
Blog post: https://blog.soykaf.com/post/activity-pub-in-pleroma/