now that @lemmy is seeing a spike in interest, and @Gargron has said he's interested in building out groups on #mastodon - this seems like the right time to update ActivityPub protocol to support groups natively. anyone looking into this?
lemmy's integration into mastodon is pretty janky right now and can be a lot better!
Other variations and extension related to #ActivityPub Groups can be defined in additional FEP's. For instance, there's one about Unbound Group and Organization by @diogo of #GNUSocial that is still in DRAFT..
Has anyone worked on or played with fediverse software that priorities pet names over display names or usernames? so any actor in the system has a private local version of their name that can be changed at anytime by the viewer user and then are only exposed as that name from there on out including in the tagging interface?
Was thinking about this recently, I think a pet name system is actually a lot more robust, and the idea of hard linking identity and data and server infra is the wrong path in the long run. I would also like to see someone play with a "SameAs" function (maybe a #FEP) for tying a bunch of #fediverse identities together into a bundle and then that bundle would then be the thing you would tell people to follow.
I might point to fediverse-ideas repository here, a recently started initiative in the same #Codeberg organization where the #ActivityPub#FEP's are too.
Free and Open Source Content Circle is hosting an event next week and I'd like to invite you!
Exploring Self Governance in the Fediverse: A discussion about decision making among a federated ensemble
--> May 29th 15:00 - 16:30 UTC
We're a circle within @SociocracyForAll , so I'll be interested to find out how sociocracy can support you. There will also be time to chat about common governance models and tensions that arise.
For #FEP (Fediverse Enhancement Proposals) we think of specifying behavior as human-readable, tech-independent #Gherkin scripts. That can be a good approach. Same org has the #FediverseIdea repo.
The #FEP is a good grassroots initiative, that is "névé" and troubling as it lacks "meaning" and is running as a "hobby" project with little if any social buy in.
NOTE: no amount of technical thinking/tinkering will add "meaning" as this is a social, not a technical problem.
I don't know the ins and outs of Channels, but would just like to point to the #Fediverse Enhancements Proposals. If Channels require new mechanisms it would be best to accompany their federation support in #CalcKey with a well-documented #FEP.
Ok so I was told that when you delete a post, a "tombstone" is left in place that points to the post before that so that a thread doesn't get broken. But when I try this (just posted three posts, deleted one, looked them up via the API), the deleted post (api/v1/statuses/:id as well as :id/context) only returns "Record not found", and the next post points to the no-longer-existing record, listing no descendants nor ancestors in /context.
Am I doing something wrong, or have I been told bullshit about ActivityPub and the Mastodon API?
The observations re:tombstones are valuable. If the W3C spec leaves so much open for different impls, creating an #ActivityPub#FEP might be considered to document the recommend best-practice approach.
Overall the more #Fediverse Enhancement Proposals there are, and interaction with the process, the greater the likelihood that devs build interoperable code. And less reference to "Mastodon does this, you can look in their codebase" is needed :)
"A proxy object is an [ActivityPub] object that is semantically identical to an entity on another, non-ActivityPub protocol. For example, an ActivityPub-to-Nostr bridge creates Actors and Notes that are proxies for Nostr users and notes."
We have the Fediverse Enhancement Proposal process, the #FEP where ever more protocol-level mechanisms and #ActivityPub extensions are defined. The process is open to anyone, and proposals are then discussed in the #SocialHub developer community.
I don't know anything about internet protocols other than that they exist and somehow enable this beautiful mess -- could I realistically read and understand something like the ActivityPub protocol? Is there a lay translation of it?
@mjc well, it isn't actually really non-technical, but the #ActivityStreams-Vocabulary spec mentions just ontology with textual explanation and JSON(-LD) samples.
When it comes to extending #ActivityPub - adding a vocabulary/ontology that supports body temperature or RBI - then doing so according to best-practices is still a bit tricky but can be done.
The FEP was written and proposed by @nutomic and implemented in #Lemmy.
#Mastodon participated in the discussion by means of @ClearlyClaire but I do not know the extent to which Mastodon intends to be compatible, and if they will propose FEP's for their partiular Group implementation.
I'm thinking that Task Management is a typical candidate for a standard #ActivityPub vocabulary extension to be created for it. One would even expect a well-known ontology to be available for the purpose.
In any case then it could become a #FEP and until that time you might add an issue to the new fediverse-ideas repo to track this.
Today's question for a resilient #Fediverse is whether various different initiatives are willing to collaborate and cross-pollinate, while keeping their independence.
There's great opportunity to increase the cohesion of the #GrassrootsFedi#ActivityPub developer community and creating strong joins:
deleted_by_author