weirdly, i dont see you on the list unless someone already accepted it haha

yeah just register on it and let me know

(also, important, you need to verify the email)

chose your instance and yeah! if waf moe i think you need to ask for an invite code to @jb

if app.wafrn.net let me know and stuff

wafrn hosts a PDS and you moove your account to it with pdsmoover, and there is a button with a guide to migrate :D

I have seen the power of MFM. I consider it cursed and wont add it to wafrn.

But I hope some day sharkey adds support for marquee

next time check wafrn! its… different and a very opinionated software not gona lie.

But its what it takes to do what wafrn does

cross-posted from: https://lemmy.world/post/44562049

I’m posting on behalf of another user on Reddit,u/TasmanianHorse, who’s exploring the possibility of integrating their platform (Echo, Pinterest alternative) into the Fediverse using ActivityPub.

I recommended the Fediverse to them earlier on, and they’re interested in making their platform interoperable with existing services (like Mastodon, Lemmy, Peertube, Pixelfed, Loops, etc.), but are still in the early stages and looking for guidance.

---

Some of the questions that they had:

• What are the main challenges when implementing ActivityPub from scratch?
• Are there recommended libraries, frameworks, or starter projects to build on?
• How difficult is it to ensure compatibility with multiple Fediverse platforms?
• Any common pitfalls or things to avoid early on?
• Are there best practices for moderation, federation control, or scalability?

---

If anyone here has experience developing for the Fediverse or has worked with ActivityPub, your insights would be really appreciated.

Thanks in advance!

Week in Fediverse 2026-03-20

Servers

- Akkoma v2026.03
- Bonfire v1.0.2
- PeerTube v8.1.3
- Mitra v4.20.0
- NodeBB v4.10.0
- GoToSocial v0.21.2
- Funkwhale v2.0.0
- Ktistec v3.3.4
- ActivityPub for WordPress v8.0.2
- PeerTube v8.1.3
- ties v0.2.0
- Wafrn v2026.03.02
- PieFed v1.6.13
- Some updates to ActivityBot
- tags.pub: Global hashtag server

Clients

- Fedilab v3.37.1
- tinmop v0.9.9.141421356237309504
- tooi v0.23.0
- Holos v1.0.0
- Voyager v2.44.0
- Aria v1.4.6

Tools and Plugins

- mastodon-bookmark-rss: A small app to let you connect your mastodon bookmarks to your RSS reader
- smol overlays: Chat overlay and emoji wall for Owncast streamers

For developers

- activitypub-federation-rust v0.5.11

Protocol

- FEP-3ab2: ActivityPub Event Streaming API
- FEP-34ec: Notification Collection Endpoint
- FEP-db70: RemoveAll Collection Activity
- FEP-c07e: add product type to object
- FEP-c195: JSONPath Filtering for ActivityPub Collection Retrieval
- FEP-f011: Full-Text Search Query Syntax for ActivityPub
- FEP-a1d1: ActivityPub Patch
- FEP-c81b: Agent Social Attribution for ActivityPub

Articles

- Openness, transparency and reach: three reasons why public institutions should embrace the Fediverse
- The Purpose of Protocols

-----

#WeekInFediverse #Fediverse #ActivityPub

Previous edition: https://mitra.social/objects/019ce933-238d-11fb-304d-c3557c940c30

@weekinfediverse there have been a bunch of updates to @fabio's #MadBlog this week too

@weekinfediverse also #pawfed https://codeberg.org/tom79/pawfed

cross-posted from: https://lemmy.world/post/44524093

Its called Aiko.

It’s still in beta.

Although I did suggest that they potentially consider federation

https://www.reddit.com/r/Pinterest/s/ZZDgIfJRWd

No offence, but I don’t think that I would want Pixelfed to add Pinterest style features.

It just feels like, at least IMO, trying to be too many things at once.

Pixelfed should remain separate from any Pinterest alternative that the Fediverse decides upon.

Now if Pixelfed wants to add features that are inspired by Pinterest, then that’s a different thing.

To me, pinterest is simply instagram/pixelfed with collections that include both other people images and yours and are displayed in masonry layout. I don’t like masonry so if we can switch between layout everybody should be satisfied

GNU MediaGoblin was founded by @cwebber. Inspired by GNU social reviving development of the StatusNet project abandoned by Identi.ca, they developed a vision of enabling federation features between MediaGoblin services, and between those and services running GNU social, GNU FM, etc. To this end, along with Jessica Tallon (@tsyesika), they got involved with the AP standardisation process, which consumed a lot of their time and organising energy.

(1/?)

#FediverseParty #ActivityPub #MediaGoblin

Response to MediaGoblin AP issue part 1;

> That's the clarity I was looking for, thanks. I've seen cases where conflict-avoidant maintainers say 'submit a patch' when what they mean is; 'this is an anti-goal but I don't want you to try to convince me otherwise, so I'll pretend to be open to a patch'. Clearly this is not you, which is a very good thing : )

(5/?)

Response to MediaGoblin AP issue part 2;

~sturm
> If you yourself are interested in implementing these features, I'd be glad to discuss in detail

Sadly I have neither the time or the skills. But if I hear from a dev wanting to gain experience with AP, and keen to brush up their Python, I will suggest adapting SH's federation library to work with MG as a project.

Thanks for the frank exchange, and keep up the good work.

(6/6)

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