@evan do you think that the portable objects/content signing/PDS stuff can be an extension, or is it so much of a difference it needs to be added to the spec
RE: https://mstdn.ca/@davidakin/116439506925613804
Not directed at David at all, but I hate headlines like this. Why should Canada Post be profitable? It's a government service.
That's like saying the roads should be profitable, or garbage pickup.
*wearily reaches up and resets the sign*
It has been [0] days since I have been unable to learn critical information about a local business because it was posted exclusively to Instagram, and in particular behind a login gate.
@valorzard personally, I think a very tight core, with a clear extensibility mechanism and lot of extensions for different applications, is the right model for the Fediverse.
This is just the best article I've read for a long, long time.
https://www.theverge.com/tldr/915176/nft-metaverse-ai-weirdos
@amanjeev hahah
@valorzard I recommend some good patterns:
- Use fallbacks.
- Support multiple profiles -- people are doing great with draft-cavage-12 and RFC 9421, for instance.
- Think about how your software will interact with software written by someone who never read your FEP. Will it fail gracefully, fallback to default behaviour, or crash and leak private data?
- Be compatible with the spec, and not just compatible with Mastodon.
There are a million Fediverses. ActivityPub is already big and diverse with many different extensions and applications.
Nobody has to push their ActivityPub profiles or extensions to the WG if they don't want. Anyone can make extensions to ActivityPub under whatever license they want.
The onus is on extension creators to make their work compatible on the wire with ActivityPub core.
Nobody who works on ActivityPub core wants to break well-defined extensions on the Fediverse.
@evan
from what i understand, some have raised concerns that certain FEPs wont be able to be merged into SocialCG because of the CLA/some creators wanting to be anonymous. How are you planning on handling that?
Will we end up with two fediverses? One that is defined by whatever SocialCG cooks up, and another that is based on all the different FEPs?
We have a staging process for stuff moving from idea stage to recommendation.
https://github.com/swicg/potential-charters/blob/main/stage-process.md