@hrefna I agree with you 100%
Do you see a path forward? FEPs?
Many here are so committed to āhow things wereā that itās hard to talk about āhow things could beā
Iāll happily sign on to something AP-adjacent (strict mode?) that lets us talk to Mastodon and Threads for now, and provides a richer overall UX among the implementers of the new protocol.
Any new group would have to be small, and filled with actual implementers, not industry reps and armchair architects.
@jenniferplusplus @benpate @hrefna I've held this belief for a while. FEPs might not be standardized by W3C but that *isn't* stopping us from implementing them and using them as if they were standard. A lot of standards have had things become standardized because they were common practice beforehand (look at C, C++ implementations). https://codeberg.org/fediverse/fep/src/branch/main/fep/9fde/fep-9fde.md I really would like to see this actually implemented and used.
@puppygirlhornypost2 @hrefna @benpate
This idea of putting together some structured way to describe how other servers should speak to you is one that's come up repeatedly. I'm not all that optimistic about it. I have no idea what the other party could or should do with that info. It's not a problem that's solvable at run time. At least not with the resources and constraints we actually have.
@puppygirlhornypost2 @hrefna @benpate
I get why people are doing it. It's the thing that would make AP an actual protocol. But only if it was done in advance, at design time. So that implementing the protocol meant producing and expecting those behaviors.
I don't think you can get from A to B with FEPs. You have to start fresh, with a successor protocol that actually defines those behaviors.
@jenniferplusplus @puppygirlhornypost2 @hrefna @benpate the issue with writing a new protocol instead of extending an existing one is that it isn't worth anything without anyone actually using it, and getting software developers to implement a completely new protocol instead of adding extensions to their current implementation is a much more difficult task
@lily @puppygirlhornypost2 @jenniferplusplus @hrefna @benpate
Think its worth looking at the PDSes from ATProto here. Adverse Interoperability is a thing, and the Bluesky people are actually not that adverse at all currently to experiments. If you're looking to extend a protocol because of the value of the userbase, atproto might be just as logical of a choice.
thinking in this direction https://berjon.com/ap-at/, but instead of AP its a modified version of AP
