Goofed Home

RE: https://mastodon.social/@bagder/116359048796181736

Could be potentially nice for fediverse server testing, as more implementations make the jump to final RFC 9421 HTTP signatures.

On the flip side, ever more complex curl invocations (here: Accept header plus signature fields plus key file, presumably) suggest use of more specialized CLI tools, such as provided by @fedify, or at least scripts/aliases.

Speaking of RFC 9421, which notable fediverse implementations can't handle it yet? Anyone keeping track?

#ActivityPub #FediDev #RFC9421

@fedify@hollo.social @julian@fietkau.social

excelent

@gabboman @fedify @julian I'm adding it to activitypub-bot this week. I'll send a link when it's up.

@jaz@toot.wales Great, the CFP for the track is now open!

https://hackers.pub/@fedidevkr/2026/fediverse-social-web-track-at-coscup-2026-cfp

The #CFP for the Fediverse & Social Web track at COSCUP 2026 (Taipei, Aug 8–9) is now open! If you’re working on #ActivityPub, the #fediverse, or anything in the open social web space, we’d love to hear from you. The deadline is May 9. #COSCUP is free to attend.

👉 https://hackers.pub/@fedidevkr/2026/fediverse-social-web-track-at-coscup-2026-cfp

(Boosts appreciated!)

#SocialWeb #fedidev

I am outputting ActivityPub/ActivityStreams content for the listing of what is in a directory.

Think of it as the AP/AS version of output from the `ls` command

AP/AS has a whole bunch of stuff that can be used to represents files. Even sub-types of files

https://www.w3.org/TR/activitystreams-vocabulary/#object-types

And, while AP/AS has 'Collection' (and 'CollectionPage') —

https://www.w3.org/TR/activitystreams-vocabulary/#dfn-collection

AP/AS doesn't have a 'Directory' type (as a sub-type of 'Collection')

#ActivityPub #ActivityStreams #FediDev #FediDevs #Federation

@maddyunderstars

Yes, I am creating a high performance read-only HTTP server for static files — that has built-in support for ActivityPub/ActivityStreams.

It also supports (the read operations of) WebDAV. So, it can be used as a shared read-only drive in operating-systems (OSes) that support WebDAV.

@reiver

This might be a misunderstanding.
Any property in ActivityPub can have multiple properties [except the few marked as 'functional'].
It does not need a special subtype.
If we have type ['CollectionPage', 'Collection', 'wd:Q201456'], it is a directory in a directory (?)
We have these nested structures in fedigeo anywhere, for example the UNESCO World Heritage or IATA Collection etc. We use wikidata (the data of wikipedia) so that anyone can use the label and infos for "directory" in any language …

My ongoing #ActivityPub projects in order of priority, for anyone waiting for something:

– Interaction policy / reply controls FEP: highest priority, stalled for the past few weeks due to other responsibilities
– @encyclia: probably migrating from Deno+Fresh to Node+Hono for @fedify 2.0, boring infra work
– Updating @fedidevs starter packs for compatibility with @loops and @Mastodon packs: on warm hold, will get to it, but vainly hoping someone will write a Python lib for it before I have to 🙃

@COSCUP@floss.social 2026（台北、8月8–9日）にて、Fediverse & Social Webトラックが採択されました！#フェディバース、#ActivityPub、オープンなソーシャルウェブをテーマに、丸一日・計6時間のトラックを予定しています。

発表者向けのCFPはまだ始まっていませんが、公開され次第お知らせします。お楽しみに！

#Fediverse #SocialWeb #COSCUP #ActivityPub #fedidev

@COSCUP@floss.social 2026(臺北, 8月 8–9日)에서 저희 Fediverse & Social Web 트랙이 承認되었습니다! #聯合宇宙, #ActivityPub, 오픈 소셜 웹을 主題로 하루 終日, 總 6時間을 進行할 豫定입니다.

發表者 募集 CFP는 아직 열리지 않았지만, 始作되는 대로 바로 公知하겠습니다. 期待해 주세요!

#페디버스 #연합우주 #SocialWeb #COSCUP #fedidev

Our Fediverse & Social Web track has been accepted for @COSCUP@floss.social 2026 (Taipei, Aug 8–9)! We’ll have a full day—six hours—to fill with talks on the #fediverse, #ActivityPub, and the open social web.

The CFP for speakers isn’t open yet, but we’ll announce it here when it is. Stay tuned!

#SocialWeb #COSCUP #fedidev

@hongminhee @COSCUP STAYING ABSOLUTELY TUNED

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

@hongminhee +1 for formalizing the existing practice in a FEP.

PropertyValue is covered in FEP-fb2a, but it proposes an alternative representation which implementers must support:

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

6/

Continuing to look for an alternative to "attachment" (for properly supporting an Actor specifying a list of Service actors associated with it) —

Maybe a custom top-level attribute would be useful.

Maybe something like:

"service": [
{
"rel":"callpub",
"href":"https://videocalls.example/users/joeblow"
}
]

Although perhaps that is not much better than "attachment", if you just care about calls

So —

#ActivityPub #ActivityStreams #AudioCall #Call #FediDev #Fediverse #VideoCall