- 2 Posts
- 5 Comments
contrapunctus@lemmy.cafeOPto Free and Open Source Software@beehaw.org•The Unexpected Opposition to Free Software AdvocacyEnglish1·1 year agoThe post already explains in painstaking detail why network effect requires us to adopt extreme measures (which you mischaracterize as “you’re either with us or against us”). It’s the nature of the conflict, and free software advocates must either recognize it or lose.
The issues with Matrix are perhaps better explained by others, elsewhere.
contrapunctus@lemmy.cafeOPto Free and Open Source Software@beehaw.org•The Unexpected Opposition to Free Software AdvocacyEnglish1·1 year agoAs I wrote in the post, “meeting people where they are” is how we get free software organizations which use proprietary platforms for everything. This mentality must be avoided if we want to move away from proprietary platforms.
contrapunctus@lemmy.cafeOPto Free and Open Source Software@beehaw.org•The Unexpected Opposition to Free Software AdvocacyEnglish0·1 year agoThe issue is above all that bridging to Telegram (a proprietary, centralized service) basically amounts to normalizing and encouraging proprietary services. The poor UX of bridges is a secondary issue.
You’re not the first person to seemingly have missed that I offered to bridge the XMPP room to the Matrix rroom, provided Telegram was de-bridged…I suppose it’s not clear from my writing.
Thanks for reading, and sharing your feedback.