Notices tagged with activitypub

@lightweight #ContributorsWelcome! One way anyone can help is with research, adding new projects to the relevant pages on our wiki, and updating them on the basis of your testing:
https://gitlab.com/fediverse/fediverse.gitlab.io/wikis/

Eg X now successfully federates over #ActivityPub, or Y is adding support for #Diaspora protocols. As the fediverse grows and evolves, this becomes a bigger and bigger job.

@wion Gargron's goals are neither here not there. The fediverse was around long before He got involved:
https://www.coactivate.org/projects/disintermedia/blog/2017/04/01/a-brief-history-of-the-gnu-social-fediverse-and-the-federation/

Gargron maintains one fediverse app and contributed to the development of one of it's protocols (#ActivityPub). Admittedly Mastodon is currently the most popular and well-known, but there are now dozens of fediverse apps, even if you only count the ones successfully federating over AP (see the watchlist I included in the post about Mobilizon).

@wion OStatus and its !groups is an example of how it worked in earlier iterations of the fediverse. #Prismo, #Anancus, #Lemmy, and #Mooncake are all projects working on federated #Reddit-a-likes using #ActivityPub, so compatible with Masto et al. See 'link-sharing and forum apps' on this watchlist for updates:
https://gitlab.com/fediverse/fediverse.gitlab.io/wikis/watchlist-for-activitypub-apps

I don't know much about #Mobilizon yet but my understanding is that it's more a replacement for FB events, #MeetUp.com, etc
@Stoori

@jessmahler
> something needs to be done about other apps not respecting followers only.

I'm talking on the edge of my technical knowledge here, maybe even a bit beyond, so take all this with a grain of salt but ... one way of thinking about a followers-only post is a group DM to everyone following you. So we need all fediverse apps to implement the bits of #ActivityPub that deal with private messages, and a way to detect those that haven't (or won't), and refuse to deliver DMs to them.
(1/2)

@wion The reason for having info-sharing and organizing discussions here is the same as your reason for having watercooler chat here, you don't need to get everyone to join one forum/ chat room for every topic they might be interested in. #ActivityPub includes protocols for federated forums, which is possible in OStatus using !groups. Projects like #Prismo and #Lemmy are trying to build a federated replacement for silos like #Reddit/ #HackerNews using AP. These will improve archiving even more.

@hellpie
> without Gargron the Fediverse would have stayed the way it was for nobody knows how long.

It's impossible to know for sure, but it's unlikely. People were engineering federated social networks for decades before Mastodon started and that would have continued with or without it. See: https://www.coactivate.org/projects/disintermedia/blog/2017/04/01/a-brief-history-of-the-gnu-social-fediverse-and-the-federation/)

Folks from projects like libre.fm, pump.io, MediaGoblin, and Pleroma, would have worked on #ActivityPub with or without Mastodon.
@kaniini

@kaniini I can't help but notice these talking points coming up repeatedly, about the existing *public* #fediverse not protecting privacy. What part of public are people not getting? If folks want fully private federated messaging, they can use networks running #Diaspora, #Zot, #SSB, #XMPP with #OMEMO, or #Matrix with encryption turned on. #OStatus can't do private, and although #ActivityPub can, nobody has implemented it well yet, and its meaningless without encryption (#E2EE).
@hellpie

@DashEquals #Mobilizon? Or #FunkWhale? It would be great to have an events platform or a music platform fully federating over #ActivityPub by the end of 2019 (and ideally inter-operable with #Diaspora and #Zot too)
@dansup @rune

Sure, there's a lot of #UX challenges to be resolved with bridging #ActivityPub and #Diaspora. But it's awesome that #Pleroma folks are taking them on. Any solutions they come up with bring us closer to the elusive goal of universal inter-operability among federation social networks.

@leip4Ier if you don't want your conversations archived, it's simple, don't publish them on the web. Have them using any one of thousands of private comms tools that don't do that. Hopefully the next generation of the #ActivityPub branch of the #fediverse will add tools for reliably private chats, groups etc as the #Zot branch already does.
@DashEquals

That's great @mayel , have you posted this intro to #CommonsPub as a thread on the #ActivityPub board on socialhub.network? Maybe it could even have its own board there?

@jboy oops! Apologies for the avoidable horn-tooting 😰 Looking at the issue Felix filed, it seems like #SFW uses a vaguely similar approach to #ActivityPub (HTTP requests plus JSON).

Have you considered adding #ActivityPub support to the Smallest Federated Wiki? I pitched this here and Ward seems supportive, although unsure of how to proceed:
https://github.com/fedwiki/wiki/issues/122
@autogestion @alcinnz @phoe @nutomic @joshsharp @jboy @cj @tsia
#FedWiki

@loke #ActivityPub supports the groups functionality and there are projects like #Prismo (@prismo) and #Lemmy (and #Anancus but dev seems be dormant) are building federated forum platforms using AP groups. I'd love to see !groups return to the #fediverse is some form, but I suspect these #Reddit-a-likes are probably a better UI for it.
@bob @Wolf480pl

@gergely I'm just doing some updates on the #ActivityPub watchlist I maintain for fediverse.party and I see there are no commits on #CalendarSocial since 7 months ago. Did you abandon the project, or is it just on hold? Or have you moved development somewhere else?
https://gitea.polonkai.eu/gergely/calendar-social

@jonah of course to solve the problem across the whole fediverse, a version of that logic would have to implemented on all the fediverse apps. I wonder if #ActivityPub addresses this, or if an extension could be written to the spec to standardize it?

@noorul yes! AFAIK @funkwhale was designed from the start to support #ActivityPub.