Marcin Czachurski@mczachurski@mastodon.social: @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.

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

Note Detail

Reply to @mczachurski@mastodon.social
Matthias Pfefferle@pfefferle@mastodon.social (2026-04-19 18:44:16)
@mczachurski I think implementing it is part of the process. The more implementers, the easier to discuss possible glitches and improve the spec. I am not even sure if a FEP will be published as final without any known implementations… any suggestions @silverpill ?
---Reply---
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.


---Replies---

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.