FEP-ef61: Portable Objects

[anotherdoesnm]

Add support for FEP-ef61 for creating server indepent fediverse applications This FEP are depend on 8b32 which already available in Fedify

[erlend-sh]

Supported! I logged the same request for wafrn.

This would also make way for Nomadic Identity.

[outlaw-dame]

https://codeberg.org/fediverse/fep/src/branch/main/fep/8b32/fep-8b32.md

[anotherdoesnm]

https://codeberg.org/fediverse/fep/src/branch/main/fep/8b32/fep-8b32.md

https://fedify.dev/manual/send#object-integrity-proofs

[2chanhaeng]

@dahlia Can I take this issue?

[dahlia]

@2chanhaeng Thanks for your interest in taking on this issue! However, after reviewing the FEP-ef61 specification in detail, I believe this might be too large for a single person to handle effectively.

FEP-ef61 introduces several complex components that would need to be implemented:

• New ap:// URL scheme with DID-based identifiers
• Gateway system with /.well-known/apgateway endpoints
• Multi-server synchronization for portable objects
• Integration with multiple related FEPs (FEP-8b32, FEP-ae97, FEP-fe34, etc.)
• Backward compatibility layer for existing ActivityPub implementations
• Hashlink support for media with integrity verification

Given the scope, I think we should first:

1. Break down this issue into smaller, manageable tasks
2. Create an implementation roadmap with clear phases
3. Identify which components can be developed in parallel
4. Determine if we need domain expertise in specific areas (DIDs, cryptographic proofs, etc.)

Would you be interested in helping with a specific component once we've done this planning? For example, you could focus on the DID parsing module or the basic gateway endpoint implementation, which would be more manageable as individual contributions.

Let's discuss how we can best approach this. Perhaps we could start with a design document or RFC that outlines the architecture before diving into implementation?

[2chanhaeng]

OK, then. Please let me know after the plan is ready!