@firstname.lastname@example.org Each system was created because there was someone thinking about something that this person was missing from the other systems. Now that we start connecting all these systems back together, do we then need the different systems anymore, or could we only fall back to using one system?
@carsten This is an excellent philosophical point. I like what you’re thinking here, and frankly, I personally prefer things to stay the way they are, small interconnected communities. pull-only model, single-user pods, or multi-user pods (with limited sized). It makes things much more manageable, and as things are designed to be slow, much harder to get drowned in and abused 👌
@email@example.com This is undoubtedly why I went away from Hugo, Pelican, WordPress and co and wrote a small, for my needs, blog software. I also learned a lot about the Flask Framework, which I can now use to enhance our apps at work and make my boss happy. I would have chosen Go, but it was not the chosen product at work, so, sorry. KISS principle. Like almost everything in the *nix world. A small tool for a small thing. Chain it with others if you need more.
The pull-only model seems to work nice. You have multiple social networks, each one with its own unique audience. Pull things from others into your when you want.
From my point of view, I think twtxt and yarn are good as they are. The protocol s nice, easy and clean afaik. The surrounding software, makes it what it is today. Multiple clients, each having it pros and cons. The only thing I am missing is some sort of media manager for my uploaded images to yarn.social. But that is specific to this implementation and has nothing to do with the twtx protocol.
@carsten Thanks 🙏