@djsf @evan @bengo Why are corpos even at the table? It should be instances and open source implementations that work on this stuff. Like what Facebook is going to come in and be like "Oh we need such and such thing in the standard" and the folks at gaycommunists.gunclub need to suddenly break everything in order to support it?
@evan @djsf @bengo Hmm I think maybe the difference is I'd like them to implement but not be in charge. The power dynamics would be so imbalanced compared to anything else. IMO it'd be nice if AP was more like HTTP where we had the core more set in stone unlike how stuff like Group Ware and email got turned into something non–corpo impls couldn't coexist with easily.
@evan @mauve @djsf @bengo "Lots of implementations" is not enough to prevent domination. If one implementation represents 90%+ of the AP Fediverse (like Mastodon does currently), domination is a real and significant risk. If Threads implements some variant of AP, they could potentially become the new dominant implementation.
@steve @evan @djsf @bengo Like when they inevitably try to add ads to AP or whatever shit we can give them the finger and fork from any impl that's shitty enough to go with it. Prople thay want big social media corps can go ahead and use em, and existing AP communiyies can do fine without it.
I think it's mostly the monolith instances like .social that will cave to incorporate whatever facebook wants of them
@evan @djsf @bengo I'm sure there's lovely people with good intentions in these companiws hut giving their overlords power over what is currently a mish mash of communities working together will just enable the capitalist misery machine to do it's job of turning human suffering into profit one way or another