If you have a big enough portfolio, direct indexing (using something like Frec or Wealthfront) could be an interesting option, and weighting the companies that you don't want at 0.
> It's not enough for the people who run a service to be good people – they also have to take steps to insulate themselves (and their successors) from the kind of drip-drip-drip rationalizations that turn a series of small ethical waivers into a cumulative avalanche of pure wickedness
I completely disagree with this guy. No amount of process or protocol can be a substitute for an actually decent organization culture; without the latter, everything falls apart no matter how good the former is.
Mostly just markdown-based skills. I've personally had more luck with harnesses, preconfigured permissions, and scripts to automate the frequent workflows, and the repo seems pretty light on that.
Eh, AP has its own sets of problems (underspecified protocol, split-brained on discoverability, new developments are met with hostility in the community)
I don't care about the specific situation either way; What I am observant of is how the core team has handled their userbase and lack of protocol robustness.
and I actually don't hate that bit (I really like lexicons, although I might have approached it in a different way) - what I hate is the aggregation layer. I know that it is possible to have an AppView-less atproto app (e.g. RedDwarf), but I feel like much of the ecosystem still defaults to the assumption that it will go through the Bluesky AppView.
I don't even think having Jesse Singal on the platform is the problem (like it or not, I believe that all beings must have the right to communicate); the problem here was the communication failure when communicating this decision to the userbase. They could have just reiterated their rules and left it at that; instead, they chose to mock their userbase, write them off as harassment, and banned users left and right, abusing their position in network to censor people at every layer of the protocol.
How do you feel about the recent communication failures from the team to the userbase? As another builder of an open-source social platform, we must all understand that it is paramount for any company to not antagonize its customers, doubly so for a SOCIAL platform. I do understand that Bluesky and ATProto has to deal with a lot of baggage from both the old userbase and the new influx from the X/Twitter exodus, but engaging in user-antagonistic communication caused me to sour on the whole protocol.
I think the main advantage of the XML here is that the model is expected to have a matching end tag that is balanced, which reduces the likelihood of malformed outputs.