So, an interesting issue came up in the #Fedify repo that I've been thinking about: #629.

You know how every #fediverse server uses schema:PropertyValue in actor attachment for profile metadata fields (like “Website”, “GitHub”, etc.)? Turns out, strict #AS2 validators like browser.pub reject it, because the AS2 spec says attachment should only contain Object or Link—and PropertyValue is a schema.org type, not an Activity Streams 2.0 type.

The thing is, we can't just drop the type like we did with Endpoints (#576), because Mastodon and others rely on seeing "type": "PropertyValue" to render profile fields. But at the same time, it's technically not spec-compliant.

I'm leaning towards writing a #FEP to formalize this existing practice rather than trying to invent a new type (like toot:PropertyValue extending Object), which would be a nightmare to migrate across the whole fediverse.

What do you all think? Has anyone else run into this? Would love to hear thoughts from implementers and spec folks.

#fedidev #ActivityPub #ActivityStreams #ActivityStreams2 #AS2 #PropertyValue

New #FEP view:

https://socialhub.activitypub.rocks/t/proposal-explore-page-with-filterable-fep-table/8572/3?u=naturzukunft

#activitypub

FEP website now displays the number of implementations for each implementable proposal:

https://fediverse.codeberg.page/fep/final/

These numbers are based on the information that authors provide in the "Implementations" section of a proposal.

By default, proposals are informational, so authors need to opt in by adding type: implementation to the metadata block.

#fep #fedidev

Recently, there was a discussion about generic #ActivityPub servers. Several people claimed that they were working on one, but it turned out that their "generic" servers only support activities defined in the ActivityPub specification. Such a server shouldn't be called generic. It is not difficult to build, neither it is an interesting concept because competing protocols (e.g. Nostr) already offer much more.

I've been writing a #FEP that describes how to build a real generic server. It is not finished yet, but I feel like now is a good time to publish it:

FEP-fc48: Generic ActivityPub server

This kind of server:

- Can process any object type, and can process non-standard activities like EmojiReact.
- Compatible with FEP-ae97 clients.
- Does not require JSON-LD.

I attempted to implement it when I was researching security properties of FEP-ae97 API: https://codeberg.org/silverpill/fep-ae97-server. Back then I didn't know what to do with side effects, but now I think that we can simply force clients to specify them.

Special thanks to @mariusor and @trwnh for their input.

#C2S

Maior feira de emprego estudantil do país regressa à FEP a 3 e 4 de março com participação de empresas nacionais e internacionais.

#fep #emprego #porto #ensino #fjcportoemprego #feiradeemprego

https://www.leca-palmeira.com/feira-de-emprego-faculdade-de-economia-da-universidade-do-porto/

There's now a proper rendered web interface for FEPs at https://fediverse.codeberg.page/fep/fep/*/, which is much nicer to read than the raw Markdown source on Codeberg. But the canonical permalink, https://w3id.org/fep/*, still redirects to the Markdown file rather than the rendered page.

Would it make sense to update the w3id.org redirect to point to the rendered version instead? It seems like the better experience for anyone following a FEP link, and arguably what a “permanent” link should resolve to—something human-readable.

I'm not sure who manages the w3id.org/fep/ redirect configuration. (It lives in the perma-id/w3id.org GitHub repo, so it would just be a PR, but I'd want to get community consensus first rather than just send one in unilaterally.)

#fedidev #fep #fediverse #ActivityPub

Reduced engagement due to Article type

NodeBB federates out Note or Article depending on the length of the content. While this by-and-large works, the article logic does not encourage as much discussion as expected because a summary is generated so as to provide something for microblog-style software to show (otherwise, it would only show the title (name) and a URL to the forum.)

That summary is limited to a maximum or 500 characters, ending at the last full detected sentence.

When composing a long topic, 500 characters may not be enough to fully introduce the topic and engage users. This lowers click-through rates.

I expressed my frustration about this online to @thisismissem and suggested that I might just revert back to sending the entire post content in summary. This would violate FEP b2b8's recommendation that summary be a maximum of 500 characters:

It should be a maximum of about 500 characters; a few sentences; or a short paragraph.

After consultation with Matt Baer of Writefreely (@[email protected]), he suggested the following changes:[...]

https://activitypub.space/post/1350