silverpill@silverpill@mitra.social: @mczachurski @pfefferle FEP-ee3a was approved. It is now stored in the FEP repository with the DRAFT status, you can update it with another PR if you want.<br><br>At some point it should be finalized, but usually this happens after an author incorporates feedback from a discussion thread and convinces at least one other developer to implement the proposal.

Home | Notifications | New Note | Local | Federated | Search | Logout

Note Detail

Reply to @pfefferle@mastodon.social
Marcin Czachurski@mczachurski@mastodon.social (2026-04-19 21:49:34)
@pfefferle @silverpill I understand your point, but it feels unusual to implement something that is not yet approved - especially in a system that already works and exchanges this information. Any change would require me to release new versions and ensure backward compatibility each time, which is quite a lot of work. I would prefer to wait for a finalized FEP and implement something stable and clearly justified.
---Reply---
silverpill@silverpill@mitra.social (2026-04-20 05:55:52)
@mczachurski @pfefferle FEP-ee3a was approved. It is now stored in the FEP repository with the DRAFT status, you can update it with another PR if you want.

At some point it should be finalized, but usually this happens after an author incorporates feedback from a discussion thread and convinces at least one other developer to implement the proposal.


---Replies---

Marcin Czachurski@mczachurski@mastodon.social (2026-04-20 20:38:58)
@silverpill Okay, I understand. I implemented this FEP, and it has already been deployed to production.

I also added a section to the FEP with information about the services that have implemented it so far - currently only Vernissage. It would be great if you could also add your WordPress implementation there, @pfefferle.

Thanks for the information. PR: https://codeberg.org/fediverse/fep/pulls/826