- cross-posted to:
- android@programming.dev
- cross-posted to:
- android@programming.dev
Personally I don’t care about this since apple is adopting rcs next year. But its a great thing for people who want iMessage.
Personally I don’t care about this since apple is adopting rcs next year. But its a great thing for people who want iMessage.
tbh, I don’t like where this new product seems to be taking Beeper. I was a giant fan of Beeper because they were a huge contributor to the matrix project. But with them creating an entirely new app that doesn’t rely on matrix at all, it looks like they may be looking to pivot away and create their own client-side implementations rather than use matrix bridges. It would be sad to lose a contributor to the matrix space.
Yes. Hopefully they’ll continue to maintain the mautrix bridges they already have.
Also it’s sad to see Beeper misusing the term open source for the source available SSPL [1]. Beeper is free not to use an open source license. But an open source “license must not restrict anyone from making use of the program in a specific field of endeavor” [2], so it’s misleading to call their demo [3] open source.
I do believe supporting the different messaging services client side could be a better experience than relying on a server to translate between different protocols.
[1] https://blog.opensource.org/the-sspl-is-not-an-open-source-license/
[2] https://opensource.org/osd/
[3] https://github.com/JJTech0130/pypush
Beeper Mini is also unfortunately closed source