 This whole Threads situation is pretty stressful It doesn't help that I've called out IG/Meta for blocking Pixelfed in the past*, and shining light on the early NDA discussions I signed the FediPact because of that, and I thought that giving them a chance would prove that I can be a better maintainer by removing my own ego from the equation I now believe that its in @pixelfed best interest to build better safety/privacy tools like domain blocks ❤️ 3 comments
@liaizon @pixelfed I appreciate that and yes I agree, I want to de-emphasize pixelfed.social once our migration and safety/privacy tools are more mature Solo was inspired by the current state of the PF ecosystem, half of all users are on pixelfed.social, and that isn't a good thing You understand me and know the history of me closing registration (like it is now) and encouraging other servers, we need ppl like you on our team to help find balance like you mentioned  @dansup @pixelfed Pixelfed has been seriously improving and I can see how much time, energy & love you pour into it. I want to see Pixelfed thrive! Figuring out how to make PF have more of a community lead direction would help take some of the stress off of yourself. You have talked a lot about the Pixelfed ecosystem being very important and have promoted the client apps a ton, but the direction of the project and yourself feel tightly coupled. I think loosing that coupling could help a ton. |
Gregory's Server
@dansup @pixelfed I think anyone whos been watching you here can tell you care immensely about this whole space and you make decisions and change them based on what you currently believe is the best path of action. I have seen some people post about their disappointment that you changed course about the fedipact, but I think this is mostly just about finding the right balance of communication. Also the division of pixelfed as a project and pixelfed.social can get a bit confusing at times.