@atomicpoet It’s because they’re designing the protocol themselves. It’s not an open, community-driven process, so they’re not often thinking about the things the community needs.
@atomicpoet Strike that. They are thinking about the things the community needs, but only in realtime, as the need arises. So, they’re taking community feedback, but they’re not letting the community be part of the process.
@ramsey@atomicpoet any three active social media and social networking users spending 30 minutes with a legal pad and pen seem likely to producer a more complete list of needed features for a protocol than this. Odd to have so many holes on features and abilities that most people would think central to any social protocol.
@atomicpoet
And since part of the business model seems to be "a plug-in infrastructure for relevancy algorithms" (my wording), this info has to be "publicly available" (on the API level).
@atomicpoet That is utterly horrendous, not to mention horrific! Your blockist should be on a strictly need-to-know basis, which basically should be you (directly) and the service's (through indirections as necessary to maintain your privacy).
@atomicpoet I can see that being problem in that it gives the blockee an unintentional boost, but personally I want everyone to know who I blocked so they can block them too. I'm more of the school of:
@atomicpoet@rmondello isn't this kind of required to implement blocking? Servers need to know who I blocked to not show my boosted posts to blocked users in the federated timeline
@c0dec0dec0de@atomicpoet@rmondello but my server need to tell any server that my posts are boosted to.
If not then they're not really blocked, it's something between a block and a mute
@Paxxi@atomicpoet@rmondello yeah, I’m assuming that the server has a different APIs for peers (other servers) and users. Conceptually, mutes could be implemented client-side. Blocks need the network to participate, but don’t have to just let random users query blocklists for individual users. Naturally, if you have a malicious/shitty admin or server implementation, they can just tell people or expose the peer API to their users.
@c0dec0dec0de@atomicpoet@rmondello yeah, it's difficult to solve in a federated system. I'm guessing there are some smart cryptographers that have some smart solutions to this problem.
I've only seen dunking on blueskys decision but nothing about better solutions or discussion about the tradeoffs involved. If anyone has any good pointers that would be lovely
Add comment