@polymerwitch I'm starting to do some updates on the #ActivityPub watchlist for fediverse.party. I notice Acorde never got past the initial commits on GH. Did you move dev elsewhere, or just haven't had time to work on it?
The front page showcases federated apps that are mature, aimed at average users (no geek superpowers required to use), and federate robustly using either one of the widely used federation standards; #ActivityPub, #Diaspora, or #OStatus. New pages have been added to include a range of up and coming apps that don't (yet) tick all of those boxes.
I wrote an article for the Mozilla Hacks blog that's a brief technical introduction to ActivityPub. I also provide an intro to my simple #ActivityPub Node.js server.
Oh. So, #Mastodon "direct messages" are public on any other #ActivityPub network (at least, Osada, Friendica). :think_bread: I should stop comparing them to macroblogging Fediverse "limited" posts then. Those are not public, normally.
Hey, yeah it's related to MoodleNet but CommonsPub is meant to be a generic #ActivityPub server/library that can later be used to power all kind of different apps. Feel free to AMA!
@js ah, ok. Thanks for the clarification. I wonder if Drew if planning to use #OAuth is sr.ht though? He seems to be opposed to using any of the protocols used in #ActivityPub for federating code forges, even though he seems to have no alternative to OAuth, #WebFinger for @mentions etc. My take is that sr.ht and #ForgeFed are addressing different aspects of the problem, and I've been trying to convince them to join forces. It's an uphill struggle so far ;)
@LWFlouisa one of the main arguments Ive heard against using #ActivityPub to federate code forges (as proposed by #ForgeFeb) is that it risks opening them up to spammers and griefers. As we've seen in the #fediverse, not everybody follows the Bill and Ted Principle ("be excellent to each other") on federated platforms ;)
I'd say something like MoodleNet is difficult to define (and I think the word platform is too restrictive, network is better), as it will involve several things:
2. Infrastructure - An initial MoodleNet instance run by Moodle HQ - MoodleNet instances run by other/people orgs - HQ API run by Moodle HQ (the org) as a central service, mostly a search index - Fediverse instances running different software
3. Community/Communities - Proximity: People on the same MoodleNet instance - Groups: People in the same 'Community' or 'Collection' on MoodleNet (across instances) - Graph: A user and the People/Communities/Collections they follow - Fediverse: People interacting between MoodleNet and other federated apps, and vice versa
Went to a great afternoon session run by @dajbelshaw and @mayel on decentralisation and ActivityPub, and how they're harnessing it to enable sharing of educational resources on MoodleNet.
To begin we shared what each of us understood decentralisation/federation/distribution to mean. Some peeps very experienced in ActivityPub were there, including @sandro.
Released #Pterotype version 1.1.1! Sync blog posts and comments from your WordPress blog with Mastodon and let users comment on posts by replying to the Mastodon thread!
Pterotype is available in the WordPress plugin repository and I'd appreciate it if you signed up as a beta tester at https://getpterotype.com/beta