Progress on the FEP for Event objects

The FEP-8a8e (Fediverse Enhancement Proposal) had at lot of progress in the last months. In the meantime, the document has become somewhat more extensive than originally planned, but contains not only instructions for new features that have to be tediously implemented, but also a lot of advice and points that should provide orientation for developers of Fediverse applications that support events.

It now covers:

• Required attributes
• Events with Open End
• Timezone
• Physical and Virtual Locations
• Event status
• RSVP (Attendee Management)
• Event Banner and Poster Images
• Event Categories
• Discoverability
• Event Organizers
• Upcoming Events Collection for ActivityPub actors
• Term Definitions

Many thanks again to all reviewers and co-editors:

@lesion @heiglandreas @naturzukunft @laurin

We warmly welcome further feedback from the communities of #Friendica, #Mobilizon, #Hubzilla, and other Fediverse platforms supporting events.
If you’re working on such an application or are part of these communities, your insights would be very valuable! @developers @mobilizon

@linos Hi, hattest du für die events/location/PostalAddress nicht irgendwo ein Feld für eine osm id vorgesehen? Ich hätte gewettet das irgendwo gelesen zu haben, finde es aber nicht mehr.

#FEP-8a8e #activitypub #rdfpub

I am working on a new revision of FEP-8b32:

https://codeberg.org/fediverse/fep/pulls/527

There are many editorial changes, such as replacing Controller Documents with Controlled Identifiers, new implementation (apsig), and one new requirement:

>The identifier of the verification method MUST have the same origin as the identifier of the secured document, or have a different origin, but with an established cross-origin trust relationship to the identifier of the secured document.

This is related to today's FEP-fe34 update and should cover all possible uses of integrity proofs, including regular objects signed with DID keys, and portable objects (FEP-ef61). I expect that all existing implementations of FEP-8b32 already meet this new requirement, but if not, please let me know. I'll keep this PR open / WIP for a couple of days.

FEP-fe34 "Origin-based security model" has been updated:

https://codeberg.org/fediverse/fep/pulls/526

There is a new section discussing cross-origin relationships. Some use cases require bypassing of same-origin policy, and in such situations confirmations of both authorities are required. One interesting example is FEP-c390: Identity Proofs, where trust is established by verification of complementary claims made by an HTTP authority (actor document) and DID authority (identity proof document).

I also added the definition of "authentication":

>Authentication is the process of verifying the origin of an object.

And the definition of "authorization":

>Authorization is the process of verfying permission to create, read, update or delete an object.

So, FEP question. How do they continue? Or what are the steps to make a draft accepted? I saw in FEP-a4ed that after sixty days, the author can request it be finalized but what happens if things stall out? Poke on the discussion, ask for what needs to be done? Ask for more comments?

(I really would like to see emoji responses. https://socialhub.activitypub.rocks/t/fep-c0e0-emoji-reactions/4443/7)

Our latest #PushingTheBoundaries online discussion is out!

Check it out at:
https://youtu.be/0zeIlfv5srg

We talk to Kate Nave about her book "A Drive To Survive."

https://mitpress.mit.edu/9780262551328/a-drive-to-survive

Bioenactivism and why the free-energy principle (#FEP) does not explain life.

Updating "FEP-f06f: Object observers": https://codeberg.org/fediverse/fep/pulls/512

I was thinking about managing a thread with #ActivityPub client and realized that observer actors would need to be created with Create(Application) activity where actor is user's primary actor (the one created during the registration).

This is unusual, but should work. Primary actors can't be created this way because the actor property of Create activity can't refer to a not yet created actor.

How to subscribe to a thread?

Several days ago FEP-efda: Followable objects was published. I don't like this solution because ActivityPub spec only talks about "following" in the context of actors, and the proposed "proxy-following" mechanism forces us to change some well-established practices.

So here is an alternative: FEP-f06f: Object observers.

Object observer is an actor that can be followed to receive object updates. If conversation thread is a collection, its observer will broadcast Add and Remove activities that have thread collection as their target. Observer's followers will have an up-to-date view of the thread.

All implementations of FEP-521a are implementations of Controlled Identifiers spec.

#fep #fep_521a #ActivityPub #ControlledIdentifiers

RE: https://w3c.social/users/w3c/statuses/113947371169653222

FEP-2277: ActivityPub core types has been submitted to the FEP repository.

I made several changes based on the feedback, but they are minor. There are parallel discussions at W3C GitHub, where I was told that core types don't exist, or don't matter, but this is obviously wrong, because many requirements in AP and AS depend on definitions of "collection", "activity" and other core types. Classification of objects based on their properties still seems to be the best solution.

Also, due to an uncertainty about the future of SocialHub (where many accounts are going to be suspended soon), I didn't create a discussion topic there. If you have any suggestions or feedback, please reply here or open an issue at https://codeberg.org/silverpill/feps/issues.

TIL Fediverse Enhancement Proposal (FEP) exists

I'm used to PEP in the Python world and DEP in the Django world.

It actually makes sense that similar mechanisms exist in other communities, especially in the Fediverse.

https://codeberg.org/fediverse/fep

I've made some changes to FEP-521a: https://codeberg.org/fediverse/fep/pulls/482

- Many changes due to a rename of Controller Documents specification to Controlled Identifiers.
- Using https://www.w3.org/ns/cid/v1 context in example. I haven't tried it myself yet, but it works in JSON-LD playground.
- Key ID and actor ID are now recommended to have same origin.

FEP-2277: ActivityPub core types (pre-draft)

https://codeberg.org/silverpill/feps/src/branch/main/2277/fep-2277.md

where I make a case for non-overlapping core types and duck typing

FEP-9967: Polls

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

Reminder: AS/AP-based suffers from #BallOfMud based ad-hoc expansion unless we find common practices and stick to them. Collaboration across a commons is essential here. Just coding your app with custom #ActivityPub protocol extension is contributing to #ProtocolDecay and increasing complexity to facilitate broad #interoperability.

The #FEP process and #SocialCG are where collective effort and proactive participation can improve #fedi for all. We need a bottom up standardization process.