@hotelbreakfast@mastodon.social standards? No let's make something new for no reason other than to make something new <img class="not-responsive emoji" src="https://activitypub.space/assets/plugins/nodebb-plugin-emoji/emoji/android/1f606.png?v=faddfb1abda" title="" />

@dansup@mastodon.social next time <img class="not-responsive emoji" src="https://activitypub.space/assets/plugins/nodebb-plugin-emoji/emoji/android/1f609.png?v=faddfb1abda" title="" />

@evan oh, I'm sorry.Don't really have those ideas, but it occurred to me that this Indexable functionality sits right at the heart of that tension point for fediverse developers on what is okay to do with public data and what is not, and where there's often controversy and heated debate.Indexable is at the same time a honest attempt to communicate something complex to people on how the network functions. And it is a horror UX as it fails to do so. Now its presence means it has become part of that public data, open to misinterpretation, expectation mismatch, building further on something vague.I think there's nothing in the technology itself that prevents fediverse from becoming just as bad as social media elsewhere already is. The only thing that prevents enshittification in the long term is having those uncomfortable discussions.In other words socio-cultural aspects and subsequent pressures on technology direction are key to success or failure of fediverse in the long term.

@dansup Congratulations! 🥳

@elgg Not underestimating, I am just trying to understand how it works. Judging by outbox contents, it is not a FEP-1b12 group. Looks like an announce-bot to me, but then, how do you achieve privacy? Private Announces?

@Edent (you know it's ancient because it uses the old switch statement syntax)

@wjmaggos > this is a different use case (social networking, more private) than what we do with microblogging or the social news feed (social media, very public) ... one ID for both would be greatI think this is why the SocialCG are working on ways to do E2EE group chat on top of ActivityPub. If this works out, we'll be able to log into a publishing app and a separate private chat app, using the same AP account. Rather than always mashing the 2 use cases together in one app.@Liquidator