@squinky@teh.entar.net wait wait I got a meme for this

@julian Yeah initially I was so intimidated by the web of specifications that I threw my hands up and said "maybe once I get there I'll just do whatever makes sense for me", and then as I learned more, I learned that I wasn't the first person to think that

@squinky@teh.entar.net in all seriousness it's entirely up to you which FEPs to support. Some FEPs have more adoption than others, so it would be wise to adopt them over time as well.

Others deal with aspects of the protocol that may not even apply to your specific use case. There is no expectation that one should implement every FEP.

Think of it this way: an FEP is a way to document in public (not in code!) how one or more implementations have approached a problem that the ActivityPub protocol spec did not cover. There may be a lot of them, they may be needlessly complicated, but it's better than having to dig through someone else's code base.