I didn’t express myself very well earlier when mentioning muting abucci. I muted to stop myself from saying anything regretful (which would be a waste of my time and theirs). Also, I try to make all mutes temporary.

@prologic@twtxt.net This is something I really like about this model. Your twts are still your own. You can at-mention whoever you like however much you like. They just don’t have to listen. Of course, if you’re on someone else’s instance, then it gets a bit more complicated. But at least it’s possible to move to your own.

@prologic@twtxt.net yeah I gotcha. I was saying that ownership of one’s twts are a bit more complicated when they’re one someone else’s instance. The instance owner could, for example, delete the feed of someone who was behaving badly. If they hadn’t backed up their feed, might be game over for all those twts.

@prologic@twtxt.net That’s why I was so excited about search the other day. I was thinking about the possibility of hosting my twtxt on IPFS which would mean effectively hosting it on no machine in particular. (It would change over time and could be multiple at the same time.) However, this would prevent me from knowing my own followers because the request log would be spread out across many nodes which most definitely wouldn’t share their user agent logs with me. That’s not great but perhaps it doesn’t matter. I personally only care about knowing my own followers so that I find people who mention me that I don’t happen to also follow. This is where search/registries would be really valuable. I could just periodically search various indexes/registries for mentions. I feel like this could have a benefit of keeping trolls at a distance. If I only search once an hour and put them in a separate queue, I can handle people outside my circle differently.